ZenLedger · Postman Collection

V3::Compliance Suite: REST API Reference

This document describes the REST API and resources provided by the **Compliance Suite**. The REST APIs are for developers who want to integrate the **Compliance Suite** into other applications. **Compliance Suite’s** REST API provide access to all suite resources via URI paths. To use a REST API, your application will make an HTTP request and parse the response. The response format is JSON. Your methods will be the standard HTTP methods like GET, PUT, POST and DELETE. Because the REST API is bas

36
Requests
15
Folders
View on GitHub Raw JSON Crypto TaxDigital AssetsTax ComplianceBlockchain AnalyticsRegTechAccountingSanctions ScreeningFinancial ServicesPortfolio AggregationCryptocurrencyPostman Collection

Overview

V3::Compliance Suite: REST API Reference is a Postman Collection published by ZenLedger on the APIs.io network.

This document describes the REST API and resources provided by the Compliance Suite. The REST APIs are for developers who want to integrate the Compliance Suite into other applications. Compliance Suite’s REST API provide access to all suite resources via URI paths. To use a REST API, your application will make an HTTP request and parse the response. The response format is JSON. Your methods will be the standard HTTP methods like GET, PUT, POST and DELETE. Because the REST API is bas

The collection contains 36 requests organised into 15 folders.

Tagged areas include Crypto Tax, Digital Assets, Tax Compliance, Blockchain Analytics, and RegTech.

Requests & Folders

Authentication
The **Compliance Suite** API uses a **Jason Web Token** to secure all data requests. Each one of the request needs to contain the **JWT** which has an expiration of 30 minutes and needs to be refreshe
Request Signature and Encryption
## Request Signing & Encryption All API requests to the endpoint where encryption is required must be **signed and encrypted** to ensure integrity and security. The signing process ensures that the re
Companies
The Companies API resource enable management of company data within the application, including the creation, retrieval, updating and deletion of company details. 1. **Create Company Endpoint**: This P
Users
This folder is dedicated to managing user-related operations within the Compliance API. It contains endpoints that enable retrieving, updating and deleting user information within specific companies.
Transactions
This folder contains endpoints related to retrieving transaction information for a user within the Compliance API. These endpoints allow you to fetch transactions for a user based on various criteria,
Transaction Types Glossary
This folder all different types of transactions that can be found in both `transactions` and `holdings` resources. The properties that contain this values is called `transaction_super_type` and `trans
Holdings
This folder contains endpoints related to retrieving holdings information for users of a company. Holdings represent the assets held by users in their uploaded accounts. The endpoints in this folder a
Polymarkets
This folder contains endpoints related to retrieving Polymarket participation data for users within a company. Polymarkets represent the prediction markets in which users have participated through the
Imports
This folder is dedicated to managing imports related operations within the Compliance API. It contains endpoints that allow processing wallet and exchange account imports via API. Please note that for
Wallet Screening
This folder contains endpoints related to the Wallet Screening Service. The endpoints in this folder allow running background checks on specific wallet addresses providing both Chain and Address.
Supported Currencies
The currencies resource in the Compliance API provides information about retrieving the list of supported currencies. By making a **GET** request to the `/compliance/api/v3/currencies` endpoint, you c
Supported Exchanges and Wallets
The sources resource in the Compliance API provides information about retrieving the list of supported exchanges and wallet providers. By making a **GET** request to the `/compliance/api/v3/sources` e
Supported Chains
The chains resource in the Compliance API provides information about retrieving the list of supported blockchains. By making a **GET** request to the `/compliance/api/v3/chains` endpoint, you can retr
Error Codes
The Compliance API includes specific error codes to indicate and describe various issues and errors that may occur during API interactions. To help you quickly identify and understand these error code
Webhooks and notifications
### Import Status Webhook After a user imports a new account, ZenLedger will process it and send a **webhook** **notification** to the defined **endpoint** once the new import is **completed**. This w

Related API Specs

ZenLedger Compliance Suite API (OpenAPI) ZenLedger Aggregator Suite API (OpenAPI)
Back to ZenLedger · All Collections · GitHub

Work with this as data

Every collection here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for collections

4 MCP tools reach this
  • find_collectionsBrowse and filter every collection in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This collection
curl "https://apis.io/api/v1/collections/postman-zenledger-compliance-v3"
All collections
curl "https://apis.io/api/v1/collections?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.