mym mym data export
Export your mym data, on your schedule.
mym data export pulls creator operations data out of mym into the format and destination your team already uses.
Datasets
Selected datasets: 1 - Last 7 days - All creators - Run once
Export history
No exports run yet.
What does an export request look like?
Example requests against the export endpoint.
# Create an export job
curl -X POST https://api.apimym.com/v1/exports \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"datasets": ["transactions", "subscriptions"],
"range": "last_30_days",
"format": "parquet",
"destination": "s3"
}'Create an export job with the datasets, range, format, and destination.
Example schema
The schema of the Transactions dataset.
| Field | Type | Description |
|---|---|---|
| transaction_id | string | Unique identifier for the transaction record. |
| creator_id | string | Identifier of the creator associated with the transaction. |
| fan_id | string | Identifier of the fan who made the purchase. |
| type | enum | subscription, ppv, tip, or private_media. |
| amount | decimal | Gross amount of the transaction. |
| currency | string | ISO currency code. |
| occurred_at | timestamp | When the transaction was recorded. |
Which datasets can be exported?
Every export can combine one or more of the following datasets.
Creators
Roster-level identifiers and profile attributes.
Fans
Fan identifiers and subscription status across creators.
Subscriptions
Plan, renewal, and cancellation records.
Transactions
Unified revenue events across subscriptions, PPV, and tips.
Tips
Individual tip events with amount and currency.
Messages
Conversation-level activity metadata, not raw message bodies.
PPV activity
Pay Per View requests, purchases, and outcomes.
Private Media requests
Private Media request status from request to delivery.
Media metadata
Titles, tags, and identifiers for exclusive content.
Tracking links
Link identifiers used for acquisition and attribution.
Attribution records
Matched clicks and downstream revenue signals.
Which export formats are supported?
Pick the format that fits your pipeline.
CSV
Simple, spreadsheet-friendly rows for quick review or manual import.
JSON
Nested records that map cleanly onto application data models.
Parquet
Columnar files sized for warehouse loads and large-scale analytics.
Where can an export be delivered?
Delivery destinations supported by the export builder.
Direct download
A signed file link generated on demand.
S3-compatible storage
Drop files into your own bucket on a schedule.
Google BigQuery
Load records directly into a BigQuery dataset.
Snowflake
Push tables into a Snowflake warehouse.
PostgreSQL
Write records into a Postgres database you control.
Webhook delivery
Send a signed notification when a scheduled export is ready.
Frequently asked questions
- The export builder lets you choose datasets, a date range, and a format, then run the export on demand or on a recurring schedule.
- Yes. Incremental exports mean scheduled runs only include new or changed records since the previous export, reducing duplicate processing downstream.
- The export covers conversation-level metadata such as timestamps and attachment flags, not raw private message bodies.
- CSV, JSON, and Parquet are the three output formats, so exports can suit a spreadsheet, an application, or a data warehouse.
- Destinations include Google BigQuery, Snowflake, and PostgreSQL alongside S3-compatible storage, direct download, and webhook delivery.
Build on mym today
Request early access to mym API and tell us what you want to build for your creators.