The operator platform,
ready as an API.
Hablame Colombia S.A. E.S.P. is a Colombian telecommunications operator with its own infrastructure. Our platform integrates through a single Bearer-authenticated HTTP surface, built for production.
# 1. Make the call
curl -i -H 'Authorization: Bearer hk_...' \
https://developers.hablame.co/api/v6/utilities/ping
# 2. Read the headers Hablame returns
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
RateLimit-Limit: 20
RateLimit-Remaining: 19
RateLimit-Reset: 47
RateLimit-Policy: 20;w=60;name="endpoint"
# 3. And the uniform envelope
{
"success": true,
"data": {
"pong": true,
"apiVersion": "v6",
"client": { "ip": "203.0.113.45" },
"account": { "id": 10000003, "status": "active" }
},
"meta": {
"requestId": "b9b1704baffab21150213c02fd853975",
"timestamp": "2026-06-04T19:43:59+00:00",
"responseTimeMs": 4.24
}
}Licensed operator
Services authorized by the Colombian Ministry of ICT.
CRC compliance
Subject to the regulation of the Communications Regulation Commission.
Our own infrastructure
We operate the network in Colombia, we do not resell it.
Hablame Colombia S.A. E.S.P.
Public utility company incorporated in Colombia.
What you can integrate today
32 documented endpoints across 9 services. Same authentication, same envelope and the same limit semantics for all of them.
Utilities
Diagnostic endpoints, available to any API key. Use them to verify your credentials are wired correctly.
Tools
General-purpose catalogs you can consume from your app. Available to any API key.
Number Insight
Resolves a phone number: country, line type, current carrier (porting-aware in Colombia) and area. One by one or in batches.
URL Shortener
Create and manage short links on your domains, and read their click analytics.
Text-to-Speech
Turn text into audio with natural voices, automatically reuse an identical audio already generated, and check the state of each request.
Call Blasting
Outbound voice calls with pre-recorded audio or text-to-speech, with configurable retries and per-attempt status.
Account
Billing summary for the organization: balance or credit, spending limits and movements. Sensitive financial data.
Organization
Organization profile, cost centers and users. Includes personal data.
Platform
Operational status of the services and a catalog of what your account has enabled.
A surface that respects your time
Stable error codes, sliding-window limits and a single envelope across every endpoint. Your integration looks the same on day 1 and on day 1000.
Bearer authentication
A single header: Authorization: Bearer hk_YOUR_API_KEY. No query parameters, no body fallbacks.
Predictable envelope
Every response is { success, data | error, meta }. One branch in your client, zero shape guessing.
Readable errors
Stable UPPER_SNAKE codes (AUTH_REQUIRED, RATE_TPS_EXCEEDED) with a direct link to the documentation on every response.
Honest limits
RFC 9598 RateLimit-* headers on every response and Retry-After on every 429. Your client paces itself without guessing.
What is not here yet
v6 ships endpoint by endpoint. These are announced but do not have a published contract yet, so you will not find them in the reference. The changelog announces them when they land.
/api/v6/sms/sendTransactional SMSComing soon/api/v6/whatsapp/sendWhatsApp BusinessComing soon/api/v6/email/sendTransactional emailComing soon/api/v6/callblasting/otpOTP by callComing soonReady to integrate the operator?
Start with the documentation, open the full reference or check the platform status.