​
Option 1 — import the OpenAPI specification

The specification is the source of truth and always matches the playground.
1

Get the spec

apps/docs/api-reference/openapi.json in the repository.
2

Import it

Postman → Import → File → select openapi.json.Choose “Generate collection from OpenAPI”. Every endpoint arrives with its parameters, enums, and descriptions.
3

Set the baseUrl variable

Postman creates a baseUrl variable from the servers block. Set it to http://localhost:3101, or to your own deployment.
Prefer this over the static collection below. Importing the spec means your collection updates when the API does, instead of drifting.

​
Option 2 — the committed collection

apps/docs/api-reference/postman-collection.json is a Postman v2.1 collection covering the same five endpoints, with a baseUrl variable defaulting to http://localhost:3101. Postman → Import → File → select it.

​
Variables

​
No auth to configure

Every request in the collection is unauthenticated — the public surface takes no credential. If you extend the collection to the self-hosted or enterprise surfaces, add:
Store keys as Postman environment secrets, not collection variables. Collection variables are exported with the collection and are easy to share by accident.

​
A test worth adding

Assert on state rather than on shape, since a 200 with data_mode: "empty" is a passing request and an empty result:
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.