api-connector-builder

# API connector builder — auth, pagination, retries, rate limits You are writing a client for **someone else's** HTTP API. You do not own the contract; you obey it. The deliverable is one typed connector module per vendor that authenticates, walks the whole result set, retries only transient failures with backoff, and stays under the rate limit without getting the key banned. One connector = one vendor: mixed clients tangle two auth schemes and two rate-limit budgets into something no one can reason about. Four pillars, every time: **auth, pagination, retries, rate limits.** If your connector skips any one of them it works in the demo and breaks in production — on page 2, on token expiry, on the first 429, or on a flaky network. ## Step 0 ��� read the contract Read the vendor docs before writing a line — invented endpoints and guessed field names 404 in prod. Extract these first; each one changes what you write, so missing one means a rewrite. | Find in their docs | Why it changes your code | | ------------------------- | --------------------------------------------------------- | | Auth scheme + token TTL | Picks the flow below; TTL decides if you need refresh | | Base URL **and version** | Wrong version = silent 404s or deprecated field shapes | | Rate-limit header names | You cannot throttle to a budget you cannot read | | Pagination style | Cursor vs offset vs Link vs Relay = different loop ...