Stellar Registration API
The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once per receiver to link their wallet. Only SDP-compatible wallet providers can facilitate the registration process. These endpoints must be supported and hit by the wallet providers after the receiver gets the initial invite. After the wallet address is successfully linked, the payment automatically begins.There are two parts to the registration flow. First, the wallet must authenticate and initiate a registration flow using the Anchor Platform Endpoints defined below. Note that these endpoints are hosted on a different host than the Stellar Disursement Platform.The second part of the registration flow is handled by the webview that is opened within the wallet application. This webview uses the endpoints defined in the Stellar Disbursement Platfrom Endpoints section to complete the registration process. The wallet application can chose not to use the webview and intstead integrate directly with the API.
Stellar Registration API is one of 33 APIs that Stellar publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Registration. 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 9 operations across 8 paths, and defines 2 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 Registration 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 9
Across 8 paths, the API surfaces 9 operations — 5 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.
The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once pe…
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is ReceiverRegistrationRequest (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 Registration 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.