Best practices

The following are the recommended best practices for consuming YOM's Recommendations API efficiently and securely.

🔄 Consumption

Reuse the token during its validity window; do not request a new one for each request.
Pagination: go through the pages using page until hasNext is false. On the per-commerce endpoint you can raise limit up to 100; the domain endpoint returns 500 per page.
Incremental loads: sort by -updatedAt and filter by date on your side to pull only what is new.
Retries: on 429 and 5xx, retry with exponential backoff.

Store the client_secret in a secrets manager.
Do not store the client_secret in repositories, logs, tickets, or shared scripts.
Keep separate credentials per environment (Staging and Production).
Rotate the credentials at any suspicion of exposure by contacting YOM.

For any integration questions, access issues, or coordination of the move to Production, contact your counterpart team at YOM.

Version	Date	Change	Owner
1.0	July 2, 2026	Initial version of the integration contract.	YOM

Previous steps

Recommendations

</aside>

Next steps

</aside>