Supporting integrations and APIs
Support the connections between systems: read a request and its error body, recognize authentication and permission problems with API keys and OAuth tokens, handle rate limits with Retry-After and backoff, prevent duplicates with idempotency keys, spot incomplete syncs caused by pagination, and receive webhooks safely. Never put keys or tokens in tickets.
- Level
- Intermediate
- Length
- About 55 minutes
- Contents
- 3 lessons · 1 video · final exam
- Status
- Published · updated 1 Oct 2026
Skills you'll practise
- Identify the parts of an API request and response and read a Problem Details error body
- Diagnose integration failures caused by expired or revoked tokens, missing scopes and leavers' accounts
- Explain rate limiting, Retry-After and exponential backoff with jitter, and recognize a retry storm
- Explain how idempotency keys prevent duplicate records when requests are retried
- Describe safe webhook handling: signature verification, quick 2xx acknowledgement, queuing and duplicate detection
Course outline
- 1.Supporting integrations and APIsVideo · 3 min
- 2.Anatomy of an integration callLesson · 17 min
- 3.Keys, tokens and permissionsLesson · 18 min
- 4.Rate limits, retries, duplicates and webhooksLesson · 20 min
- 5.Supporting integrations and APIs: knowledge checkKnowledge check · 19 questions
- 6.The integration that stopped overnightScenario
- 7.Final exam9 questions · passing it completes the course, so people who already know the material can test out
Sources it draws on
The lessons and questions are written from these references, so learners can go back to the original.
- IETF RFC 9110: HTTP Semantics (section 10.2.3, Retry-After)
- IETF RFC 6585: Additional HTTP Status Codes (section 4, 429 Too Many Requests and Retry-After)
- IETF RFC 9457: Problem Details for HTTP APIs (type, title, status, detail, instance)
- IETF RFC 6749: The OAuth 2.0 Authorization Framework (access tokens, refresh tokens, scope)
- Google Cloud Storage documentation: Retry strategy (exponential backoff with jitter; retry transient errors; idempotency)
- Stripe API reference: Idempotent requests (example of an idempotency key implementation)
- GitHub Docs: Best practices for using webhooks (respond with 2XX within 10 seconds, webhook secret, X-GitHub-Delivery, redelivery)
- General technical-support practice
See it with your own jobs and topics
Tell us about your team and we'll walk you through setup, from choosing jobs to your first skills check.