Get Mango Analytics Summary

Server URLloading...

GET

/api/v1/external/analytics/mangoes/summary

Send

Authorization

Header

Reports the shape of the authenticated creator’s Mango catalogue right now: how many Mangoes exist, how they split between paid and free pricing, how many of each are visible versus hidden, and which single Mango has the most active members.

Use this to render a catalogue overview. It answers "what does this creator sell?" — for "how much did this creator earn?", use Get Mango Revenue Analytics (GET /api/v1/external/analytics/mangoes/revenue) instead.

Scope. There is nothing to configure and no creator to select: the response always covers the whole catalogue of the creator you authenticated as. There are no query parameters, no date range, and no pagination; any query string you send is ignored. The counts are a snapshot of the present moment, not a time series — they are not affected by when a Mango was created or sold.

What is counted. totalMangoes, paid, and free cover the Mangoes the creator currently offers: deleted Mangoes are excluded, Mangoes whose availability period has already ended are excluded as of the instant you call, and the free platform-wide Mango that TagMango creates for every white-label account is excluded. Hidden Mangoes are counted, in the hidden bucket of their pricing type.

Most popular. mostPopular is ranked purely on current active member count, all-time and independent of revenue, and it applies a deliberately different filter from the counts: it skips the creator’s free sign-up service, which every member joins automatically and would otherwise always win, but it does not skip expired or hidden Mangoes. As a result mostPopular can name a Mango that totalMangoes does not count. When two Mangoes have the same active member count, which one is returned is undefined and may differ between identical requests.

Freshness. Analytics are served from TagMango’s reporting store rather than the live transactional one, so a Mango created, hidden, or deleted moments ago may not be reflected yet, and no staleness bound is guaranteed. The counts and mostPopular are also read separately rather than from one atomic snapshot, so a catalogue change made mid-request can leave the two marginally out of step. Both settle on their own; there is nothing to refresh.

Header Parameters

Response Body

curl -X GET "https://api-prod-new.tagmango.com/api/v1/external/analytics/mangoes/summary" \  -H "x-whitelabel-host: string"

{
  "totalMangoes": 24,
  "paid": {
    "total": 15,
    "live": 13,
    "hidden": 2
  },
  "free": {
    "total": 9,
    "live": 8,
    "hidden": 1
  },
  "mostPopular": {
    "_id": "64a1f0c2e4b0a1b2c3d4e5f6",
    "title": "Creator Growth Masterclass",
    "activeCustomers": 512
  }
}

{
  "code": 400,
  "type": "Bad Request",
  "statusMessage": "BAD_REQUEST",
  "success": false,
  "message": "Invalid request",
  "result": "Invalid request"
}

{
  "code": 401,
  "type": "Unauthorized",
  "statusMessage": "UNAUTHORIZED",
  "message": "Invalid token",
  "result": "Invalid token",
  "success": false
}

{
  "code": 403,
  "type": "Forbidden",
  "statusMessage": "FORBIDDEN",
  "errorCode": "WORKSHOP_MANGO_FORBIDDEN",
  "message": "You can not access this api with a TagMango account, only available for whitelabel hosts",
  "result": "You can not access this api with a TagMango account, only available for whitelabel hosts",
  "success": false
}

{
  "code": 429,
  "type": "Too Many Requests",
  "statusMessage": "TOO_MANY_REQUESTS",
  "message": "Request limit exceeded. try after 10 seconds",
  "result": "Request limit exceeded. try after 10 seconds",
  "success": false
}