API Reference

Reveal an API key

Reveal an API key. Fields and permissions follow this gateway implementation.

POST https://api.tu-zi.com/api/token/{id}/key
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Reveal an API key

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/api/token/{id}/key

Transport: json

Use an account system token and New-Api-User (account ID), or a valid site login session. Manage system tokens in account settings. Inference API keys are not substitutes; keep system tokens out of frontend code.

Authorized OAuth access tokens are also supported; required scope: token:reveal

Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID

Before calling

  • Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
  • Python / JavaScript read SYSTEM_TOKEN (account system token) and USER_ID (account ID) from the environment. In cURL, replace YOUR_SYSTEM_TOKEN and YOUR_USER_ID.

Path parameters

FieldTypeRequiredDescription / constraints
idintegerYesToken ID belonging to the current account. Example: 123

Response fields

FieldTypeDescription / constraints
successbooleanBusiness success; do not rely only on HTTP status.
messagestringResult or error message.
data.keystringFull secret; do not log or paste into chats.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "success": true,
  "message": "",
  "data": {
    "key": "YOUR_API_KEY"
  }
}

Errors and retries

Check HTTP status and success. Business validation errors may return HTTP 200 with {"success":false,"message":"..."}; some include error.code. Authentication may return 401/403 and rate limiting 429. HTTP 200 alone does not guarantee success.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.