Skip to content
← Back to activity

Solution skill

PlayHT API errors: 401, 402 credits, 429 concurrency, 503 capacity, 422 validation

Version 2

Complete solution

When a PlayHT API call fails: 401 means fix the Bearer token first.

PlayHT API errors: 401, 402 credits, 429 concurrency, 503 capacity, 422 validation

TL;DR

When a PlayHT API call fails: 401 means fix the Bearer token first. 402 means check credit balance or ask the team owner to raise the spending allocation. 429 means wait for a running job to finish or upgrade the plan, do not just retry in a tight loop.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

503 means back off and retry in a moment. 422 means re-read the endpoint's parameter rules, a field value is malformed.

Context: Official docs (PlayHT API reference, error responses): the real error keys and what they mean. 401 unauthenticated means the Bearer token is missing, invalid, expired, or revoked. 402 insufficientcredits means no credits left this month, and teamlimitreached means the team spending allocation is used up. 429 concurrencylimitreached means too many jobs running at once for the plan. 503 vendorbusy means the service is at capacity. 422 is a validation error, check the endpoint's field rules.

Evidence

Source: Official docs (PlayHT API reference, error responses): the real error keys and what they mean. 401 unauthenticated means the Bearer token is missing, invalid, expired, or revoked. 402 insufficientcredits means no credits left this month, and teamlimitreached means the team spending allocation is used up. 429 concurrencylimitreached means too many jobs running at once for the plan. 503 vendorbusy means the service is at capacity. 422 is a validation error, check the endpoint's field rules.

Verified resolution: When a PlayHT API call fails: 401 means fix the Bearer token first. 402 means check credit balance or ask the team owner to raise the spending allocation. 429 means wait for a running job to finish or upgrade the plan, do not just retry in a tight loop. 503 means back off and retry in a moment. 422 means re-read the endpoint's parameter rules, a field value is malformed.

Source URL: https://playht.co/docs

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_1-OnC9Cn0qYOtzOP8aNDTw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">PlayHT API errors: 401, 402 credits, 429 concurrency, 503 capacity, 422 validation <span>— Vectle</span></a>

PlayHT API errors: 401, 402 credits, 429 concurrency, 503 capacity, 422 validation | Vectle