Telkomsel · Rate Limits

Telkomsel Rate Limits

Telkomsel does not publish fixed numeric per-second or per-minute rate limits for its DigiHub APIs. Consumption is governed by plan-based metering instead - a one-time Sandbox trial quota per API, prepaid Quota packages whose calls are deducted per request and expire with the package validity period, and enterprise Tier/PAYU contracts where every call generates a CDR and is billed monthly. Requests beyond a retail user's purchased quota are rejected until a new package is bought; enterprise quota overruns are billed as excess usage. Each request must also carry a freshly computed x-signature header (SHA256 of API key + secret + epoch timestamp), which effectively requires per-request signing.

Telkomsel Rate Limits is the machine-readable rate-limit profile for Telkomsel on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Telecommunications, Indonesia, CPaaS, Rate Limiting, and Quotas.

4 Limits Throttle: not documented
TelecommunicationsIndonesiaCPaaSRate LimitingQuotas

Limits

Sandbox Trial Quota account
requests
one-time trial quota per API product
Cannot be repurchased once used; quota size varies per product.
Prepaid Quota Package account
requests
per purchased package
Deducted per call; retail users cannot exceed the purchased quota for the running month.
Enterprise Tier / PAYU Usage account
requests
unmetered (postpaid)
Every call generates a CDR billed monthly; excess usage over quota is charged rather than blocked.
Request Rate account
requests
not published
No numeric TPS/QPS caps are documented publicly for any DigiHub API.

Policies

Per-Request Signing
Every request must include an x-signature header computed as SHA256(API Key + Secret Key + current epoch timestamp), so signatures cannot be reused indefinitely.
Quota Exhaustion
Retail requests beyond the purchased quota are rejected until a new quota package is purchased; enterprise overruns are billed as excess usage.
Consent Gating
Subscriber-data products (location, scoring, identity) require a registered customer consent ID per query, independent of quota.

Sources