Developer reference
This page consolidates reference-oriented workflows that support implementation and incident response.
Pillar and supporting pages
Pillar:
Supporting pages:
Reference coverage
- Authentication and API access patterns
- Link lifecycle and redirect behavior
- Event/webhook semantics
- Diagnostics and operational safeguards
Implementation example:
- During API integration, map each endpoint call to expected auth context and error handling.
- For webhook consumers, verify signature handling and idempotency before enabling production retries.
- During migration, run a small canary campaign that exercises click, redirect, app open, and webhook receipt before moving all traffic.
Production validation checklist
- Confirm each environment is using the intended base URL and API key scope.
- Validate redirect behavior for iOS, Android, and web fallback.
- Replay webhook samples and verify signatures, retries, and idempotency handling.
- Compare click/open metrics with expected campaign volume before launch.
- Record rollback conditions and owner contacts in the release runbook.
Troubleshooting reference issues
- Auth succeeds in one route but fails in another: check endpoint-specific permissions and key usage.
- Webhook payload mismatch: validate event version/schema and update parser contracts.
- Intermittent callback failures: inspect retry behavior, timeout budgets, and downstream availability.
- Event counts disagree across systems: reconcile event deduplication rules and timestamp windows before investigating data loss.
- Cutover regression after release: compare release-time config changes (keys, domains, path rules) against last known good baseline.