Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.momogood.com/llms.txt

Use this file to discover all available pages before exploring further.

Welcome to the momoGood Messaging API v3 (formerly the Tatango Message Sending API) — purpose-built for high-throughput omnichannel message sending across SMS, MMS, RCS, and WhatsApp. It’s optimized for performance-sensitive delivery workloads where speed, reliability, and channel breadth matter most.
Need to manage lists, subscribers, custom fields, webhooks, or scheduled broadcasts? Use the momoGood Messaging API v2 — the platform management API for momoGood Messaging.

​
Base URL

The momoGood Messaging API v3 is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP. All requests contain the following base URL: 
https://api.v3.tatango.com

​
Authentication

To authenticate you need to add the x-api-key header populated with your momoGood-provided API key shown in the GIF below. 
x-api-key: tatango_key_xxxxxxxxx

​
API Key Creation

You can create an API key by logging into the momoGood Messaging app and navigating to My Account -> API -> Create API Key. GIF showing the process of creating an API key in the momoGood Messaging app interface

​
Response Codes

The momoGood Messaging API v3 uses standard HTTP codes to indicate the success or failure of your requests. In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.
StatusDescription
200Successful request.
202Successful request, and the request is being processed asynchronously.
400Check that the request body’s parameters were correct.
403The API key used was invalid or missing.
404The resource was not found. Check the URL and HTTP method.
429The rate limit was exceeded.
5xxIndicates an error with momoGood servers. If you receive this error repeatedly, please contact support.
Specific error information is available for each request. This is shown on the request’s page. See the “response” sub-section at the bottom of the page for an example. Then, click the drop down to see the specific error response examples.

​
Rate Limit

The default rate limit is 10 requests per second. This number can be increased for trusted senders by request. After that, you’ll hit the rate limit and receive a 429 response error code. Learn more about our rate limits.