Credits Management
Learn how to inspect and understand YODI credits.
Overview​
YODI credits are tracked per backend bucket, not per UI label. The current backend exposes four canonical buckets only: translation, audio, sms, and voice_call.
If a feature is not represented in quota and used, it does not have its own credit bucket in the current backend.
Checking Your Balance​
Endpoint: GET /credits/me
curl -X GET "https://admin.yodi.tg/api/credits/me" \
-H "Authorization: Bearer YOUR_API_KEY"
Response:
{
"message": "SUCCESS",
"error": false,
"data": {
"id": 1,
"quota": { "translation": 1000, "audio": 500, "sms": 200, "voice_call": 100 },
"used": { "translation": 145, "audio": 23, "sms": 12, "voice_call": 5 },
"source": "purchase",
"expiresAt": "2025-01-01T00:00:00.000Z"
},
"status": 200
}
Service Catalog​
Endpoint: GET /services
Returns the available credit-based services. In the current backend, that list is limited to translation, audio, sms, and voice_call.
Service Quota​
Endpoint: GET /services/{name}/quota
Check quota and usage for one of the four supported buckets.
curl -X GET "https://admin.yodi.tg/api/services/translation/quota" \
-H "Authorization: Bearer YOUR_API_KEY"
Credit Buckets​
| Bucket | Backend key | What it covers |
|---|---|---|
| Translation | translation | Translation requests |
| Audio | audio | Audio generation and speech workflows |
| SMS | sms | SMS delivery |
| Voice Call | voice_call | Voice call usage |
Notes​
- Chat, analysis, and other AI features are not separate credit buckets in the current backend.
- The keys shown above are the canonical keys returned by
GET /credits/me.
Low Credit Alerts​
Set up alerts in your dashboard to be notified when credits are low.
Buying Extra Credits​
Contact support or purchase through the dashboard for bulk credit packages.