Best practices for integrating with the Pure API
This guide provides best practices and recommendations for developers integrating with the Pure API.
While we don’t publish specific rate limits, we do monitor API usage to ensure fair access for all users. If you’re planning to make a large number of requests, please contact us at [email protected] to discuss your needs.
The API returns standard HTTP status codes to indicate success or failure:
All error responses include an error
field with a description of what went wrong:
For endpoints that return multiple items (like /products
), we use offset-based pagination:
Spot prices for precious metals can change rapidly. When displaying spot prices to users, consider:
updatedAt
) to indicate when the price was last updatedmarketOpen
) to indicate if the market is currently activeWhen working with product data, keep in mind:
highestOffer
and lowestListing
fields represent the current market state and may be null if no offers/listings existpremiumCalculationType
field)We recommend testing your integration thoroughly before deploying to production. Use the following approach:
/protected
endpoint to verify authenticationIf you encounter any issues or have questions about the API, please contact our support team at [email protected].