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

PolySign settlement confirmation API

The settlement confirmation API from PolySign — 6 operation(s) for settlement confirmation.

PolySign settlement confirmation API is one of 17 APIs that PolySign publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include settlement confirmation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

6 operations 6 paths 9 schemas 5 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5ba508e7771507febd8e2056c369fffd575b4272
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

PolySign settlement confirmation API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • OAuth2 — OAuth 2.0 with the client credentials grant flow.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 5 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

settlement confirmation 6
GET
/v1/settlement_confirmations/{settlement_id}
Get all settlement confirmations for a settlementid in AtomicNet.
1 param → 200
GET
/v1/settlement_confirmations/{give_order_id}/{take_order_id}
Get the detail of a settlement confirmation on AtomicNet.
2 params → 200
GET
/v1/settlement_confirmations/list
Get the detail of all settlement confirmations on AtomicNet.
1 param → 200
GET
/v1/settlement_confirmations/list/local
Get the detail of all settlement confirmations involved by this node on AtomicNet.
1 param → 200
PUT
/v1/settlement_confirmations/
Release a settlement confirmation on execution after being memorialized on ABC.
body → 200
GET
/v1/settlement_confirmation_status_updates/{give_order_id}/{take_order_id}
Get all status updates associated with a settlement confirmation by its id.
2 params → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Metadata5 (9 properties), SettlementConfirmationRecord (7 properties), SettlementConfirmation (6 properties), SettlementConfirmationStatusUpdate (5 properties). Each schema is shown below with its type and property counts.

SettlementConfirmationRecord
object
7 properties 7 required
AbcSignature5
object
5 properties 4 required
SettlementConfirmation
object
6 properties 1 required
SettlementConfirmationStatusUpdateList
object
List of settlement confirmation status update objects.
1 property 1 required
Metadata5
object
9 properties
SettlementConfirmationList
object
1 property 1 required
OnetimeIdMap5
object
ID mapping.
2 properties 2 required
OnetimeIdMapList5
object
List of ID mappings.
1 property
SettlementConfirmationStatusUpdate
object
Settlement confirmation status update object.
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

polysign-settlement-confirmation-api-openapi.yml Raw ↑

Other APIs PolySign publishes across the network.

PolySign ABC Accounts API
PolySign ABC Memorials API
PolySign ABC Signing API
PolySign ABC Testnet API
PolySign Asset API
PolySign Authentication API
PolySign beneficiary authorization API
PolySign book transfer API
PolySign book transfer confirmation API
PolySign escrow authorization API
PolySign Investor API
PolySign Order API
Where this information came from

This is an independent, third-party profile of PolySign settlement confirmation 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.