Coding & developmentIntegrationscode
Build an API integration with failure handling
Plans an integration around real schemas, authentication boundaries, retries and tests.
Ready to use
Prompt
Design and implement an integration between [SOURCE SYSTEM] and [DESTINATION SYSTEM] for [BUSINESS OUTCOME]. Use only the supplied API documentation and schemas; do not invent endpoints or fields.
First map required data fields, authentication method, pagination, rate limits, idempotency key, timeouts and error codes. Draw the one-way or two-way data flow and define the source of truth for each field. Handle retries with bounded backoff, duplicates, partial failures, stale credentials, logging without secrets and a reconciliation mechanism. Provide a dry-run mode before any production write.
Return the implementation plan, the smallest working code change, contract tests with mocked responses and a safe production acceptance checklist. Stop if required permissions or API facts are missing; identify the exact gap.
Documentation and schemas:
[API MATERIAL]