When an API request fails, keep the response and compare your request with the current Playhub API documentation. Avoid automatic repeated writes until you understand the result.
Check authentication
Make sure the integration is using the intended key, that its expiration is appropriate and that you are sending authentication in the documented format.
Do not paste the key into a support message or screenshot. If a secret has been exposed, use the available key-management controls and ask support for guidance if needed.
Check the operation and fields
Confirm the HTTP method, endpoint and required fields against the documentation. Check the identifiers and data types, particularly when updating an existing offer or attaching images.
An example from an old integration may no longer describe the operation you are calling.
Check whether the action already happened
A timeout does not always explain the final state of a write request. Before retrying an operation that creates or changes something, inspect the affected offer or order through the available read operation or website.
Do not assume that repeating a request is safe or that the API automatically prevents duplicates.
Send a useful support report
Include the operation, request time with time zone, response status, relevant error text and a sanitized request example. Explain the expected and actual result.
Exclude API keys, passwords, delivered credentials and unnecessary buyer information. If you need help with access setup, see Get started with the Seller API.