The Playhub Seller API lets you work with offers and other documented seller operations from your own integration. You manage API keys in your Playhub profile.
Where to find your API key
1. Open your profile
Sign in to your seller account and select the profile icon in the top-right corner of Playhub.
2. Select API
On your profile, select the API tab next to Balance. You can also open your API settings directly while signed in.
The API Keys section is where you manage access. If you have not created a key, it shows No API keys yet.
3. Select Add
Select Add in the API Keys section to open Create new API key.
4. Review the validity period and create your key
The confirmation window states that the API key is valid for 6 months from the date of creation. When you are ready to connect your integration, select Create and complete the on-screen steps. Select Cancel to close the window without creating a key.
Store the generated key securely and use it according to the authentication instructions in the API documentation. Keep track of its expiry and arrange a replacement before your integration depends on an expired key.
Keep your API key private
Treat the key like a password. Do not include it in screenshots, support messages, shared documents, public repositories or client-side website code. Store it in a protected server-side configuration or secret manager.
If you suspect a key has been exposed, stop using it and review the controls in API Keys. Contact Playhub support if you need help securing access. Do not send the key itself to support.
Check the available operations
The reviewed documentation groups operations under Seller Offers, Seller Purchase Messages, Customer API, Seller Offer Bulk and Seller Offer Images.
Use the documentation for the method, path, authentication requirements and request fields. Do not assume that all actions available on the website have an equivalent API operation.
Build the smallest workflow first
Choose one documented operation.
Check its required fields and response format.
Confirm that the request targets the intended offer or order.
Start with a read operation where the documentation provides one.
Validate the result before adding writes or bulk changes.
Do not test create, publish or delete operations against real listings unless those changes are intended.
Plan for errors
Record the operation, time, response code and a safe reference for troubleshooting. Remove credentials and personal data from logs.
For failed requests, use Troubleshoot Seller API requests. The API documentation remains the reference for exact request syntax.