Build with the Hablame v6 API.
REST endpoints for SMS, WhatsApp, e-mail and other messaging primitives. Bearer-authenticated, uniform JSON envelope, IETF rate-limit headers and a machine-readable error catalog, built for high-volume integrations.
Five reads that cover everything
Take them in order on day one; come back to them as reference.
Getting started
Mint a key, send a Bearer, read the envelope. First request in 30 seconds, common pitfalls and next steps.
Authentication
The Bearer scheme, key format (hk_ + a unique identifier), lifecycle, the auth pipeline, security best practices and incident response.
Response envelope
The uniform { success, data | error, meta } shape. How to branch your client. HTTP status vs error.code.
Rate limiting
Two-tier sliding-window guards, RateLimit-* headers (RFC 9598), Retry-After, and the recommended backoff strategy.
Caching
The X-Cache / X-Cache-TTL contract: how to tell a HIT from a MISS, when responses are real-time, and how long a cached snapshot is still good for.
Endpoints, errors and machine-readable spec
The reference is auto-generated from our OpenAPI spec. Every endpoint shows parameters, schemas, response codes with examples, code samples in 8+ languages, and a Try It panel that hits the live API with your bearer.
Every endpoint with a live Try-It panel.
Every error.code with cause and resolution.
The shortest path to a 200
If /utilities/ping returns 200, your wiring is sound. From there, browse the reference for module endpoints.
$ curl -H 'Authorization: Bearer hk_YOUR_API_KEY' \ https://developers.hablame.co/api/v6/utilities/ping
Read the full walk-through in Getting started.
What's documented today
v6 is rolling out endpoint by endpoint. Subscribe to the changelog for new releases.
/api/v6/sms/send
Coming soon
/api/v6/whatsapp/send
Coming soon
/api/v6/email/send
Coming soon
/api/v6/callblasting/otp
Coming soon