Skip to main content
Create and manage API keys in the YingTu console. Use a development key while integrating, and keep production keys separate. Every public YingTu endpoint in this documentation uses the same header:
A single convention means changing model IDs does not require an authentication rewrite.

​
Keep the key on the server

Load the key from a secret manager or server-side environment variable:
Do not commit the value, place it in mobile or browser-delivered code, include it in screenshots, or write complete request headers to application logs. Rotate a key after suspected disclosure and revoke keys through the authenticated console.

​
Using the interactive tester

The embedded Try it forms send browser-direct requests to YingTu. Use a short-lived development key, inspect the request before sending it, and remember that a generated cURL command can display the entered key. A successful request can incur a real charge.

​
401 versus 403

  • HTTP 401: the Authorization header is missing or the key is invalid.
  • HTTP 403 with insufficient_user_quota: the key is valid, but the account cannot fund the request.
  • A valid key can still be unable to use a model because of current account or group access. Check the console rather than repeatedly retrying the same call.

Send the first request

Use the key from a server-side cURL, Python, or Node.js request.

Handle authentication errors

Choose the correct action for 401, 403, and other failures.
Last modified on September 2, 2026