Coinflow events API
The events API from Coinflow — 1 operation(s) for events.
Coinflow events API is one of 14 APIs that Coinflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 1 operation across 1 path, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api-sandbox.coinflow.cash/api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 8
Coinflow events API declares
8 security schemes
for authenticating requests.
An API key is passed in the header as x-coinflow-auth-wallet (wallet).
An API key is passed in the header as x-coinflow-auth-blockchain (blockchain).
An API key is passed in the header as x-coinflow-auth-user-id (userId).
An API key is passed in the header as Authorization (merchant).
An API key is passed in the header as x-coinflow-auth-signed-message (signedMessage).
An API key is passed in the header as x-coinflow-auth-merchant-id (merchantId).
An API key is passed in the header as x-coinflow-auth-session-key (sessionKey).
An API key is passed in the header as Authorization (admin).
wallet— The web3 wallet of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-keyblockchain— The blockchain associated with the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-keyuserId— The external identifier of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-keymerchant— The API key of the merchant - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-keysignedMessage— The message signed by the users walletmerchantId— The merchant ID the session should be generated forsessionKey— The session key generated for the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 34
The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are SignUpEvent (7 properties), PhoneChallenge (5 properties), ThirdPartyKycChallenge (5 properties), SignInFailureEvent (5 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 Coinflow 12
Other APIs Coinflow publishes across the network.
This is an independent, third-party profile of Coinflow events 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.