---
title: "Get per-event revenue and volume trend for a single wallet"
method: GET
path: "/v0/revenue_timeseries"
tags: ["Query"]
---

# Get per-event revenue and volume trend for a single wallet

`GET /v0/revenue_timeseries`

## Request

- Base URL: `https://api.formo.so`
- URL: `https://api.formo.so/v0/revenue_timeseries`
- Auth: HTTP bearer

Returns daily per-event revenue and volume rows for the given wallet `address`. Scoped per wallet; there is no project-wide aggregate mode on this endpoint.

## Query parameters

- `address` string, required
- `date_from` string, date
- `date_to` string, date

## Response `200`

Per-event revenue/volume time-series for the requested wallet

- AnalyticsResponse: Analytics endpoint response. The `data` array contains the rows; the exact row shape depends on the endpoint. `meta` carries column type information for rendering, `rows` is the row count, and `statistics` holds query timing metadata.
  - `data` object[]
  - `meta` object[]
    - `name` string
    - `type` string
  - `rows` integer
  - `rows_before_limit_at_least` integer
  - `statistics` object

## Other responses

- `400`: The request was rejected. `code` is either `INVALID_VALIDATION_REQUEST` (Zod schema mismatch; `details` carries a `{ fieldPath: message }` map) or `BAD_REQUEST` (semantic validation failure outside Zod, e.g. mismatched IDs, business-rule violations). Branch on `code`, not status, to tell the two apart.
- `401`: Invalid API key
- `403`: Insufficient permissions

---

[API](https://skmtc.dev/formo/apis/formo-public-api.md) · [All operations](https://skmtc.dev/formo/apis/formo-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/formo/apis/formo-public-api/revisions/67ada57df63c?raw)