For event ticketing software, text buyers their ticket link, schedule changes and day-of alerts through one REST API, with each organizer on its own sub-account, number and registration. Keep these texts transactional, and keep promotion for the next event on a separate, consented list.

Ticket buyers want the text most when something changes: a venue move, a delay, a weather call. Organizers want to send it from their own name. Your platform sits between them, so what you build is partly a messaging feature and partly a guardrail. Read SMS API for SaaS platforms for the general model.

What to send, and when

MomentMessageType
After purchaseConfirmation and ticket linkTransactional
Day beforeEntry details, parking, start timeTransactional
Change or cancellationNew time, venue or refund stepsTransactional, urgent
Day ofGate opens, line statusTransactional
After eventThanks, feedback, next eventPromotional, needs separate consent

Mixing the last row into the others is the usual cause of filtering. See transactional versus promotional SMS.

Build it in four steps

  1. Create a sub-account per organizer with POST /v1/sub-accounts, using the sub-accounts docs.
  2. Register the organizer's business through the registration API. Most approvals take 2 to 7 days.
  3. Give the organizer a number, at $2 a month.
  4. Send with POST /v1/messages, setting consent_attested only when the buyer agreed to texts at checkout.

Plan for the registration wait. A new account can send up to 500 texts a calendar month until its registration is approved, and the limit lifts on approval, not on filing. Tell organizers to register early, well before a big on-sale.

Spikes

An on-sale and a last-minute change can both create a burst: thousands of texts in minutes. Per-second throughput is limited, and a fresh standard campaign gets about 1 to 4 segments a second, so a 20,000-text notice at an assumed 10 segments a second takes about 33 minutes. Queue sends and prioritize urgent changes over promotions. SMS queue design for platforms and throughput explained cover this.

Quiet hours

A late change can fall outside the recipient's allowed hours. An API text is held only if the window opens within 6 hours. Otherwise you get a 409 QUIET_HOURS_BLOCK, and your code sends again when it opens. A reply to a buyer who texted in the last 24 hours goes out at any hour. See handling the 409.

Cost

Each segment is $0.0075 plus $0.0045. A 5,000-ticket event sending three one-segment texts to each buyer is 15,000 segments, so 15,000 × ($0.0075 + $0.0045) in send charges. Assumptions, so use your own.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Frequently asked questions

Should the ticket be in the text? Send a link to the ticket, not the code itself, and keep the link short enough to stay in one segment.

What about transferred tickets? Text the new holder only if they've agreed to texts, and never reuse the old buyer's consent.

Can buyers reply? Yes. Route each reply to the right organizer by the number it was sent to.

Next step

Mock one event: purchase, reminder and a last-minute change, using a test key, and check that each text is one segment.