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

Coinflow merchantSubscription API

The merchantSubscription API from Coinflow — 4 operation(s) for merchantsubscription.

Coinflow merchantSubscription API is one of 14 APIs that Coinflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 4 paths, and defines 20 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.

7 operations 4 paths 20 schemas 1 DELETE3 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.coinflow.cash/api
Authentication
API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 8

Coinflow merchantSubscription 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-key
  • blockchain — The blockchain associated with the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
  • userId — The external identifier of the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
  • merchant — The API key of the merchant - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
  • signedMessage — The message signed by the users wallet
  • merchantId — The merchant ID the session should be generated for
  • sessionKey — The session key generated for the end user - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

merchantSubscription 7
PATCH
/merchant/subscription/subscribers/{subscriptionId}
Cancel Subscription (by merchant)
cancel-subscription 2 params → 200
GET
/merchant/subscription/subscribers/{subscriptionId}
Get Subscription Payments
get-subscription-payments 2 params → 200
POST
/merchant/subscription/plans
Create Plans
create-plan 1 param body → 200
GET
/merchant/subscription/plans
Get Plans
get-plans 1 param → 200
DELETE
/merchant/subscription/plans/{planId}
Deactivate Plan
deactivate-plan 2 params → 200
PUT
/merchant/subscription/plans/{planId}
Update Plan
update-plan 2 params body → 200
GET
/merchant/subscription/plans/{planId}/subscribers
Get Subscribers
get-subscriptions 2 params → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are TotalsResponse (19 properties), SubscriptionPlan (11 properties), Partial_SubscriptionPlanRequest_ (10 properties), SubscriptionPlanRequest (10 properties). Each schema is shown below with its type and property counts.

Blockchain.SOLANA
string
SubscriptionDisplay
object
9 properties 7 required
Blockchain.TEMPO
string
Blockchain.STELLAR
string
SubscriptionInterval
string
Partial_SubscriptionPlanRequest_
object
Make all properties in T optional
10 properties
Blockchain.ETH
string
Blockchain
string
Blockchain.POLYGON
string
SubscriptionPlanRequest
object
10 properties 4 required
Blockchain.ARBITRUM
string
SubscriptionStatus
string
Blockchain.MONAD
string
Currency
string
Blockchain.BASE
string
TotalsResponse
object
19 properties 6 required
SubscriptionPlan
object
11 properties 6 required
OperationalBlockchain
SubscriptionPayment
object
4 properties 4 required
CurrencyCents
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coinflow-merchantsubscription-api-openapi.yml Raw ↑

Other APIs Coinflow publishes across the network.

Coinflow authentication API
Coinflow cardTokenization API
Coinflow checkout API
Coinflow customers API
Coinflow events API
Coinflow marketplace API
Coinflow merchant API
Coinflow redeem API
Coinflow refund API
Coinflow subMerchant API
Coinflow subscription API
Coinflow utilities API
Where this information came from

This is an independent, third-party profile of Coinflow merchantSubscription 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.