Prepare your account
Sign in to APOB and confirm that you are using the account whose models, media, and credits you intend to use. Check the capabilities and access instructions provided by your integration before starting a workflow. Authentication identifies the account. It does not grant access to another account’s private assets or remove a workflow’s input and credit requirements.Choose the supported access method
Use the access method documented by your client or integration. API keys and
OAuth access tokens are separate credentials with different acceptance boundaries.
API keys
An API key belongs to an account. Its complete value is returned once when it is created; a later listing contains identifying metadata rather than the secret. Store the key securely when you receive it. If it is lost or exposed, replace it and revoke the old key. Keep keys in your server’s secret storage. Avoid placing them in browser code, public repositories, screenshots, or support messages.OAuth connections
An OAuth client directs you through a sign-in and consent flow. Review the client and the APOB account before approving the connection. The connected client then acts under that account’s authorization. If access expires or the connection is revoked, follow the client’s sign-in flow again. A successful login still requires the account to be active when an operation runs.Check access before generating
- Confirm the connected account and its available credits.
- Use your own private models and media, or references explicitly available to you.
- Check whether automatic credit reload is enabled before paid work.
- Keep credentials out of the workflow’s prompts and media.