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

TIGRS Registry Client API

The Tradable Instrument for Global Renewables (TIGR) registry client API for retrieving and retiring TIGR certificates — corporate entity, ledger, subaccount and system operations behind an OAuth2 password-grant JWT.

This API exposes 5 operations across 5 paths, organized into 4 resource areas, and defines 15 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against a single base URL, //tigrsregistry.apx.com:443/clientapi.

5 operations 5 paths 15 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://tigrsregistry.apx.com/clientapi
Authentication
API Key
Resource Areas
4

Authentication & Security 1

TIGRS Registry Client API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (JWT).

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. They span 4 resource areas: corporateEntity, ledger, subaccount, system. Each is listed below with its method, path, parameters, and response codes.

corporateEntity 1

Corporate Entities Operations

GET
/api/corporateEntity
Corporate Entities
getCorporateEntities 6 params → 200400401403429500
ledger 2

Ledger Operations

GET
/api/ledger/holding
Holdings
getHoldings 8 params → 200400401403429500
POST
/api/ledger/retire
Retirements
retireUsingPOST 1 param body → 200400401403413429500
subaccount 1

SubAccount Operations

POST
/api/subaccount/{subaccountType}
Subaccounts
createSubaccountsUsingPOST 2 params body → 200400401403413429500
system 1

System Information

GET
/api/system/ping
Ping System
pingUsingGET → 200401403429500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Holding (21 properties), RetireResponse (12 properties), RetireRequest (11 properties), ErrorItem (6 properties). Each schema is shown below with its type and property counts.

CorporateEntities
object
Corporate entities information
5 properties 5 required
ErrorContainer
object
Container for errors
2 properties
ErrorItem
object
Describes a specific error
6 properties 2 required
Holding
object
Holding information
21 properties 16 required
ODataEnvelopeOfCorporateEntities
object
Container for OData-like rows of information
2 properties
ODataEnvelopeWithTotalCountOfHolding
object
4 properties 2 required
Pong
object
Response indicating server health
1 property 1 required
RequestContainerOfRetireRequest
object
Container for requests
1 property
RequestContainerOfSubaccountCreateRequest
object
Container for requests
1 property
ResponseContainerOfRetireResponse
object
Container for responses
2 properties 1 required
ResponseContainerOfSubaccountCreateResponse
object
Container for responses
2 properties 1 required
RetireRequest
object
Request to retire credits
11 properties 6 required
RetireResponse
object
Response to an retire request
12 properties 7 required
SubaccountCreateRequest
object
Request to create a subaccount
4 properties 1 required
SubaccountCreateResponse
object
Response to a subaccount creation request
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xpansiv-tigr-registry-client-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of TIGRS Registry Client 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.