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

Neon Commerce Subscriptions API

The Subscriptions API from Neon Commerce — 4 operation(s) for subscriptions.

Neon Commerce Subscriptions API is one of 13 APIs that Neon Commerce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.neonpay.com.

4 operations 4 paths 3 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.neonpay.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Neon Commerce Subscriptions API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (EnvironmentApiKey). By default, every request must be authenticated.

  • EnvironmentApiKey — Your Environment API key, scoped to a particular environment. Sandbox keys are prefixed with pksandbox; production keys are prefixed with pk. Find your keys in…

Paths & Operations 4

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

Subscriptions 4
POST
/subscriptions/{subscriptionId}/cancel
Cancel a subscription
cancelSubscription 1 param → 200400
POST
/subscriptions/{subscriptionId}/update-payment-method
Generate a payment method update link
generateUpdatePaymentMethodUrl 1 param body → 200400
GET
/subscriptions/{subscriptionId}
Returns a subscription's details.
getSubscription 1 param → 200400404
POST
/subscriptions
Create a subscription
postSubscription body → 201400

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are SubscriptionResponse (14 properties), APIError (4 properties), ErrorDetail (2 properties). Each schema is shown below with its type and property counts.

APIError
object
4 properties 2 required
ErrorDetail
object
2 properties 2 required
SubscriptionResponse
object
14 properties 10 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neon-commerce-subscriptions-api-openapi.yml Raw ↑

Other APIs Neon Commerce publishes across the network.

Neon Commerce Account API
Neon Commerce Assets API
Neon Commerce Auth API
Neon Commerce Checkout API
Neon Commerce Client API
Neon Commerce Payouts API
Neon Commerce Prices API
Neon Commerce Pricing Sheet API
Neon Commerce Purchases API
Neon Commerce Reports API
Neon Commerce Status API
Neon Commerce Storefront API
Where this information came from

This is an independent, third-party profile of Neon Commerce Subscriptions 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.