Skip to main content

Overview

US carriers require a business and a texting campaign to be registered before a workspace can text from US numbers. In the Sendora app that is two screens. In the API it is one resource, SMS registrations, with a type of brand (your business) or campaign (what you text and how people opt in). The order is always the same:
  1. Check readiness and, if you want, ask for a quote.
  2. Create a brand draft, then submit it.
  3. Create a campaign draft for that brand, then submit it.
  4. Attach your numbers to the campaign.
Drafts are free and can be edited as often as you like. Submitting, the paid trust check and attaching numbers charge your wallet, and each one is quoted first. All of these calls need an API key with write access, except the reads.

1. Check readiness and a quote

The response has readiness (can you text yet, and next_step), options (the exact values the forms accept: entity_type such as company, sole_proprietor, nonprofit, government or public_company, vertical, use_case, opt_in_method and more) and, when you ask for one, a quote with total_due_now_cents. Use quote=campaign with use_case, or quote=vetting, for the other fees.

2. Create a brand draft

Send an Idempotency-Key of 8 to 255 characters, so a retry returns the same draft instead of making a second one.
A draft only needs type and entity_type. Use the values from options; a value that is not on the list answers 422. Fill the rest in with PATCH /sms-registrations/{id}, sending only the fields to change and type again. The response lists issues, the fields still missing or wrong, so you know what to fix before you submit.

3. Submit the brand

This charges the wallet for the registration fee. If the wallet is short, the call answers 402 and nothing is submitted. Read state and status_text on the brand to follow its review. A sole proprietor brand also needs its phone code: action: "send_code", then action: "verify_code" with pin. Other brand actions: vetting runs the optional paid trust check, and revet re-checks after you fix a problem.

4. Create and submit the campaign

Then submit it with { "type": "campaign", "action": "submit" }. Other campaign actions: appeal (with reason) after a rejection, clone to copy a finished campaign into a new draft, attach_numbers (with phone_number_public_ids) and detach_number (with phone_number_public_id). Attaching numbers charges the wallet.

5. Read, follow and clean up

A registration with attached numbers or an active campaign cannot be deleted. The error says why.

Assistants and the MCP

The Sendora MCP exposes the same steps. Reading and drafting are read_channels and edit_channels. The steps that charge the wallet (submit_sms_registration, request_sms_vetting, attach_sms_numbers) are in their own tool, run_channels, so an assistant has to ask for them on purpose. Read the quote and confirm with the person before it submits.

Errors