mym mym developer tools
mym developer tools built for mym CRM integration.
mym developer tools connect creator activity to a CRM, a warehouse, or your own product, with scoped keys and signed webhooks.
GET /v1/creators/cr_1042/subscribers
{
"data": [
{ "id": "sub_5512", "fan_id": "fan_88213", "status": "active", "plan": "monthly" }
],
"next_cursor": "eyJpZCI6InN1Yl81NTk5In0",
"has_more": true
}Which developer tools are included?
The primitives every mym developer tools integration relies on.
API keys and scopes
Project-level keys scoped to specific creators and specific data, so a key only reaches what it needs.
Account connections
A creator-controlled connection flow that links a mym account to your workspace without collecting passwords.
Creator profiles
Structured profile records covering plan tiers, bio fields, and public settings for each connected creator.
Fans and subscribers
Subscriber lists with plan, status, renewal date, and lifetime value fields for CRM sync.
Conversations
Private conversation metadata and message counts, useful for team inboxes and response-time tracking.
Private Media and MOD workflows
Follow Private Media and Media on Demand requests from creation to fan purchase.
PPV activity
Pay Per View sends, opens, and purchases, so campaigns can be measured per creator.
Tips and revenue
Tip events and revenue rollups across subscriptions, PPV, Private Media, and tips.
Private Shows
Scheduling and completion events for Private Shows, with fan and duration fields.
Media metadata
Titles, tags, and content flags for media libraries, without hosting the media itself.
Tracking links
Attribution links per campaign, mapped to downstream subscription and purchase events.
Notifications
A notification feed your product can mirror, so no fan activity goes unseen.
Webhooks
Signed event deliveries with automatic retries for subscriptions, purchases, and messages.
Audit logs
A record of every key, connection, and permission change across your workspace.
Usage monitoring
Request volume, error rate, and quota usage per API key and per creator.
How does mym CRM integration work?
mym CRM integration pushes subscriber and revenue records into the CRM your agency already runs, either directly or through a no-code workflow.
Two-way sync
Subscriber status changes in mym flow into CRM records, and CRM tags can inform future outreach.
Field mapping
Map mym fields such as plan, spend, and last activity to your CRM's own contact schema.
Segment export
Push a fan segment - for example lapsed subscribers - straight into a CRM list or campaign.
Revenue attribution
Attach subscription, PPV, and tip revenue to the CRM contact that generated it.
How do you call mym API from your stack?
Example requests across three common clients.
# Example request against the mym API
curl https://api.apimym.com/v1/creators/cr_1042/subscribers?limit=50 \
-H "Authorization: Bearer YOUR_API_KEY"Example endpoints, fields, and responses.
How does a webhook retry work?
If your endpoint does not acknowledge a delivery, mym API retries on a backoff schedule before marking the event failed.
Attempt 1 - 0s
subscription.created delivered to your endpoint, response timed out.
Attempt 2 - 30s
Retried after backoff, endpoint returned HTTP 500.
Attempt 3 - 5m
Retried again, endpoint acknowledged with HTTP 200.
Attempt 4 (example failure path)
If every attempt failed, the event would be marked failed and visible in the delivery log.
Retry timing for a failed delivery.
How does pagination work?
List endpoints use cursor-based pagination so large fan or event lists can be paged reliably.
GET /v1/creators/cr_1042/subscribers?limit=50&cursor=eyJpZCI6InN1Yl81NTEyIn0
{
"data": [ { "id": "sub_5512", "status": "active" } ],
"next_cursor": "eyJpZCI6InN1Yl81NTk5In0",
"has_more": true
}How are errors reported?
Errors use consistent HTTP status codes and a machine-readable error code, so retries and alerts can be automated.
HTTP/1.1 429 Too Many Requests
{
"error": {
"code": "rate_limited",
"message": "Too many requests for this API key. Retry after the window resets.",
"retry_after_seconds": 12
}
}How do audit logs and usage monitoring work?
Every workspace change and every request is recorded, so agencies can see who did what and how the integration is performing.
Audit logs
Key creation, scope changes, connection revocations, and team permission edits, each with an actor and a timestamp.
Usage monitoring
Dashboards for request volume, error rate, and remaining quota, broken down per API key and per creator.
Frequently asked questions
- Use cases include CRM sync, revenue dashboards, fan segmentation, and internal automations built on scoped API keys and webhooks.
- Yes. Webhooks deliver signed payloads with automatic retries.
- Yes. A sandbox with example data lets you build and test an integration before connecting a live creator.
- The model uses scoped API keys, encrypted tokens, and signed webhook payloads. See the authentication page for the full security model.
- No. mym CRM integration works directly or through a no-code workflow tool, so teams without engineering resources can still sync records.
- Yes. Event filters ensure a webhook endpoint or a CRM sync only receives the event types and creators it needs, reducing noise.
Build on mym today
Request early access to mym API and tell us what you want to build for your creators.