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 beneficiary authorization API

The beneficiary authorization API from PolySign — 6 operation(s) for beneficiary authorization.

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

Tagged areas include beneficiary authorization. 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 4 GET1 POST1 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 beneficiary authorization 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 — 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

beneficiary authorization 6
GET
/v1/beneficiary_status_updates/{beneficiary_auth_id}
Get all status updates associated with a beneficiary authorization by its id.
1 param → 200
GET
/v1/beneficiary_authorizations/{beneficiary_auth_id}
Get the details of a beneficiary authorization on AtomicNet by its id.
1 param → 200
GET
/v1/beneficiary_authorizations/list
Get the detail of all beneficiary authorizations on AtomicNet.
1 param → 200
GET
/v1/beneficiary_authorizations/list/local
Get the detail of all beneficiary authorizations involved by this node.
1 param → 200
POST
/v1/beneficiary_authorizations/request
Request a new beneficiary authorization.
body → 200
PUT
/v1/beneficiary_authorizations/
Approve a beneficiary authorization.
body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Metadata4 (9 properties), BeneficiaryAuth (5 properties), AbcSignature4 (5 properties), BeneficiaryAuthStatusUpdate (4 properties). Each schema is shown below with its type and property counts.

BeneficiaryAuthRecord
object
Beneficiary authorization record object.
4 properties 4 required
AbcSignature4
object
5 properties 4 required
Metadata4
object
9 properties
OnetimeIdMap4
object
ID mapping.
2 properties 2 required
BeneficiaryAuth
object
Beneficiary authorization schema.
5 properties 1 required
BeneficiaryAuthStatusUpdateList
object
List of beneficiary authorization status update objects.
1 property 1 required
BeneficiaryAuthStatusUpdate
object
Beneficiary authorization status update object.
4 properties 4 required
BeneficiaryAuthList
object
1 property 1 required
OnetimeIdMapList4
object
List of ID mappings.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

polysign-beneficiary-authorization-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 book transfer API
PolySign book transfer confirmation API
PolySign escrow authorization API
PolySign Investor API
PolySign Order API
PolySign Partner API
Where this information came from

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