Enhance customer experiences with Apollo GraphOS

Handling the N+1 Problem Declaratively with Apollo Connectors


<p class="wp-block-paragraph">We’ve all been there: vague API docs, an outdated OpenAPI spec, and a half-buried list of endpoints that leave you guessing. With prebuilt <a href="https://www.apollographql.com/docs/graphos/connectors">REST Connectors</a>, you skip the guesswork. Just download the schema files, run your graph locally, and start querying live data with GraphQL.<br></p>



<p class="wp-block-paragraph">In this guide, we’ll use the <a href="https://thespacedevs.com/llapi">Space Devs Launch Library 2</a> in the <a href="https://github.com/apollographql/connectors-community/tree/main">Connectors Community repo</a> as an example to show how easy it is to integrate a REST API into your graph in minutes and how you can tailor it to meet your needs.</p>



<h2 class="wp-block-heading"><a href="#prerequisites" aria-hidden="true" class="aal_anchor" id="prerequisites"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Prerequisites</h2>



<ul class="wp-block-list">
<li>Create an <a href="https://studio.apollographql.com/">Apollo Studio</a> account. This allows you to create and manage your graph, providing the necessary credentials, APOLLO_KEY and APOLLO_GRAPH_REF (more on those later…) which the Apollo Router uses to fetch the supergraph schema and run locally.</li>



<li><a href="https://www.apollographql.com/docs/rover/getting-started#installation-methods">Install</a> and <a href="https://www.apollographql.com/docs/rover/configuring">authenticate</a> Rover CLI which we will use for configuring our graph and running Apollo Router locally.</li>
</ul>



<h2 class="wp-block-heading"><a href="#setup" aria-hidden="true" class="aal_anchor" id="setup"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Setup</h2>



<p class="wp-block-paragraph">In your working directory, initialize your schema with:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover init</code></pre>



<p class="wp-block-paragraph">Select the option to create a new graph.</p>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="563" height="191" src="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXdh3fMQgFgWtJA4lcp3KQZ1nFByKyDQLFkiN5eh5EkVRoKQuOy5l4zfAlhhc9-V7xpF3n30bXhvdZvpqTk4F1WddygOcvqLlLxd3Iv_v_TYIozku47ugVOPorwAcdkBwsM5AvF5Qg.png" alt="" class="wp-image-24399" srcset="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXdh3fMQgFgWtJA4lcp3KQZ1nFByKyDQLFkiN5eh5EkVRoKQuOy5l4zfAlhhc9-V7xpF3n30bXhvdZvpqTk4F1WddygOcvqLlLxd3Iv_v_TYIozku47ugVOPorwAcdkBwsM5AvF5Qg.png 563w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXdh3fMQgFgWtJA4lcp3KQZ1nFByKyDQLFkiN5eh5EkVRoKQuOy5l4zfAlhhc9-V7xpF3n30bXhvdZvpqTk4F1WddygOcvqLlLxd3Iv_v_TYIozku47ugVOPorwAcdkBwsM5AvF5Qg-300x102.png 300w" sizes="auto, (max-width: 563px) 100vw, 563px" /></figure>



<p class="wp-block-paragraph">Then “Start a graph with one or more REST APIs”.</p>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="565" height="208" src="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcNMVqddgoNT2Hh0WfUUXBCgLCkk-0P8qHEjz6QQn8UpdIpa7mC0C2vlzRz6DG8nP2QVzQ63DltPRgE1vTkYSE6pxqeQOu4PSyouyXMJBp23Sudd2eLR2tN3nqM8FgLYWwVsJL2HA.png" alt="" class="wp-image-24395" srcset="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcNMVqddgoNT2Hh0WfUUXBCgLCkk-0P8qHEjz6QQn8UpdIpa7mC0C2vlzRz6DG8nP2QVzQ63DltPRgE1vTkYSE6pxqeQOu4PSyouyXMJBp23Sudd2eLR2tN3nqM8FgLYWwVsJL2HA.png 565w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcNMVqddgoNT2Hh0WfUUXBCgLCkk-0P8qHEjz6QQn8UpdIpa7mC0C2vlzRz6DG8nP2QVzQ63DltPRgE1vTkYSE6pxqeQOu4PSyouyXMJBp23Sudd2eLR2tN3nqM8FgLYWwVsJL2HA-300x110.png 300w" sizes="auto, (max-width: 565px) 100vw, 565px" /></figure>



