API Reference
Base path: /v1. Machine-readable spec: OpenAPI 3 (also GET https://api.wapedia.id/v1/openapi.json).
Spec version: 1.0.0.
Messages
POST /v1/messages
Send text, template, or media (after upload).
Header: Authorization: Bearer <API_KEY>
Example body (text):
{
"to": "6281234567890",
"type": "text",
"body": "Halo",
"phone_number_id": "1234567890"
}GET /v1/messages/:id
Outbound status (queued / sending / sent / failed + delivery).
GET /v1/messages/inbound · GET /v1/messages/outbound
List messages with limit / offset pagination.
Media
POST /v1/media
Multipart upload (file + mime_type). Maximum 16 MB.
POST /v1/media/resumable
Resumable upload (Meta handle) for supported files.
Subscription & usage
GET /v1/subscription·GET /v1/usage— plan status and fair-useGET /v1/wallet*/ Midtrans messaging top-up endpoints are not used for messaging billing in the current Tech Provider model (MESSAGING_WALLET_ENABLED=false). Schema remains for a later era; do not rely on them for message billing.
Other (summary)
Inbox: conversations, agents, contacts, chatbot rules, templates, analytics — see the full OpenAPI and backend README for the complete list.
Idempotency & queue
Outbound messages enter a worker queue; check status with GET /v1/messages/:id. Do not assume a synchronous send to Meta completes on a 202 response.