Resilient REST Integration
Build an API integration around token reuse, bounded retries, idempotency and observable failures instead of happy-path calls.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
An integration that behaves predictably during auth expiry, throttling and partial failure.
Define idempotency semantics.
Know which calls can be safely retried.
Keep secrets outside versioned/public code.
Cache OAuth tokens
Reuse tokens rather than minting one for every API call.
Bound retries
Honor Retry-After and use exponential backoff instead of tight retry loops.
Design idempotent writes
Retries should not multiply business side effects.
Keep secrets out of code
Public repositories and Script Activities are not secret stores.
Use the troubleshooting runbook
Separate auth, request shape, rate limit and downstream failures.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.