Wire Tatango into your campaign's own systems.
Two REST APIs and list webhooks let your team add opt-ins from your own forms, write opt-outs back to your CRM, send a text from your own code, and route replies. Scheduled Data Hub reports drop results into your warehouse. The full reference is at developers.momogood.com.
What campaigns build with it.
Six jobs a campaign, committee or agency data team usually automates first, with the endpoint that does each one.
Add opt-ins the moment a form is submitted
When a supporter opts in on your signup page, volunteer form or event RSVP, post them to a list with name, ZIP, tags and any custom field you keep, such as a VAN ID.
POST /api/v2/lists/{ID}/subscribers
Adding a SubscriberKeep opt-outs in sync with your CRM
Turn on unsubscribe events for each list and write every STOP back to your CRM as it happens. For a full reconcile, pull every unsubscribed number on a list.
GET /api/v2/lists/{ID}/subscribers/unsubscribed
Unsubscribed phone numbersSend one text from your own system
A canvass confirmation, a shift reminder, a reply to a form. The v3 API sends SMS or MMS to one number per request and returns a transaction ID. RCS messages to U.S. numbers fall back to SMS if they fail, though RCS is not yet approved for political senders.
POST /transactional_messages/send_sms
Messaging API v3Route replies to the people who answer them
The reply webhook carries the reply text, the message it answered and the subscriber's fields and tags, so your code can open a ticket or hand the conversation to a volunteer tool.
webhook: campaign_response
Creating a webhookCheck a keyword before it goes on a yard sign
Test whether a keyword is free on your short code before it is printed, then set it as a keyword on the list it should feed.
POST /api/v2/shortcodes/{ID}/test_keyword
Testing keyword availabilityLoad results into your warehouse
Data Hub delivers CSV reports daily, weekly or monthly: opt-ins and opt-outs, recipients, clicks, replies, and donations attributed to a message. They land in Amazon S3, Google Cloud Storage, SFTP or email.
Scheduled reports, turned on through your Customer Success Manager
Data Hub reportsTwo APIs, one account.
v2 manages lists, subscribers, custom fields, tags, keywords, webhooks and list broadcasts. v3 is the sending API for one message at a time across SMS, MMS, RCS (not yet approved for political senders) and WhatsApp. Both use API keys from your Tatango account.
Lists, subscribers and webhooks
- Base URL
- https://app.tatango.com/api/v2
- Auth
- HTTP Basic: your login email as the username, your API key as the password
- Format
- JSON over REST
- Pagination
- 10 results per page by default; per_page up to 1,000
- Rate limit
- 1,200 calls per hour. Your account manager can raise it
- Webhooks
- Per list: subscribe, unsubscribe, message sent, reply, cleaned
One message per request
- Base URL
- https://api.v3.tatango.com (HTTPS only)
- Auth
- x-api-key header. Create a key in the app under My Account, API
- Channels
- SMS and MMS to U.S. and Canadian numbers; RCS to U.S. numbers with SMS fallback, not yet approved for political senders; WhatsApp templates with SMS fallback
- Response
- 202 Accepted with a transactionId
- Rate limit
- 10 requests per second and 10,000 per day per key. Higher limits for trusted senders on request
- Webhooks
- Delivery status, reply received, invalid phone
Two requests, as the docs write them.
Swap in your list ID, login email and API key. Phone numbers go in as ten digits with no country code.
curl "https://app.tatango.com/api/v2/lists/LIST_ID/subscribers" \
-X POST \
-u "you@yourcampaign.com:YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"subscriber": {
"phone_number": "2065551111",
"first_name": "Dana",
"zip_code": "98101",
"tags": "volunteer,precinct-12"
}}' Adding a Subscriber reference curl "https://api.v3.tatango.com/transactional_messages/send_sms" \
-X POST \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phoneNumber": "2065551111",
"webhookUrl": "https://example.com/tatango-events",
"content": "Confirmed: Saturday canvass, 10am."
}'
# 202 Accepted
{ "message": "Request accepted, sending message to recipient",
"transactionId": "019687e1-1b54-70f4-a68a-60af7fa776f4" } Send an SMS Message reference Set per list with a callback URL. An unreachable callback is retried 10 times, then dropped.
Webhook event payloadsPosted to the HTTPS webhookUrl you pass on each send request.
v3 webhook referenceCheck for a connector before you write code.
The platforms most campaigns run on already connect to Tatango without a line of code. Build against the API for what they do not cover.
ActBlue
See every ActBlue donation in Tatango within minutes, and connect each gift to the text message that inspired it.
WinRed
Turn WinRed donors and leads into opted-in SMS subscribers within minutes, and connect every gift back to the message that inspired it.
NGP VAN
Connect NGP VAN form opt-ins and donations to Tatango so campaigns and committees can mobilize supporters and tie fundraising back to texting.
Anedot
Turn Anedot donations and action page submissions into opted-in SMS subscribers in Tatango.
Zapier
Connect Tatango to thousands of apps. Trigger SMS sends from form submissions, donations, CRM updates and more.
SFTP
Move supporters from a daily file drop into Tatango lists, with no manual uploads from your team.
Consent rules apply to your code too.
The API does what you tell it. Whether a number may be texted is still a question of how and when that person opted in, and keeping that record is your committee's job.
Only post numbers that opted in
The add-subscriber endpoint can skip the double opt-in step with bypass_opt_in_process. Use it only when you hold the opt-in record from your own form. A purchased list or a voter-file phone column is not a record of consent to texts.
Respect opt-outs across systems
Posting a number that unsubscribed from a list starts the resubscribe process for it. Check the unsubscribe events and the unsubscribed list before a sync re-adds someone who replied STOP.
Landlines are rejected
A landline or unreachable number returns a 422 with "Bad phone number: landline or unreachable carrier". Log it and stop retrying it.
A named Customer Success Manager for every account.
Every account gets a Customer Success Manager you can call, who partners with your team from onboarding through election night to build effective campaigns and raise the ROI on every send. Our CS team is the part of Tatango customers review highest.
Fast, guided onboarding
Your CSM gets your numbers registered, integrations connected, and first send out on your timeline, then stays on the account.
Number registration · Integrations · First send
Campaign strategy and compliance guidance
Message cadence, segment strategy, ask amounts, consent and opt-out setup, quiet hours, and registration, reviewed with you before launch and as the cycle changes. Guidance, not legal advice.
Cadence · Segments · Consent · Carrier rules
Campaign-cycle coverage
Extended support through deadline nights, debates, and election week, with a person who already knows your program picking up the phone.
Deadline nights · Debates · Election week
Common questions
Where is the API documentation? +
At developers.momogood.com, under Messaging. It has the v2 and v3 API references, webhook payloads, the Data Hub report fields, and the Salesforce Marketing Cloud setup guide.
How do we get an API key? +
Log in to the Tatango app and go to My Account, then API, then Create API Key. The v3 API takes the key in an x-api-key header. The v2 API uses HTTP Basic auth with your login email as the username and the key as the password.
Which API should we use, v2 or v3? +
Use v2 to manage lists, subscribers, custom fields, tags, keywords and list webhooks, and to send a message to a whole list. Use v3 to send one SMS, MMS, RCS or WhatsApp message to one number per request, with a delivery webhook for each send.
What are the rate limits? +
v2 allows 1,200 calls per hour, about one every 3 seconds. v3 allows 10 requests per second and 10,000 per day per API key. Both return a 429 when you go over. Ask your account manager or support if your use case needs more.
What happens if our webhook endpoint is down? +
A v2 list webhook is retried 10 times when the callback URL cannot be reached. After the tenth attempt it is not sent again, so reconcile with the API after an outage.
Can we get data out without writing code? +
Yes. Data Hub sends scheduled CSV reports, including opts, recipients, clicks, replies and attributed donations, to Amazon S3, Google Cloud Storage, SFTP or email. Ask your Customer Success Manager or support@tatango.com to turn them on and add your own custom fields, such as a VAN ID.
Can the API add supporters from a voter file? +
The API adds whatever numbers you post, so the question is consent, not code. Add numbers only for people who opted in to texts from you, and keep the record of how and when.
Trust that holds up to scrutiny.
Security, privacy, and compliance controls audited independently and built into the platform, so a committee treasurer, compliance counsel, or data lead can sign off quickly.
SOC 2 Type II
Independently audited security controls, with a clean opinion for 2025.
HIPAA
HIPAA-ready controls and BAAs for organizations that handle protected health information alongside political or advocacy work.
TCPA controls
Consent capture, automatic opt-out handling, list scrubbing before every send, and exportable audit history.
10DLC and short code registration
Registered with The Campaign Registry and carriers before your first send.
Encryption and access
Encryption in transit and at rest, role-based access, and audit logging on every action.
Privacy and data handling
Data retention controls, isolated opt-out lists per organization, and a published trust center.
See it on your program.
A 30-minute walkthrough tailored to fundraising, mobilization, or both.