Documentation · REST endpoints

REST endpoints

Six REST endpoints. Cursor-paginated; JSON; UTF-8; all timestamps ISO 8601 in UTC.

Base URL

https://api.vera.cryptobriefing.com/v1

The endpoints

Method · Path	What it returns
GET /events	List recent events with filters. Cursor-paginated.
GET /events/{id}	A single event record by id.
GET /markets	List active markets we track. Filterable by venue, status, search.
GET /markets/{id}	A single market with its current snapshot.
GET /markets/{id}/events	Events that have related this market.
GET /export/events	Bulk CSV/JSONL export of events for a time window.

GET /events

List recent events with filters. The most-used endpoint.

Parameters

Parameter	Type	Notes
since	ISO 8601	Only events with `event.ingested_at >= since`. Maximum 30-day window for a single call.
until	ISO 8601	Only events with `event.ingested_at <= until`. Defaults to now.
relevance	csv	One or more of `low`, `moderate`, `high`. Filters by `aggregate_event_relevance.bucket`.
momentum	string	Set to `passed` to return only events whose related market carries a passing `momentum` tag (the higher signal-to-noise subset). See Schema.
market_id	string	Only events related to the specified market. May be repeated.
venue	string	One of `polymarket`. (`kalshi` ships with the future Multi-Venue tier.)
credibility_tier	csv	One or more of `t1`, `t2`, `t3`.
limit	integer	1–100. Default 25.
after	string	Cursor from a previous response's `next_cursor`.
order	string	`ingested_desc` (default) or `ingested_asc`.

Example

bashbash

curl https://api.vera.cryptobriefing.com/v1/events \
     -H 0 \
     -G --data-urlencode 1 \
        --data-urlencode 2 \
        --data-urlencode 3 \
        --data-urlencode 4

Response

jsonjson

{
  0: [
    { 1: { ... }, 2: [ ... ], 3: { ... } }
  ],
  4: 5,
  6: true
}

GET /events/{id}

Fetch a single event by its evt_ id. Idempotent: the same id always returns the same record.

bashbash

curl https://api.vera.cryptobriefing.com/v1/events/evt_2QPq6Bj2nKxH \
     -H 0

Returns the full event record (the schema at Schema), wrapped in a data envelope.

GET /markets

The registry of markets Vera tracks. Useful for discovery and for resolving market ids you find elsewhere.

Parameters

Parameter	Type	Notes
venue	string	Currently `polymarket`.
status	string	`active` (default) or `resolved`.
q	string	Free-text search against market title.
resolves_before	ISO 8601	Filter by close date.
limit, after, order	various	Same as `/events`.

bashbash

curl https://api.vera.cryptobriefing.com/v1/markets \
     -H 0 \
     -G --data-urlencode 1 \
        --data-urlencode 2

GET /markets/{id}

A single market with its current snapshot. Snapshot is refreshed roughly every 30 seconds upstream from Polymarket Gamma.

bashbash

curl https://api.vera.cryptobriefing.com/v1/markets/polymarket_0x1a2b... \
     -H 0

GET /markets/{id}/events

All events that have referenced this market. Cursor-paginated, same shape as /events.

bashbash

curl https://api.vera.cryptobriefing.com/v1/markets/polymarket_0x1a2b.../events \
     -H 0 \
     -G --data-urlencode 1 \
        --data-urlencode 2

GET /export/events

Bulk export for a defined time window. Capped at 10,000 rows per call; 50 calls per day.

Parameter	Type	Notes
since	ISO 8601	Required. Earliest ingestion timestamp.
until	ISO 8601	Required. Latest ingestion timestamp. Window cannot exceed 30 days.
format	string	`jsonl` (default) or `csv`. CSV is flattened (one row per event×market pair).
relevance, venue, credibility_tier	various	Same as `/events`.

bashbash

curl https://api.vera.cryptobriefing.com/v1/export/events \
     -H 0 \
     -G --data-urlencode 1 \
        --data-urlencode 2 \
        --data-urlencode 3 \
        -o vera-may.jsonl

Pagination

All list endpoints are cursor-paginated. The response includes next_cursor (string) and has_more (boolean). To get the next page, pass after=<next_cursor>.

Cursors are opaque; never construct them yourself.

Conventions

All responses are JSON. UTF-8.
All times are ISO 8601 with timezone offset, always UTC.
Unknown query parameters are silently ignored (forwards-compatible).
Every response includes rate-limit headers. See Rate limits.
Errors are returned with a 4xx/5xx status code and an error envelope. See Errors.