<p class="wp-block-paragraph">Next you will name your graph and Rover will generate you a new ID for your graph and APOLLO_KEY.&nbsp; Once your APOLLO_KEY and GRAPH_REF are generated,you can start the router with the command provided, but I would recommend putting these values in an VSCode &gt; settings.json. The configuration below will ensure these environment variables are loaded into any new VSCode terminal windows you open:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-python" data-line="">{

 &quot;terminal.integrated.profiles.osx&quot;: {

   &quot;graphos&quot;: {

     &quot;path&quot;: &quot;zsh&quot;,

     &quot;args&quot;: [&quot;-l&quot;],

     &quot;env&quot;: {

       &quot;APOLLO_KEY&quot;: &quot;&lt;YOUR_KEY&gt;&quot;,

       &quot;APOLLO_GRAPH_REF&quot;: &quot;&lt;GRAPH_REF&gt;&quot;

     }

   }

 },

 &quot;terminal.integrated.defaultProfile.osx&quot;: &quot;graphos&quot;

}</code></pre>



<p class="wp-block-paragraph">  Rover generated a supergraph.yaml file for you. You can delete this.</p>



<h2 class="wp-block-heading"><a href="#using-thespacedevs-prebuilt-connector" aria-hidden="true" class="aal_anchor" id="using-thespacedevs-prebuilt-connector"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Using thespacedevs prebuilt connector</h2>



<p class="wp-block-paragraph">Next, navigate to<a href="https://github.com/apollographql/connectors-community/tree/main/connectors/thespacedevs"> thespacedevs folder</a> in the Connectors Community repo. This Connector is an implementation of the <a href="https://thespacedevs.com/llapi">Space Devs Launch Library 2</a>.  Download all of the graphql files here and the supergraph.yaml.  You can add these to the root of your project folder. Rover generates test schema files and a supergraph. Anything that is duplicated or you do not need can be removed.</p>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="1136" height="546" src="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcTiWPeDxP7Qgwzi8jTAT9xOOpw98vdj43HjwF3q-E37dnH2M8aKEK0vYbEezZN04npXlzALEqp4mZ7vKSJESe-NE7AJa2wn_1i_67kyIDhSODE8JFeLGZqEioHQIdZGffJbEh8UA.png" alt="" class="wp-image-24401" srcset="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcTiWPeDxP7Qgwzi8jTAT9xOOpw98vdj43HjwF3q-E37dnH2M8aKEK0vYbEezZN04npXlzALEqp4mZ7vKSJESe-NE7AJa2wn_1i_67kyIDhSODE8JFeLGZqEioHQIdZGffJbEh8UA.png 1136w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcTiWPeDxP7Qgwzi8jTAT9xOOpw98vdj43HjwF3q-E37dnH2M8aKEK0vYbEezZN04npXlzALEqp4mZ7vKSJESe-NE7AJa2wn_1i_67kyIDhSODE8JFeLGZqEioHQIdZGffJbEh8UA-300x144.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcTiWPeDxP7Qgwzi8jTAT9xOOpw98vdj43HjwF3q-E37dnH2M8aKEK0vYbEezZN04npXlzALEqp4mZ7vKSJESe-NE7AJa2wn_1i_67kyIDhSODE8JFeLGZqEioHQIdZGffJbEh8UA-1024x492.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXcTiWPeDxP7Qgwzi8jTAT9xOOpw98vdj43HjwF3q-E37dnH2M8aKEK0vYbEezZN04npXlzALEqp4mZ7vKSJESe-NE7AJa2wn_1i_67kyIDhSODE8JFeLGZqEioHQIdZGffJbEh8UA-768x369.png 768w" sizes="auto, (max-width: 1136px) 100vw, 1136px" /></figure>



