How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ZenLedger Compliance Suite API

Digital-asset trade-monitoring and crypto tax-compliance REST API (v3) for financial institutions and enterprise compliance teams. Registers companies and their users, imports exchange accounts and wallets over a signed and AES-256 encrypted request, returns normalized transactions and per-source holdings, screens blockchain addresses against sanctions lists, exposes Polymarket positions, and serves supported currency, source and chain reference data. Authenticated with an OAuth 2.0 client_credentials JWT that expires in 30 minutes. Import completion, import-limit and wallet-screening events are delivered as webhooks.

ZenLedger Compliance Suite API is one of 2 APIs that ZenLedger publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tax Compliance, Sanctions Screening, Digital Assets, RegTech, and Blockchain Analytics. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 27 operations across 20 paths, organized into 11 resource areas. It is described by OpenAPI 3.1.0, at version v3.

Requests are made against a single base URL, https://api.zenledger.io.

27 operations 20 paths 0 schemas 3 DELETE17 GET5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v3
Base URL
https://api.zenledger.io
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
11

Authentication & Security 1

ZenLedger Compliance Suite API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — JWT bearer token obtained from POST /oauth/token using the OAuth 2.0 clientcredentials grant with the clientid and clientsecret ZenLedger issues. The token exp…

Paths & Operations 27

Across 20 paths, the API surfaces 27 operations — 3 DELETE, 17 GET, 5 POST, 2 PUT. They span 11 resource areas, including Authentication, Companies, Users, Transactions, Holdings, Polymarkets, Imports, Wallet Screening, and 3 more. Each is listed below with its method, path, parameters, and response codes.

Authentication 1

OAuth 2.0 clientcredentials token issuance.

POST
/oauth/token
JWT request
jwtRequest body → 200401400
Companies 5

Enterprise tenants registered under the Compliance Suite account.

GET
/compliance/api/v3/companies
GET companies
getCompanies → 200401
POST
/compliance/api/v3/companies
CREATE company
createCompany body → 200422
GET
/compliance/api/v3/companies/{company_reference}
GET company
getCompany 1 param → 200404
DELETE
/compliance/api/v3/companies/{company_reference}
DELETE company
deleteCompany 1 param → 200404
PUT
/compliance/api/v3/companies/{company_reference}
UPDATE company details
updateCompanyDetails 1 param body → 200404
Users 5

End users tracked under a company.

GET
/compliance/api/v3/companies/{company_reference}/users
GET company users
getCompanyUsers 1 param → 200404
POST
/compliance/api/v3/companies/{company_reference}/users
CREATE company user
createCompanyUser 1 param body → 200
GET
/compliance/api/v3/companies/{company_reference}/users/{user_id}
GET company user
getCompanyUser 2 params → 200404
PUT
/compliance/api/v3/companies/{company_reference}/users/{user_id}
UPDATE user details
updateUserDetails 2 params body → 200404
DELETE
/compliance/api/v3/companies/{company_reference}/users/{user_id}
DELETE company user
deleteCompanyUser 2 params → 200404
Transactions 2

Normalized crypto transactions for a user or across a company.

GET
/compliance/api/v3/companies/{company_reference}/users/{user_id}/transactions
GET transactions for user
getTransactionsForUser 10 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/transactions
GET transactions for all user of a company
getTransactionsForAllUserOfACompany 9 params → 200404
Holdings 6

Per-source balances and import state for a user or company.

GET
/compliance/api/v3/companies/{company_reference}/users/{user_id}/holdings
GET holdings for user
getHoldingsForUser 6 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/users/{user_id}/holdings/{source_id}
GET holdings for user by source
getHoldingsForUserBySource 3 params → 200404
DELETE
/compliance/api/v3/companies/{company_reference}/users/{user_id}/holdings/{source_id}
DELETE user source
deleteUserSource 3 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/holdings
GET holdings for all users of a company
getHoldingsForAllUsersOfACompany 2 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/holdings/{source_id}/resync
GET resync source
getResyncSource 2 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/holdings/{source_id}/resume
GET resume source
getResumeSource 2 params → 200404
Polymarkets 2

Polymarket prediction-market positions.

GET
/compliance/api/v3/companies/{company_reference}/users/{user_id}/polymarkets
GET polymarkets for user
getPolymarketsForUser 3 params → 200404
GET
/compliance/api/v3/companies/{company_reference}/polymarkets
GET polymarkets for all users of a company
getPolymarketsForAllUsersOfACompany 2 params → 200404
Imports 2

Wallet and exchange-account import (signed and encrypted).

POST
/compliance/api/v3/companies/{company_reference}/users/{user_id}/imports
POST wallet
postWallet 3 params body → 200401
POST
/compliance/api/v1/companies/{company_reference}/users/{user_id}/imports
POST exchange
postExchange 3 params body → 200401
Wallet Screening 1

Sanctions and risk screening for a blockchain address.

GET
/compliance/api/v3/screening
GET Wallet Screening Report
getWalletScreeningReport 2 params → 200404
Supported Currencies 1

Currency reference data.

GET
/compliance/api/v3/currencies
GET currencies
getCurrencies 1 param → 200401
Supported Exchanges and Wallets 1

Supported exchange/wallet source reference data.

GET
/compliance/api/v3/sources
GET sources
getSources 1 param → 200401
Supported Chains 1

Supported blockchain reference data.

GET
/compliance/api/v3/chains
GET chains
getChains 1 param → 200401

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zenledger-compliance-api-openapi.yml Raw ↑

Other APIs ZenLedger publishes across the network.

ZenLedger Aggregator Suite API
Where this information came from

This is an independent, third-party profile of ZenLedger Compliance Suite API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.