Add practical API integration guides - #50
Conversation
✅ Deploy Preview for legendary-lollipop-e2d131 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 588df800e2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d9c30e8b05
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Safe retry behavior depends on the result: | ||
|
|
||
| - Do not retry `400`, `401`, `403`, `404`, or `422` unchanged. | ||
| - Retry temporary network and `5xx` failures with progressive backoff and a maximum attempt count. |
There was a problem hiding this comment.
Avoid retrying requests with an unknown outcome
When an event POST reaches Hellotext but the client receives a timeout, connection failure, or late 5xx, following this blanket retry instruction can create the same event twice: the guide itself notes that the server may already have completed a timed-out request, while _i18n/en/developers/external-tracking.md states that most accepted tracking requests create a new event and the API has no general idempotency key. Distinguish failures known to occur before transmission from ambiguous outcomes, and apply the same correction to the mirrored Spanish guidance.
Useful? React with 👍 / 👎.
Summary
Why
The Developers section had endpoint reference material but needed practical implementation recipes that connect resource creation, customer identity, event tracking, retries, and verification into complete flows.
Validation
yarn buildgit diff --check origin/main...HEAD