Skip to main content
Start with the safe facts available in Yir Console: task ID, source, source path, status, timestamps, and the API key prefix used by the task.

​
Authentication failures

Check that:
  • the request uses Authorization: Bearer <YIR_API_KEY>;
  • the key is a Yir key, not an upstream provider key;
  • the key has not been revoked;
  • the secret does not contain surrounding quotes or whitespace added by your environment.
Never send the full API key in a screenshot, support message, log excerpt, or URL.

​
Admission failures

The current developer preview supports only the four exact GPT Image 2 routes shown in the Gateway reference. Unknown fields, unsupported models, unsupported paths, and arbitrary source forwarding are rejected rather than silently passed upstream. If a retry follows a timeout, reuse the original Idempotency-Key only for the same logical request with identical data. A new task needs a new key.

​
A task appears slow

Query the existing task ID. An active state, query timeout, or temporary transport error is not a confirmed generation failure. Avoid submitting a replacement task automatically because the upstream task may still finish and produce billing facts.

​
Evidence to collect

When escalating an issue through the support channel provided with your Yir account, include:
  • Yir task ID;
  • source (kie or apimart) and request path;
  • approximate UTC timestamp;
  • safe API key prefix;
  • HTTP status and public error code, if present.
Do not include the full API key, upstream credentials, raw files, or complete request and response bodies. Share prompt or media content only through an explicitly approved secure channel when it is necessary for the investigation.