Partner earnings API

If you want to see your earnings on your own website or in a panel, connect the earnings API. It returns the same figures as your wallet on Millida: balance, amount available for withdrawal, and earnings for the selected period broken down by service: modpack subscriptions, hosting, donations, market, and others.

The API is read-only. You cannot withdraw money, change payout details, or pay for anything through it. The key only sees your wallet; you cannot access other people's data with it.

Key

The key is issued in the partner dashboard: Profile → section named after your studio → Earnings API. When issuing it, specify the IP address of the server from which requests will be sent. The key does not work from any other address, even if it is stolen.

• You can specify up to ten addresses or subnets. The subnet must be no wider than /24 for IPv4 and /48 for IPv6.
• Home and local addresses (127.0.0.1, 10.x, 192.168.x) are not accepted: you need the server's public address.
• The key is shown once. Store it on the server, in environment variables, or in a secrets store, and never expose it to the browser.
• You can have up to five active keys. If you lose a key or change servers, revoke the old key and issue a new one. A revoked key stops working immediately.

All endpoints are relative to https://api.millida.net/v2. The key is passed in the header:

Authorization: Bearer mek_live_…

Summary

GET /earnings-api/v1/summary?from=2026-09-01T00:00:00.000Z&to=2026-09-30T23:59:59.999Z

from and to are the period boundaries in ISO 8601 format. Both parameters are optional: without them, the period covers all time.

{
  "currency": "RUB",
  "balance": {
    "balanceKopecks": 1254000,
    "availableKopecks": 1204000,
    "withdrawableKopecks": 980000,
    "heldKopecks": 50000,
    "pendingPayoutKopecks": 0,
    "tradeHoldKopecks": 0,
    "tradeHoldReadyAt": null,
    "marketHoldKopecks": 0,
    "marketWithdrawalReadyAt": null
  },
  "period": {
    "from": "2026-09-01T00:00:00.000Z",
    "to": "2026-09-30T23:59:59.999Z",
    "earnedKopecks": 3108000,
    "heldKopecks": 0,
    "spentKopecks": 0,
    "toppedUpKopecks": 0,
    "paidOutKopecks": 2000000,
    "refundKopecks": 0,
    "netKopecks": 1108000,
    "operations": 142,
    "earnedBySource": [
      { "source": "catalog", "amountKopecks": 2950000, "operations": 131 },
      { "source": "hosting", "amountKopecks": 158000, "operations": 11 }
    ],
    "truncated": false
  },
  "subscriptions": {
    "subscribers": 14,
    "bundleSubscribers": 2,
    "packSubscribers": 12
  }
}

All amounts are in kopecks: 1254000 means 12 540 ₽.

The source values:

New values may be added over time. If you don't recognize a value, display it as is and don't treat it as an error.

Subscribers

GET /earnings-api/v1/subscriptions?from=2026-09-01T00:00:00.000Z&to=2026-09-30T23:59:59.999Z

How many people are currently playing your modpacks under a Millida subscription and what happened to subscriptions during the period. Subscribers are counted by active access, not by payments: a person counts as long as they can launch the modpack, including the three days after the payment date given for the retry charge. Access via your website's keys, team access, and one-time purchases do not count as subscriptions.

The API returns only numbers. You cannot find out who exactly is subscribed through it.

from and to define the period in the same way as in the summary. They affect only the period block; the total, active, renewal, and packs blocks always show the state at the time of the request.

{
  "from": "2026-09-01T00:00:00.000Z",
  "to": "2026-09-30T23:59:59.999Z",
  "generatedAt": "2026-09-28T16:30:00.000Z",
  "total": {
    "subscribers": 14,
    "bundleSubscribers": 2,
    "packSubscribers": 12
  },
  "partners": [
    {
      "partner": { "slug": "arcania-labs", "name": "Arcania Labs" },
      "active": {
        "subscribers": 14,
        "bundleSubscribers": 2,
        "packSubscribers": 12,
        "packSubscriptions": 12
      },
      "renewal": {
        "autoRenewing": { "bundle": 2, "packs": 12 },
        "canceledStillActive": { "bundle": 0, "packs": 0 }
      },
      "packs": [
        { "slug": "arcania", "title": "Arcania 1.4.3", "published": true, "activeSubscribers": 14, "viaPack": 12, "viaBundle": 2 },
        { "slug": "dread", "title": "DREAD - A Horror Survival Pack", "published": true, "activeSubscribers": 2, "viaPack": 0, "viaBundle": 2 }
      ],
      "period": {
        "newSubscriptions": { "bundle": 2, "packs": 12 },
        "canceled": { "bundle": 0, "packs": 0 },
        "expired": { "bundle": 0, "packs": 0 },
        "refunded": { "bundle": 0, "packs": 0 }
      },
      "truncated": false
    }
  ]
}

packs lists all your modpacks, including those with no subscribers.

bundle counts people, while packs counts subscriptions to individual modpacks. If a subscription is canceled, it appears in canceled on the day of cancellation, and in expired when the paid term ends.

Errors

Limits

A single key can send up to 30 requests per minute. The figures change along with payments, so there is no point in polling the API more than once a minute. It is better to cache the response on your server.

Example

curl -s https://api.millida.net/v2/earnings-api/v1/summary \
  -H "Authorization: Bearer $MILLIDA_EARNINGS_KEY"

curl -s https://api.millida.net/v2/earnings-api/v1/subscriptions \
  -H "Authorization: Bearer $MILLIDA_EARNINGS_KEY"