Actionpackd

Messaging API · Official WhatsApp Tech Provider

WhatsApp,
from your backend.

Send templates, replies, and documents with an API key. We onboard the number and hold the Meta token. Receipts and customer replies come back to your webhook.

Custom pricing. Credits are sold. Meta message fees are paid by the customer directly to Meta.

POST /v1/messages
curl -X POST https://api.actionpackd.com/v1/messages \
  -H "Authorization: Bearer apk_test_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 7f3a2c1e" \
  -d '{"to":"9198XXXXXXXX","type":"template",
       "template":{"name":"order_shipped","language":"en"}}'

To +91 98XXX XXX21template: order_shipped

  1. queued

    10:42:01

    202 Accepted

  2. sent

    10:42:02

    Handed to Meta

  3. delivered

    10:42:03

    This one is billed

  4. read

    10:42:19

    Webhook only

Custom pricing. Credits are sold. Your own number on the WhatsApp Business API. Messaging API only. Studio is not included. Meta message fees are paid by you directly to Meta.

Talk to us

How it works

Three steps. Then it sends.

  1. 01

    Connect the number

    Onboard a WhatsApp Business number through our Meta Tech Provider flow. Meta approves the number. The token never lands in your repo.

  2. 02

    Mint a key

    Build against a free apk_test_ key. It does not count toward the allowance. Switch to apk_live_ once the number is live.

  3. 03

    Send and listen

    Post a template, or a text reply while the 24-hour window is open. Delivery receipts and customer replies arrive on one HTTPS webhook.

Reference

The whole API.

API reference
  • POST/v1/messagesTemplate, or text, interactive, or a document inside the 24-hour window.
  • GET/v1/messages/{id}Latest status for one send.
  • POST/v1/mediaUpload a PDF or Office file, or pass a public HTTPS link. Live keys only.
  • GET/v1/media/{id}Details for one uploaded file.
  • PUT/v1/webhookWhere replies and receipts go.
  • GET/v1/webhookThe URL currently set.

Base URL https://api.actionpackd.com/v1. Authorize with Bearer apk_live_… or apk_test_…. The OpenAPI 3.1 spec is at openapi.json.

Message fees

What you can send.

Meta prices each delivered message by category. We pass that rate through with no markup. A live key sends on your connected number. It does not change Meta’s category rate.

  • Utility

    Meta's India rate

    Order updates, shipping, appointment reminders, booking confirmations.

  • Authentication

    Meta's India rate

    OTP and login codes.

  • Authentication International

    Meta's international rate

    Charged only when Meta marks the message eligible.

  • Service

    Meta's India rate

    Support replies inside the 24-hour window, after Meta’s own 1,000 free service messages.

  • Marketing

    Meta's India rate

    Offers and campaigns. Meta prices this category. You pay Meta directly.

Engineering

You send the message. We run the WhatsApp side.

  • The Meta token

    We hold it. Your requests authenticate with an Actionpackd key, and the key is bound to your account, so payloads never carry a tenant id.

  • Retries

    Every send requires an Idempotency-Key. A timeout and a retry still produce one message and one charge.

  • Webhooks you can trust

    Inbound messages and status events are signed with HMAC SHA-256 in X-Actionpackd-Signature-V2. Check it against the X-Actionpackd-Timestamp and the raw body.

  • Your backend

    Your code sends and receives. Receipts and replies arrive on the webhook you set. Revoke a key and the next call fails.

Pricing

Custom pricing — Talk to us

Credits are sold. A live key sends on the number you connect. Usage shows on Billing.

Failed sends, inbound messages, and webhooks are not an Actionpackd charge. Meta message fees are paid by you directly to Meta.

Talk to us

One number.
Your backend.

Inbound messages and webhooks stay on your webhook. Meta message fees are paid by you directly to Meta.