api-connector-builder

To add an API connector that matches a repo integration pattern, follow a step-by-step workflow to learn the house style and construct repo-native layers for config, client transport, mapping, registration, and tests. This ensures your connector mirrors layout, auth, and error handling exactly.

A repo-native API integration mirrors the target repo's existing layout, config schema, auth model, and registry wiring. You need this approach when adding one more integration without inventing a second architecture or generic HTTP clients across common connector styles.

No, you cannot use this approach to build a generic HTTP client. It specifically enforces standard workflows and guardrails for adding repo-native integrations that match the host repository's established patterns for layout, testing, and discovery.

The best way to match the host repo's config schema and auth model is to follow the provided reference shapes and workflows. Emulate the existing integration pattern exactly to construct aligned repo-native layers for config, client transport, and registration.

Yes, you need to follow the host repository's specific testing patterns. The process requires matching the target repo's integration pattern exactly, which includes mirroring its established tests and registry wiring to ensure a repo-native integration surface.

Your new API connector needs registry wiring to ensure a repo-native integration surface. Matching the target repo's established registration process allows the new connector to be discovered and function correctly within the host architecture.