Build on the Tech Pad API.

Quick start

From zero to a delivered WhatsApp message in four steps. Everything here also works inside the app’s Developers → Overview page, which tracks your progress.

Authentication

The API is authenticated with per-workspace API keys sent as a bearer token. Keys are created and revoked from Developers → API keys.

• Keys start with ttp_live_ and are scoped to one workspace.
• Create a separate key per integration — each key tracks its own last used timestamp.
• The full secret is displayed only once at creation; it cannot be recovered later. Revoke and recreate instead.
• Send the key in the Authorization header: Authorization: Bearer ttp_live_…

Send a message

Sends an approved WhatsApp template message to one opted-in recipient from a connected number in your workspace.

Request body

Example request

curl -X POST 'https://v1.thetechpad.com/functions/v1/api-send' \
  -H 'Authorization: Bearer ttp_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
  "phoneNumberId": "1122334455",
  "to": "15551234567",
  "template": {
    "name": "order_update",
    "language": "en",
    "parameters": ["Ava", "#4031"]
  }
}'

// JavaScript
const response = await fetch('https://v1.thetechpad.com/functions/v1/api-send', {
  method: 'POST',
  headers: { Authorization: 'Bearer ttp_live_...', 'Content-Type': 'application/json' },
  body: JSON.stringify({
    phoneNumberId: '1122334455',
    to: '15551234567',
    template: { name: 'order_update', language: 'en', parameters: ['Ava', '#4031'] }
  })
});

Webhooks

Outbound webhooks push message lifecycle events to your HTTPS endpoint in near real time. Manage endpoints from Developers → Webhooks — add, edit, pause, test and delete.

Events

• Endpoints must be HTTPS and reachable from the internet.
• Each endpoint subscribes to a chosen subset of events; every event fires with a JSON payload containing the message id and status.
• Use Test on an endpoint to send a sample delivery and verify your handler.
• Paused endpoints keep their configuration but stop receiving events.

Rate limits

Messages are sent at up to your plan’s package rate. Actual throughput can be lower when Meta applies messaging-tier, phone-quality or account-level limits. Messages remain queued safely rather than being discarded.

Every request counts toward your API-call quota and is recorded in the API logs with its status code and duration.

Logs & monitoring

Developers → Logs keeps two views:

• API logs — every API request: method, endpoint, HTTP status, template used and duration.
• Webhook logs — every webhook delivery attempt and its outcome.

Use them to debug failed sends, confirm webhook delivery and audit integrations end to end.

Errors

Successful requests return a 2xx status. Failures return a non-2xx status with a JSON body describing the problem:

{
  "error": "Template not approved",
  "hint": "Check the template status in Templates — only APPROVED templates can be sent."
}