API reference

TrustMRR API

Access verified startup revenue data programmatically. Browse startups, filter by revenue, MRR, asking price, growth, team size, funding status, and more — all backed by real payment provider data.

Authentication

Bearer token via API key. Generate keys from your developer dashboard.

Rate limits

Standard keys get 10 requests per minute. Premium keys get 60 requests per minute. Rate limit headers are included in every response.

Base URL

https://trustmrr.com/api/v1

1Get your API key

Go to the developer dashboard and create an API key. Keys start with tmrr_. Store it securely — you won't be able to see the full key again.

Acceptable use is required

Creating a key requires agreement to the API Acceptable Use Policy. Cloning businesses, rebuilding TrustMRR, bulk republication, unauthorized public SEO pages, abusive targeting, credential sharing, and access-control evasion are prohibited and can result in a permanent platform ban.

2Make your first request

Pass your key as a Bearer token in the Authorization header.

cURL

curl -s https://trustmrr.com/api/v1/startups \
  -H "Authorization: Bearer tmrr_your_api_key"

3Parse the response

Every response returns JSON with a data field containing your results. List endpoints also include a meta object for pagination.

Response shape

{
  "data": [ ... ],
  "meta": {
    "total": 142,
    "page": 1,
    "limit": 10,
    "hasMore": true
  }
}

RevenueCat data

New RevenueCat connections import all available daily revenue, transaction counts, MRR and active subscription history through its authenticated Charts API. TrustMRR calculates rolling 30-day churn from subscription and MRR movements. These are aggregate metrics; individual customer records are not imported by this connection.

Existing RevenueCat Legacy connections still use public Verified Metrics, with revenue tracking beginning roughly 30 days before connection. They remain supported until the owner migrates. Both methods use revenuecat as the payment provider in API responses. See the FAQ for connection, migration and replacement-key instructions.

Authentication

All API requests require a valid API key sent as a Bearer token. If the key is missing or invalid, you'll receive a 401 error.

Authorization header

Authorization: Bearer tmrr_your_api_key

Rate limiting

Every response includes rate limit headers so you can monitor your usage.

Header	Description
X-RateLimit-Limit	Maximum requests allowed per window (10 standard, 60 premium)
X-RateLimit-Remaining	Requests remaining in the current window
X-RateLimit-Reset	Unix timestamp when the window resets

Error codes

Status	Meaning
400	Bad request — invalid or missing parameters
401	Unauthorized — missing or invalid API key
403	Forbidden — API access disabled under the Acceptable Use Policy
404	Not found — the requested resource doesn't exist
429	Rate limited — slow down and check the rate limit headers
500	Server error — something went wrong on our end

Endpoints

GET/startups

Browse and filter all startups with sorting, pagination, and revenue filters.

View docs

GET/startups/{slug}

Get full details for a single startup including tech stack, cofounders, and extended metrics.

View docs