Skip to main content

API troubleshooting and limits

Understand common API issues and where to check the technical details.

If an API workflow does not work as expected, first identify whether the issue is related to access, input, usage balance, rate limits, processing status, or the destination platform.

Common causes

API issues are often caused by:

  • Missing, inactive, or exposed API keys

  • Not enough API Units

  • Unsupported or inaccessible source videos

  • Upload files that do not meet current API requirements

  • Too many requests in a short period

  • Too many active processing tasks

  • A task that is still processing

  • A task that failed because the source content could not be processed

  • A destination platform rejecting, muting, blocking, or limiting the final content

Where to check first

Check these places before contacting Support:

  • API Dashboard for API key status, API Units balance, usage, and payment history

  • API Docs for current endpoint requirements, status codes, rate limits, and task behavior

  • Your own logs for request time, task ID, error message, and trace ID if available

  • Source platform or destination platform if the issue involves an imported link, export, or social publishing

Polling and task status

Many API tasks are asynchronous, so they may not return the final result immediately.

Your integration should follow the task status and result handling guidance in the API Docs. Help Center does not maintain separate polling examples, because those details can change with the API.

Rate limits and concurrency

WayinVideo may limit how many requests or active tasks your account can run at the same time.

For current limits, see the Rate Limits documentation. If your production workflow needs higher limits, contact WayinVideo.

Error details

For current HTTP status codes and error formats, see the Status Codes documentation.

When you contact Support, include:

  • Your WayinVideo account email or workspace

  • The API feature you were using

  • The approximate time of the issue

  • The task ID, error message, or trace ID if available

  • Whether the issue happens once or repeatedly

Related articles

Did this answer your question?