slug; /v1/movement/{id} takes a numeric movement ID.
GET /v1/movement
Returns treasury movements for a project with classification status, category, and counterparty detail. Powers the Movements and Classifications tabs. Parameters:slug (required), limit, page
Example Response
Example Response
GET /v1/movement/export/csv
Returns all movements for a project as a CSV file download. Parameters:slug (required)
CSV exports are not available on every plan. If your plan does not include this endpoint, it returns
403.Returns a text/csv file with the same fields as /v1/movement. Use -o to save to a file.
GET /v1/movement/
Returns full detail for a single movement by its numeric ID. Parameters:id (path, required)
The
MOV- prefix shown in the 01Resolved UI is a display convention only. Pass the numeric value after the prefix (e.g. use 19958999, not MOV-19958999).Example Response
Example Response
GET /v1/movement/filters/entity
Returns the entity types present in a project’s movements. Used to populate the entity filter dropdown alongside/v1/movement/filters/token.
Parameters: slug (required)
Example Response
Example Response
Returns a flat array of entity types. Projects with a separate operating company return both DAO and OpCo; DAO-only projects return DAO alone. Pass any value back as the entityType filter on the movement endpoints.
GET /v1/movement/filters/token
Returns the list of tokens present in a project’s movements. Used to populate token filter dropdowns in the Movements and Classifications tabs. Parameters:slug (required)
Example Response
Example Response
GET /v1/category
Returns movement classification categories and subcategories. Powers the Category and Sub-category columns in the Movements and Classifications tabs. Parameters:slug (required)
Example Response
Example Response
GET /v1/dao/movements
Returns treasury transactions with labeled source and destination wallets. A simpler alternative to/v1/movement that uses slug and returns less classification detail.
Parameters: slug (required), limit, page
Example Response
Example Response