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

Carry1st Payments API

Create payment requests and query their status.

Carry1st Payments API is one of 4 APIs that Carry1st publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 4.0.

Requests are made against 2 base URLs: https://api-gateway.carry1st.com, https://api-gateway.platform.stage.carry1st.com.

2 operations 2 paths 7 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0
Base URL
https://api-gateway.carry1st.com
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Carry1st Payments API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as AccessToken (accessToken).

  • basicAuth — Base64(APIKEY:APISECRET) used only on the auth/token and auth/refresh endpoints.
  • accessToken — Bearer issued by generateAccessToken; required on all Gateway API requests.

Paths & Operations 2

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

Payments 2

Create payment requests and query their status.

POST
/api/pay1st/payments/create
Create Payment Request
createPaymentRequest 2 params body → 201400401
GET
/api/pay1st/payments
Query Payment Status
queryPaymentStatus 1 param → 200400401403429

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CreatePaymentRequest (11 properties), PaymentResponse (6 properties), Product (5 properties), Error (3 properties). Each schema is shown below with its type and property counts.

PaymentStatus
string
Payment lifecycle status.
CreatePaymentRequest
object
11 properties 6 required
Product
object
5 properties
PaymentResponse
object
6 properties
Metadata
object
2 properties
PaymentDetail
Error
object
Standard Pay1st error envelope.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

carry1st-payments-api-openapi.yml Raw ↑

Other APIs Carry1st publishes across the network.

Carry1st Authentication API
Carry1st Payment Methods API
Carry1st Refunds API
Where this information came from

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