# get_site_payment_analytics

Source: https://modulify.ai/docs/api/payments/get-site-payment-analytics

Totals the payments a site took over a period, per currency, with refunds, disputes and failed payments.

- Title: Total the payments of a site over time
- Scope: `config:read`
- Access: Read only
- Endpoint: `POST /v1/get_site_payment_analytics`

> **Payments are in alpha**
>
> Payments are open on a few sites while we test them. On any other site this tool is refused with `Payments are not available on this site yet!`. To ask for access, use the [support chat](https://modulify.ai/docs/reference/support-chat).

Totals the payments a site took over a period, the way the **Analytics** sub-tab of its **Payments** tab does. `currencies` holds one entry per currency, with `Payments` (how many went through), `PaidCents` (what they took, in the currency's smallest unit), `RefundedCents` and `Refunds`, `Disputes`, and `Failed`, the attempts that did not go through, which never count as paid. `primaryCurrency` is the currency with the most payments, and `series` charts it, one entry per hour, day or month as `interval` says, with zeros where nothing was paid. Leave `period`, `from` and `to` out for the last 30 days. Payments stay in the list for 1 year, so a longer window only totals the ones still kept. Only the workspace owner can read them, so any other caller is refused.

## Request

Call it with a `POST` to `https://api.modulify.ai/v1/get_site_payment_analytics`, sending the inputs below as a JSON object. The token needs the `config:read` scope.

It only reads and changes nothing, so retrying it is safe.

```bash
curl -X POST https://api.modulify.ai/v1/get_site_payment_analytics \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID"}'
```

Over MCP, the same method is the [get_site_payment_analytics tool](https://modulify.ai/docs/mcp/payments/get-site-payment-analytics).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site id. |
| `period` | string | No | One of `day`, `24h`, `7d`, `30d`, `90d`, `12mo` or `all`. `day` is today so far, from midnight UTC, `24h` is the current hour and the 23 before it, `7d`, `30d` and `90d` are the last 7, 30 and 90 days counting today, `12mo` is this month and the 11 before it, and `all` reaches back to the first record. Defaults to `30d`. |
| `from` | string | No | The first day of a custom range as `YYYY-MM-DD` in UTC, sent together with `to`. |
| `to` | string | No | The last day of a custom range as `YYYY-MM-DD` in UTC, included in the range and sent together with `from`. |

## Response

Every call answers with the [JSON envelope](https://modulify.ai/docs/api/requests-and-responses#the-response) of `success`, `message`, `data`, `code` and `version`. `data` holds the result described above, and on a method that returns a total, `count` carries it. The [response headers](https://modulify.ai/docs/api/requests-and-responses#headers-on-every-method-call) carry the call's `X-Request-Id` and what is left of your per-minute budget in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. [Errors](https://modulify.ai/docs/api/errors) explains every status code a call can answer with.