Skip to content

Add practical API integration guides - #50

Merged
pelcasandra merged 2 commits into
mainfrom
codex/api-integration-guides
Aug 7, 2026
Merged

Add practical API integration guides#50
pelcasandra merged 2 commits into
mainfrom
codex/api-integration-guides

Conversation

@pelcasandra

Copy link
Copy Markdown
Member

Summary

  • add bilingual step-by-step guides for product and variant synchronization, order lifecycle tracking, coupon redemption tracking, and custom integration troubleshooting
  • explain the boundary between public catalog synchronization and live inventory availability
  • add the guides to Developers navigation and cross-link them from the overview, custom-store setup, and external tracking guides

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 build
  • verified all eight English and Spanish generated routes
  • verified local links in every new page
  • verified referenced API anchors against the current public API reference
  • git diff --check origin/main...HEAD

@netlify

netlify Bot commented Aug 7, 2026

Copy link
Copy Markdown

Deploy Preview for legendary-lollipop-e2d131 ready!

Name Link
🔨 Latest commit d9c30e8
🔍 Latest deploy log https://app.netlify.com/projects/legendary-lollipop-e2d131/deploys/6a76118c3ada5d00080b92af
😎 Deploy Preview https://deploy-preview-50--legendary-lollipop-e2d131.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread _i18n/en/developers/orders-with-api.md Outdated
@pelcasandra
pelcasandra merged commit fdfefa1 into main Aug 7, 2026
6 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant