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 Aggregator Suite API

Partner/aggregator REST API (v1) that creates an aggregated portfolio from a set of exchange and wallet accounts, returns the resulting tax calculation for that portfolio by aggregation code, and serves the supported source and currency reference data. Authenticated with the same OAuth 2.0 client_credentials JWT as the Compliance Suite.

ZenLedger Aggregator 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 Portfolio Aggregation, Crypto Tax, and Digital Assets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, organized into 5 resource areas. It is described by OpenAPI 3.1.0, at version v1.

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

5 operations 5 paths 0 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

ZenLedger Aggregator 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 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. They span 5 resource areas: Authentication, Portfolios, Taxes, Supported Exchanges and Wallets, Supported Currencies. 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
Portfolios 1

Create an aggregated portfolio from a set of accounts.

POST
/aggregators/api/v1/portfolios
CREATE portfolio
createPortfolio body → 200422
Taxes 1

Retrieve the tax calculation for an aggregated portfolio.

GET
/aggregators/api/v1/taxes
Taxes
taxes 1 param → 200
Supported Exchanges and Wallets 1

Supported exchange/wallet source reference data.

GET
/aggregators/api/v1/sources
GET sources
getSources 1 param → 200401
Supported Currencies 1

Currency reference data.

GET
/aggregators/api/v1/currencies
GET currencies
getCurrencies 1 param → 200401

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zenledger-aggregator-api-openapi.yml Raw ↑

Other APIs ZenLedger publishes across the network.

ZenLedger Compliance Suite API
Where this information came from

This is an independent, third-party profile of ZenLedger Aggregator 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.