Connectors in the GraphQL schema

GraphQL meets REST, with Apollo Connectors

Introducing Apollo Connectors Project setup How Connectors work in the schema Defining a @source The @connect directive Debugging Connectors Arguments Orchestration in action Using entities with Connectors Mutations

3. How Connectors work in the schema

Practice

What is the purpose of the @source directive?

To define the HTTP method and path for an API endpoint.To define how JSON responses map to schema fields.To specify core information about a data source, such as its base URL and headers.To configure the router to handle API requests.

What does the @connect directive do?

Defines the core information about a data source.Configures the router to process API requests.Defines request instructions and response mappings for root or object fields in the schema.Connects fields from one schema to fields in a different schema file.

Key takeaways

The @source directive sets up data sources, including their name, base URL, and any necessary HTTP headers.
The @connect directive attaches to root or object fields, defining instructions for our request and responses to a REST API endpoint.
The router serves as the single entry point to the API, taking care of the orchestration for us.

Up next

Let's jump into the schema and put these directives to work! Coming up next, we'll use @source to define our REST API data source.

Share your questions and comments about this lesson

Your feedback helps us improve! If you're stuck or confused, let us know and we'll help you out. All comments are public and must follow the Apollo Code of Conduct. Note that comments that have been resolved or addressed may be removed.

You'll need a GitHub account to post below. Don't have one? Post in our Odyssey forum instead.