api-connector-builder

An API connector builder creates a repo-native integration surface by learning the host repository's existing connector architecture, then defining an integration-specific scope for auth flows, pagination, and core read/write operations that matches current conventions.

You implement pagination and retries by replicating the abstraction boundaries and error handling logic established by existing connectors in the repository, ensuring the new provider adheres to the house style rather than using generic vendor patterns.

The best way to define an integration-specific scope is to limit the implementation to only the surfaces the repository actually needs, such as the auth flow, core read/write operations, pagination, rate limits, and webhook or polling model.

Yes, the connector builder supports RBAC-aware security and config schema validation by ensuring these components match the repository's existing conventions rather than applying generic or vendor-derived configurations.

You write test fixtures by matching the repository's existing test style and conventions, ensuring the new provider's tests align with the house style discovered from at least two existing connectors in the codebase.