Stellar Receivers API
Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identifiable information. Each receiver must be unique within the disbursement.Each receiver will have at least one wallet associated with them. The wallet public key will remain null until the receiver registers with a wallet provider and links the wallet to the SDP through SEP-24. Receivers must verify their identity through that process, which requires the SDP to store verification information on receivers like date of birth, national ID number, or personal PIN. This information can be updated by the organization through the receiver endpoints.
Stellar Receivers API is one of 33 APIs that Stellar publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Receivers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a GitHub repository, and rate-limit docs.
This API exposes 7 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 2.1.0.
Requests are made against the base URL https://horizon.stellar.org.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Stellar Receivers API declares
4 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (BearerAuth).
An API key is passed in the header as Authorization (SEP10Auth).
An API key is passed in the header as Authorization (SEP24Auth).
An API key is passed in the query as token (SEP24QueryAuth).
BearerAuth— Authorization header containing an SDP JWT (ES256) or an SDP API key.SEP10Auth— Authorization header containing a SEP-10 JWT (Bearer {token}).SEP24Auth— Authorization header containing a SEP-24 JWT (Bearer {token}).SEP24QueryAuth— Query parameter containing a SEP-24 JWT.
Paths & Operations 7
Across 5 paths, the API surfaces 7 operations — 3 GET, 3 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identi…
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ReceiverWallet (17 properties), Receiver (12 properties), WalletLite (7 properties), PatchReceiverRequest (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Stellar 12
Other APIs Stellar publishes across the network.
This is an independent, third-party profile of Stellar Receivers 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.