API documentation

The CRPRO Hub API sends and receives WhatsApp Business Platform messages per number, with signed webhooks, scoped API keys and complete isolation between organizations.

What you can do

• Channels — create, connect and manage an organization’s WhatsApp numbers, including coexistence onboarding through Meta’s Embedded Signup.
• Messages — send messages and read the history of each channel.
• Media — upload and download files attached to messages.
• Templates — register and read the templates approved by Meta.
• Webhooks — register endpoints and test event delivery.
• API keys — create, list and revoke scoped hub_pk_... keys.
• Subscription, usage and logs — read the contracted plan, the limits in force, message and media consumption, and the request audit trail.

How the API behaves

• Every successful response is wrapped in {"data": ...}, and every error in {"error": {"code", "message"}}.
• Asking for a resource that belongs to another organization returns 404, not 403 — the existence of someone else’s resource does not leak either.
• Sending a message requires an Idempotency-Key header. Replaying the same key with the same body returns the original response instead of sending twice.
• Sending returns 202: accepted and queued, not delivered. Final state arrives over the webhook.

Where to start

Start with the quickstart: it goes from zero to the first message sent. Then read authentication to choose the right credential, and webhooks to receive what happens after the send.

The complete endpoint-by-endpoint reference is currently available in Portuguese only, at /docs/referencia. The request and response examples there are language-neutral.