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

ConnexPay Checkout Sessions API

Operations for creating and managing checkout sessions.Checkout sessions are secure server-side objects that contain all payment detailsfor a transaction. They serve as a bridge between your backend and the ConnexPay SDK,ensuring that sensitive transaction data cannot be tampered with on the client side.

ConnexPay Checkout Sessions API is one of 39 APIs that ConnexPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkout Sessions. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 1 operation across 1 path, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://sandboxsalesapi.connexpay.com, https://salesapi.connexpay.com.

1 operations 1 paths 7 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://salesapi.connexpay.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

ConnexPay Checkout Sessions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — JWT token obtained from ConnexPay authentication

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.

Checkout Sessions 1

Operations for creating and managing checkout sessions. Checkout sessions are secure server-side objects that contain all payment details for a transaction. They serve as a bridge…

POST
/api/v2/Checkout/checkout-session
Create Checkout Session
createCheckoutSession body → 200400401422500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SaleData (32 properties), Customer (16 properties), CheckoutSessionResponse (9 properties), LineItem (9 properties). Each schema is shown below with its type and property counts.

EnhancedData
object
9 properties
LineItem
object
9 properties 4 required
SaleData
object
32 properties 3 required
Customer
object
16 properties
DtoCheckoutSession
object
3 properties 3 required
ErrorResponse
object
3 properties
CheckoutSessionResponse
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

connexpay-checkout-sessions-api-openapi.yml Raw ↑

Other APIs ConnexPay publishes across the network.

ConnexPay 3ds API
ConnexPay 3 D Secure API
ConnexPay Accounting API
ConnexPay Addendum API
ConnexPay Authenticate API
ConnexPay Authonlys API
ConnexPay Cancel API
ConnexPay Captures API
ConnexPay Card Booking API
ConnexPay Cards API
ConnexPay Chargeback API
ConnexPay Credit API
Where this information came from

This is an independent, third-party profile of ConnexPay Checkout Sessions 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.