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 Client API

The Client API from Neon Commerce — 4 operation(s) for client.

Neon Commerce Client 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 Clients. 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 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

4 operations 4 paths 12 schemas 1 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 3

Neon Commerce Client API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-Client-Key (ClientKey). An API key is passed in the header as X-Api-Key (EnvironmentApiKey). An API key is passed in the header as X-Client-Token (ClientToken).

  • ClientKey — Your Client key, used for client-side requests. Sandbox keys are prefixed with cksandbox; production keys are prefixed with ck. Find your keys in the Neon dash…
  • 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…
  • ClientToken — A short-lived client token obtained from the /client/token endpoint, used for client-side requests to the Neon APIs.

Paths & Operations 4

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

Client 4
POST
/client/token
Retrieve a client token
createClientToken body → 201400401500
POST
/client/checkout
Create a checkout using a client token
createCheckoutClient body → 201400
PATCH
/client/purchase/{purchaseId}/claim
Mark an unclaimed purchase as claimed
clientClaimPurchase 1 param → 200400404
GET
/client/purchases/unclaimed
Get all unclaimed purchases for a particular user
clientGetPurchasesUnclaimed → 200400404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are BasePurchase (29 properties), PurchaseItem (9 properties), BaseClientCreateCheckoutRequest (9 properties), PurchaseEvent (5 properties). Each schema is shown below with its type and property counts.

BaseClientCreateCheckoutRequest
object
9 properties 4 required
ClientCreateCheckoutRequest
APIError
object
4 properties 2 required
ErrorDetail
object
3 properties 2 required
PurchaseBundleItem
object
3 properties 3 required
PurchaseItem
object
9 properties 9 required
PurchaseNotFoundError
object
1 property
Purchase
APIError_2
object
4 properties 2 required
ErrorDetail_2
object
2 properties 2 required
PurchaseEvent
object
5 properties 4 required
BasePurchase
object
29 properties 19 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neon-commerce-client-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 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
Neon Commerce Subscriptions API
Where this information came from

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