# API Orchestration with Connectors - Thinking in Entities

DevFeed: [API Orchestration with Connectors - Thinking in Entities](<https://devfeed.tech/articles/api-orchestration-with-connectors-thinking-in-entities-23152.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/api-orchestration-with-connectors-thinking-in-entities>)

Author: Michael Watson

Published: 2025-02-12T16:51:19Z

Content type: article

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [Apollo Connectors](<https://devfeed.tech/topics/apollo-connectors.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [assets](<https://devfeed.tech/tags/assets.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [identifier](<https://devfeed.tech/tags/identifier.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [openapi-specification](<https://devfeed.tech/tags/openapi-specification.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-apis](<https://devfeed.tech/tags/rest-apis.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

## AI overview

The excerpt recommends identifying API entities before connecting REST services so schema design can follow the domains and identifiers already present in those APIs. Look for GET routes whose URL contains a unique identifier, such as `/pet/{petID}`; an object without an identifier in its listed routes may not be suitable to expose as an entity, though an incomplete OpenAPI spec could explain the omission. Entities identified by multiple URL parameters are also valid and should retain their existing domain definition. The excerpt begins an example of exposing an entity in a connector, but ends before providing the schema or implementation steps.

## Source excerpt

Since we first announced Apollo Connectors for REST at GraphQL Summit 2024, there has been an enormous amount of excitement from the community to dive in. I've been working with dozens of Enterprises on their use cases from breaking apart existing monoliths to integrating multiple production OpenAPI specification endpoints. In my work, there have been some patterns that have emerged and I wanted to start a new blog series that helps share the happy path to building faster.