momoGood developer platform · v1

Build with momoGood.
One ecosystem. Three product APIs.

Reach donors over SMS, run gala auctions, and pull unified analytics — each through its own purpose-built API. We keep the systems separate so each one stays great. We unify the developer experience so you only learn it once.

Start buildingAll systems operational

Choose a product

Each API has its own routes, auth model, and operational SLAs. Click in to browse the reference.

Product API · Messaging
Messaging

SMS broadcasts, two-way replies, subscriber lists, and keyword automation. Built for high-volume, compliant US/CA messaging.

POST/v2/messages
GET/v2/lists
PUT/v2/lists//keywords
Browse reference →Product API · Events & Auctions
Events & Auctions

Read-only export of event metadata, lot catalogs, guests, and committed purchases. Ideal for keeping a downstream CRM or warehouse in sync.

GET/events/v1/events
GET/events/v1/events//guests
GET/events/v1/events//purchases
Browse reference →Product API · Data Hub
Data Hub

Joined-up reporting across messaging and events. Donor profiles, audience insights, and scheduled exports — by SFTP, S3, or webhook.

GET/v1/reports/
POST/v1/exports
GET/v1/donors/
Browse reference →

How the platform fits together

Each product API is its own service with its own routes and SLAs. They share a developer portal, a single brand, and a small set of conventions — not a backend.

One developer ecosystem, multiple product APIs. Not a unified backend — each system below preserves its own routes, auth, and operational model.
Your app
Integration
CRM, warehouse, ETL, internal tool
Messaging
api.momogood.com/messaging/v2
HTTP Basic · REST
Events & Auctions
api.momogood.com/events/v1
Service user · Polling
Data Hub
api.momogood.com/datahub/v1
OAuth 2.0 · Scoped
3
Product APIs
58
Endpoints
99.97%
12-mo uptime
8
Webhook events

Get up and running

Provision credentials
Spin up a momoGood Messaging API key from My Account → API in the dashboard. Send it as the x-api-key header on every request.
Create an API key →
Send your first message
POST to /sms with a recipient, sending number, and message body. JSON in, JSON out, HTTPS only.
Send an SMS →
Close the loop with webhooks
Subscribe to delivery-status, reply-received, and invalid-phone events to confirm delivery, capture replies, and prune bad numbers.
Wire up webhooks →