GET /v1/balance
Read the selected owned resource or current workflow state without starting a new generation.
Request example#
curl 'https://platform.tongai.io/v1/balance' \ -H "Authorization: Bearer $TONG_API_KEY"Configuration
curl --versionAuthentication#
Use a server-side API key for your account, or OAuth for each customer’s account. Never send keys in prompts or tool arguments.
balance:readParameters#
No parameters are required.
Request body#
This endpoint has no request body.
Response schema#
{}HTTP 200
application/jsonobjectErrors and limits#
| HTTP | Error | Recovery |
|---|---|---|
400 | Invalid requestREQUEST_INVALID | Correct the fields identified by the error before trying again. |
401 | Invalid credentialCREDENTIAL_INVALID | Check the credential, its expiry and whether it has been revoked. |
402 | Insufficient creditsINSUFFICIENT_CREDITS | Add credits to the account that owns the credential, then continue the saved work. |
403 | Permission deniedSCOPE_REQUIRED | Use a credential with the required scopes and access to the selected resource. |
404 | Resource unavailableRESOURCE_UNAVAILABLE | Check the resource ID and that it belongs to the authorized account. |
409 | Intent conflictIDEMPOTENCY_CONFLICT | Reuse an intent only with its original request. Use a new UUID for a different action. |
429 | Rate limitedRATE_LIMITED | Wait for Retry-After before retrying the same intended request. |
503 | Temporarily unavailableDEPENDENCY_UNAVAILABLE | Wait for Retry-After and retry with the same intent. Check the saved operation after a timeout. |
AuthenticationAPI keys charge the account that owns the key. OAuth lets each connected user use their own credits.Errors and rate limitsUnderstand error responses, retry safely and recover from failed generations.Requests and logsAn accepted request is not a finished generation. Track the saved job until its output is ready.