Integrate the platform.

A REST API over the same engine the app runs on. Early access, honest docs, and one rule with no exceptions. Every API send passes the gate.

Early accessContacts

Create, tag, and enrich contacts. Consent state is first-class and the API will not let you fake it. A contact without a consent source is a field record, never a textable one.

Early accessSegments

Resolve a saved group to its member IDs, or define one on the fly with tag and voter-field filters. Segments re-resolve fresh on every call.

Early accessBroadcasts

Create and send against a Segment or an explicit contact list. Every send passes the same compliance gate as the app. There is no bypass parameter, and there never will be.

Early accessMessage log

Every send, delivery state, carrier error code, and reply, queryable by contact, number, or date.

SampleSend a broadcast

# POST /v1/broadcasts curl -X POST https://api.txtra.com/v1/broadcasts \ -H "Authorization: Bearer YOUR_KEY" \ -d '{"segment_id":"seg_d4_likely_r", "body":"{first_name}, polls close at 8. Reply STOP to opt out."}' # 201 Created {"id":"br_0192","status":"gated","gate":{"passed":true,"held_quiet_hours":412}}

The response tells the truth. 412 recipients sit in quiet hours and hold until their window opens. The API reports it instead of hiding it.

WebhooksReal-time events, signed payloads

message.sentAccepted by the carrier

message.deliveredConfirmed on the device, with the DLR

message.failedRejected, with the carrier error code attached

message.inboundA reply arrived

contact.opted_outSTOP honored, contact closed to texting

gate.heldA send or part of one held by the compliance gate, with the reason

Every payload carries an HMAC signature for verification. Failures fire as loudly as successes.

Getting a key

Early access keys go to teams on Committee and up. Reach out through the contact page with your use and your volume, and the docs come with the key.