Build with the TechUpServices v1 API

Available operations

• POST /api/v1/messages/send sends text or approved template messages to up to 50 parsed recipients.
• POST /api/v1/broadcasts queues a background campaign and returns its broadcast and run identities.
• GET /api/v1/broadcasts/:id reads account-scoped campaign, run, aggregate, recipient, and filtering data.
• Use same-origin /api/v1 paths. Do not hard-code an unverified documentation hostname.

Quick start

1. Step 1

   Create an API key

   Open Developer API at /dashboard/api, enter Key name, create the key, and copy the plain value once.

2. Step 2

   Authenticate

   Send Authorization: Bearer <key> or X-API-Key with the exact required scope.

3. Step 3

   Make one bounded request

   Start with one reviewed recipient or a dry reviewed campaign source and inspect the complete response.

4. Step 4

   Store response identities

   Persist request_id and any broadcast_id, run_id, message_id, and client_reference needed for reconciliation.

Acceptance is not delivery

A direct result marked accepted or a broadcast response marked queued confirms only the current application/provider stage. Delivery and read evidence arrive later. Inspect each direct-send result and poll broadcast detail conservatively.

Integrate safely

• Treat v1 mutations as non-idempotent and do not automatically retry unknown outcomes.
• Throttle callers and back off explicit rate_limited recipient results; no numeric application rate-limit contract is published.
• Keep keys secret, use E.164 recipient data, preserve consent, and correct permanent sender, template, policy, or recipient errors before retrying.