This callFreeNever billed, so safe to call often
Credential testFreeA wrong key answers 401
SuccessExample response envelope
{
"ok": true,
"request_id": "req_…",
"data": {
"kind": "me",
"user_id": "user_…",
"credits": 250
},
"usage": {
"credits_spent": 0,
"balance": 250,
"bytes": 0
}
}Account endpoints
- GETCredit BalanceValidate a TranscriptFetch API key and read the account's remaining credit balance over REST, free, with curl, Python and Node examples.
- GETHealth CheckTranscriptFetch's public liveness probe for uptime monitoring: 200 whenever the API is serving, no API key and no credits, with curl, Python and Node examples.
Frequently asked questions
Does checking the balance cost credits?
No. This call is never billed.
How do I test a key without spending credits?
Call this endpoint with it. A valid key answers 200 with the balance; a wrong one answers 401. The n8n node tests credentials this way.
Where else can I see credits spent?
Every billed response carries a usage block with credits_spent and the balance after the call.