<p class="wp-block-paragraph">Next, open your terminal and run the following.</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover dev --supergraph-config supergraph.yaml</code></pre>



<p class="wp-block-paragraph">That’s it! Your graph is live at http://localhost:4000. Pop it open in your browser to explore the queries in Apollo Sandbox.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="640" height="342" src="https://wp.apollographql.com/wp-content/uploads/2025/06/upcomingLaunches.gif" alt="gif of launches query executing" class="wp-image-24392" /></figure>



<h2 class="wp-block-heading"><a href="#modifying-a-prebuilt-connector" aria-hidden="true" class="aal_anchor" id="modifying-a-prebuilt-connector"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Modifying a prebuilt connector</h2>



<p class="wp-block-paragraph">You can use a prebuilt Connector as is or modify it for your application.  For example, I’d like to add more information about what a valid search string looks like for upcoming launches.</p>



<p class="wp-block-paragraph">In <strong>launches.graphql</strong> find the upcoming launches query and place this comment above it.  </p>



<pre class="wp-block-prismatic-blocks"><code class="language-python" data-line="">&quot;&quot;&quot;
Fetches a list of upcoming launches by agency name. 
Try Starlink, Nasa, or Exa for example.
&quot;&quot;&quot;
upcomingLaunches(search: String, limit: Int = 5, offset: Int = 0): LaunchConnection

   @connect(

     source: &quot;llv2&quot;

     http: {

       GET: &quot;/launches/upcoming/?search={$args.search}&amp;limit={$args.limit}&amp;offset={$args.offset}&amp;format=json&quot;

     }
...rest of code</code></pre>



<p class="wp-block-paragraph">Save your file and you will see your new comment as context in the query builder.</p>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="696" height="371" src="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXfLemjFId_VBD269QHAioohgplSwU15tAJEE8bsZcoIYAh1s-p8F1CNdh3RL1HuM4u0aHSaUMWP7D7G_G_qbxwxlpJgzg4b1N3DOBmyvvpLlmzzF04tEHMl6JrrdGwJy97NVk5z-A.png" alt="" class="wp-image-24397" srcset="https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXfLemjFId_VBD269QHAioohgplSwU15tAJEE8bsZcoIYAh1s-p8F1CNdh3RL1HuM4u0aHSaUMWP7D7G_G_qbxwxlpJgzg4b1N3DOBmyvvpLlmzzF04tEHMl6JrrdGwJy97NVk5z-A.png 696w, https://wp.apollographql.com/wp-content/uploads/2025/06/AD_4nXfLemjFId_VBD269QHAioohgplSwU15tAJEE8bsZcoIYAh1s-p8F1CNdh3RL1HuM4u0aHSaUMWP7D7G_G_qbxwxlpJgzg4b1N3DOBmyvvpLlmzzF04tEHMl6JrrdGwJy97NVk5z-A-300x160.png 300w" sizes="auto, (max-width: 696px) 100vw, 696px" /></figure>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s Next?</h2>



<p class="wp-block-paragraph">Once you have the prebuilt Connector ready for your use case now you are ready to integrate it to a client.  To continue exploring where to use this Connector, take a look at <a href="https://www.apollographql.com/blog/simplify-your-rest-api-logic-in-react-with-connectors-for-rest-apis-and-graphql">this tutorial</a> to learn how to replace traditional REST API calls in a React and Next.js application. Or write your very first MCP tool using the <a href="https://www.apollographql.com/docs/apollo-mcp-server">Apollo MCP server</a>. There’s even a <a href="https://github.com/apollographql/apollo-mcp-server/tree/main/graphql/TheSpaceDevs">ready to go example </a>using The Space Devs Api for MCP you can use.</p>



<p class="wp-block-paragraph">There are many prebuilt Connectors ready to use or extend including <a href="https://github.com/apollographql/connectors-community/tree/main/connectors/stripe">Stripe</a>, <a href="https://github.com/apollographql/connectors-community/tree/main/connectors/openai">OpenAI</a>, <a href="https://github.com/apollographql/connectors-community/tree/main/connectors/aws">AWS Lambda</a>, and more. <br>Motivated to build your own Connectors to share with the community? We welcome contributions! Learn how to submit your Connector in the <a href="https://github.com/apollographql/connectors-community">Connectors Community repo</a>.</p>


From REST to GraphQL in minutes with prebuilt Connectors

Simplify Your REST API Logic in React with Connectors for REST APIs and GraphQL

Integrate Headless CMS Data with any API in GraphQL


<p class="wp-block-paragraph">Today we are releasing <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a>, a major update that brings our declarative, graph-based orchestration technology to teams using REST APIs.</p>



<p class="wp-block-paragraph">Modern applications integrate dozens or even hundreds of different APIs. The task is significant. These APIs must be called in a precise manner and sequence. API calls need to be chained together, feeding the output of one into the next. In some cases, it’s desirable to parallelize them for better performance. Synchronous services can be made async, and vice versa. Almost universally, it is necessary to filter, transform, and reformat the responses, as they are rarely an exact match for the needs of an application. Teams must properly handle errors and timeouts, not to mention authentication and authorization.</p>



<p class="wp-block-paragraph">We can give a name to these tasks: API orchestration.</p>



<p class="wp-block-paragraph">API orchestration accounts for a significant fraction of the total cost of implementing software. It shows up everywhere: application teams shipping roadmap items, companies migrating off of legacy software systems or onto modern microservice architectures, anyone acquiring products and integrating them together, and in every agentic AI project – the last of these especially top of mind now for many. And because orchestration requirements tend to be unique to each individual application or use case, teams end up accumulating a mountain of code dedicated to orchestration.</p>



<p class="wp-block-paragraph">In the vast majority of cases, API orchestration is implemented procedurally, as code. This is the world of backends-for-frontends, integration APIs, and SDKs autogenerated from service catalogs. Sometimes the code is implemented as a separate tier, as in the BFF pattern. Other times, it lurks inside applications or services. No matter where it lives, this code is expensive to write and annoying to maintain. It holds API-rich companies back from shipping great products and getting the most value from their API investments.</p>



<h3 class="wp-block-heading"><a href="#graphql-is-graph-based-api-orchestration" aria-hidden="true" class="aal_anchor" id="graphql-is-graph-based-api-orchestration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL is graph-based API orchestration</h3>



<p class="wp-block-paragraph">What we’ve known all along is that GraphQL is really a technology for API orchestration. GraphQL federation, which we developed in collaboration with many of the teams using GraphQL at large scales, allows developers to write GraphQL queries that get executed as an automatically planned sequence of individual API calls. The heart of what makes this possible is an advanced runtime, the <a href="https://www.apollographql.com/graphos-router">Apollo Router</a>, that provides connection management, rate limits, error handling, API call chaining and more, all made available through GraphQL schemas and operations.</p>



<p class="wp-block-paragraph">Most of the API orchestration tasks I listed above? They’re built right into the Apollo Router with our implementation of <a href="https://www.apollographql.com/federation">GraphQL federation</a>. Apollo developers don’t write procedural code to cache API responses, enforce authentication policies, filter results, or join across APIs. To give one example of how much power comes with this, you can mark part of a query as “deferrable” which instructs the query planner to break the query into a synchronous portion and an async portion to be delivered later – typically data coming from slow APIs that you can’t allow to delay app interactivity or a screen render. Six characters and a couple of braces replace what would have been a significant amount of procedural code to write, test, and maintain.</p>



<p class="wp-block-paragraph">GraphQL federation has been a huge success. It now powers many of the largest online retailers, media properties, traditional banks, and fintech startups. It’s probably inside your television and will almost certainly be in your next car. Companies that adopt this architecture are able to ship new products in a fraction of the time it used to take and with far less development risk.</p>



<h3 class="wp-block-heading"><a href="#bringing-graphql-to-everyone" aria-hidden="true" class="aal_anchor" id="bringing-graphql-to-everyone"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bringing GraphQL to everyone</h3>



<p class="wp-block-paragraph">There’s one hitch, though. To use graph-based API orchestration, you needed GraphQL APIs – either by adding GraphQL to existing services or by creating new GraphQL-specific services (what GraphQL federation developers call “subgraph servers”). This requirement was a significant up-front price of admission to the benefits of graph-based orchestration. And hearing customer after customer tell us about the REST APIs they wanted to bring to the graph led us to a key insight, which is that the responses from these APIs are awfully close to the entity objects that make up a federated GraphQL schema. All that’s really necessary is a language for describing the relationship between them.</p>



<p class="wp-block-paragraph">And that leads us to today’s news: we’re making <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a> for REST APIs generally available, which lets you define a GraphQL schema in terms of the REST APIs you have and orchestrate calls to those APIs with just a few lines of configuration. </p>



<p class="wp-block-paragraph">Connectors are meant to work with real-world APIs: they include functions you can use to restructure and transform API responses as needed and support the usual patterns for headers, auth credentials, and so on. And it’s just federated GraphQL under the hood, so you can use all the usual federation features and mix and match any combination of REST and GraphQL together. You can read much more technical detail about how Apollo Connectors work in our <a href="https://www.apollographql.com/blog/our-journey-to-apollo-connectors">engineering blog</a>, the <a href="https://www.apollographql.com/docs/graphos/schema-design/connectors">documentation</a>, or just give it a try with your own APIs. Everything you need is included in our free tier of GraphOS and you can be orchestrating APIs in well under an hour.<br>Since we <a href="https://www.apollographql.com/events/exploring-apollo-s-new-products-a-deep-dive">previewed Apollo Connectors</a> at GraphQL Summit in October we’ve worked with many of you to improve every aspect of their tooling and functionality. Early results are promising: you can read about how the team at <a href="https://www.apollographql.com/customers/cox-automotive">Cox Automotive </a>used Apollo Connectors to add a particularly important API to their graph in just days, saving nearly a year of otherwise planned development work. We’re looking forward to hearing about your experience.</p>



<h3 class="wp-block-heading"><a href="#the-future-is-declarative" aria-hidden="true" class="aal_anchor" id="the-future-is-declarative"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The future is declarative</h3>



<p class="wp-block-paragraph">Declarative architectures define the modern, cloud-native stack. Containerization for packaging software. React for packaging UI components. It should be no different for APIs.  Apollo Connectors allows developers to describe the data model they want, and let Apollo&#8217;s graph-based API orchestration infrastructure figure out how to do it.</p>



<p class="wp-block-paragraph">We believe declarative, graph-based orchestration is going to replace procedural orchestration code. We’re excited to see GraphQL become the standard that all developers can reach for and we’re committed to working with everyone interested to make that happen. And we can’t wait to see what you build with it.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Ready to get started? Try Connectors today with <a href="https://studio.apollographql.com/signup?referrer=blog">our new free tier</a>, explore our <a href="https://www.apollographql.com/docs/">documentation</a> and<a href="https://www.apollographql.com/tutorials/"> Odyssey training courses</a>, or join us at upcoming <a href="https://www.apollographql.com/events">Connectors Live events</a> to learn more. The future of APIs is here – powered by GraphQL-based API orchestration that makes it easier than ever to build applications.</td></tr></tbody></table></figure>


Apollo Connectors

Handling the N+1 Problem Declaratively with Apollo Connectors

From REST to GraphQL in minutes with prebuilt Connectors

Simplify Your REST API Logic in React with Connectors for REST APIs and GraphQL

Integrate Headless CMS Data with any API in GraphQL

REST API Orchestration With GraphQL

Our Journey to Apollo Connectors

API Orchestration with Connectors – Thinking in Entities

Past posts

Simplify OData API Orchestration with Apollo Connectors

Apollo Connectors

Handling the N+1 Problem Declaratively with Apollo Connectors

From REST to GraphQL in minutes with prebuilt Connectors

Simplify Your REST API Logic in React with Connectors for REST APIs and GraphQL

Integrate Headless CMS Data with any API in GraphQL

REST API Orchestration With GraphQL

Our Journey to Apollo Connectors

API Orchestration with Connectors – Thinking in Entities

Past posts

Simplify OData API Orchestration with Apollo Connectors

Stay in our orbit