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

Xpansiv Ledger API

Ledger Operations

Xpansiv Ledger API is one of 43 APIs that Xpansiv publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ledger. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, authentication docs, a quickstart, and an API reference.

This API exposes 6 operations across 6 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://narenewables2.apx.com/ClientAPI, //tigrsregistry.apx.com:443/clientapi.

6 operations 6 paths 30 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://connect.xpansiv.com/app/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Xpansiv Ledger API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (JWT).

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Ledger 6

Ledger Operations

POST
/api/ledger/transfer
Inter-Account Transfers
interaccountTransfer 1 param body → 200400401403413429500
POST
/api/ledger/transfer/pending/action
Pending Transfer Actions
actionPendingTransfers 1 param body → 200400401403413429500
POST
/api/ledger/subaccountTransfer
SubAccount Transfers
subaccountTransfer 1 param body → 200400401403413429500
POST
/api/ledger/retire
Retirements
retire 1 param body → 200400401403413429500
GET
/api/ledger/holding
Certificate Holdings
getHoldings 9 params → 200400401403429500
GET
/api/ledger/transfer/pending
Pending Transfers
getPendingTransfers 7 params → 200400401403429500

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are Holding (24 properties), Holding_2 (21 properties), PendingTransfer (15 properties), RetireResponse (15 properties). Each schema is shown below with its type and property counts.

SubaccountTransferRequest
object
Request to transfer credits between active subaccounts
4 properties 2 required
InteraccountTransferResponse
object
Response to a transfer request to another account
6 properties 4 required
SubaccountTransferResponse
object
Response to a transfer request between active subaccounts
6 properties 3 required
PendingTransferActionRequest
object
Request to take action on a pending transfer
4 properties 2 required
InteraccountTransferRequest
object
Request to transfer credits to another account
4 properties 3 required
ErrorItem
object
Describes a specific error
6 properties 1 required
PendingTransfer
object
Pending transfer information
15 properties 12 required
PendingTransferActionRequestDto
object
Transfer action requests
1 property
ResponseContainerPendingTransferActionResponse
object
Container for responses
2 properties 1 required
RetireResponse
object
Response to an retire request
15 properties 5 required
ResponseContainerSubaccountTransferResponse
object
Container for responses
2 properties 1 required
ErrorContainer
object
Container for errors
2 properties
ResponseContainerRetireResponse
object
Container for responses
2 properties 1 required
SubaccountTransferRequestDTO
object
Subaccount transfer requests
1 property
InteraccountTransferRequestDto
object
Transfer requests
1 property
PendingTransferActionResponse
object
Response to a pending transfer action request
4 properties 2 required
RetireRequestDto
object
Retire requests
1 property
ODataEnvelopeWithTotalCountOfHolding
object
Container for OData-like rows of information with count
4 properties 2 required
ResponseContainerInteraccountTransferResponse
object
Container for responses
2 properties 1 required
RetireRequest
object
Request to retire credits
13 properties 4 required
Holding
object
Holding information
24 properties 11 required
ODataEnvelopeWithTotalCountOfPendingTransfer
object
Container for OData-like rows of information with count
4 properties 2 required
ResponseContainerOfRetireResponse
object
Container for responses
2 properties 1 required
ODataEnvelopeWithTotalCountOfHolding_2
object
4 properties 2 required
RetireResponse_2
object
Response to an retire request
12 properties 7 required
RetireRequest_2
object
Request to retire credits
11 properties 6 required
ErrorItem_2
object
Describes a specific error
6 properties 2 required
Holding_2
object
Holding information
21 properties 16 required
RequestContainerOfRetireRequest
object
Container for requests
1 property
ErrorContainer_2
object
Container for errors
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xpansiv-ledger-api-openapi.yml Raw ↑

Other APIs Xpansiv publishes across the network.

Xpansiv Data API
Xpansiv Marketplace FIX API
Xpansiv Account API
Xpansiv Building types API
Xpansiv Clean Transportation API
Xpansiv Corporate Entity API
Xpansiv Exchange API
Xpansiv Facilities API
Xpansiv Facility import error handling API
Xpansiv File Type V1 API
Xpansiv /file Registry API
Xpansiv Forward Deals API
Where this information came from

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