POST /user/subscription_tokens/{provider}/verify
Verify the stored token by using it.
TypeScript SDKThe npm client, generated from the API spec.Python SDKThe PyPI client, sync and async.
| Method | Path |
|---|---|
| POST | /v1/user/subscription_tokens/{provider}/verify |
Makes one minimal call on the exact runtime path, so a pass proves the token is what will pay. This is the gate on routing: success enables the token, failure disables it, so verifying a revoked token is how you stop it routing. A 200 with `ok: false` is the normal way a bad token is reported — it is an answer, not a transport failure.
Path parameters
providerenumrequired
Named for the harness the token drives, not the vendor behind it: a developer connects "my Claude subscription", and the path segment they type is `claude`.
one of
claudecodexcurl -X POST \
"https://api.ellipsis.dev/v1/user/subscription_tokens/{provider}/verify" \
-H "Authorization: Bearer $ELLIPSIS_API_KEY"import os
from ellipsis import Ellipsis
client = Ellipsis(api_key=os.environ["ELLIPSIS_API_TOKEN"])
result = client.user.subscription_tokens.verify(
"claude",
)
print(result)import { Ellipsis } from '@ellipsis-dev/sdk';
const client = new Ellipsis({
apiKey: process.env.ELLIPSIS_API_TOKEN!,
});
const result = await client.user.subscriptionTokens.verify('claude');
console.log(result);Request
Response
Example response · 200
{
"message": "string",
"ok": false
}