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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cacheflow

Cacheflow Payments API

The Payments API from Cacheflow — 5 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cacheflow Payments API is one of 57 APIs that Cacheflow 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, authentication docs, and rate-limit docs.

This API exposes 5 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 0.0.3.

Requests are made against 2 base URLs: https://api.getcacheflow.com, https://api.sandbox.getcacheflow.com.

5 operations 5 paths 13 schemas 4 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.3
Base URL
https://api.getcacheflow.com
Resource Areas
1

Paths & Operations 5

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

Payments 5
GET
/api/latest/data/transactions/{id}
Retrieve a payment
getTransaction 1 param → 200
GET
/api/latest/data/transactions/reference/{type}/{referenceId}
Get payment by reference
getTransactionByReference 2 params → 200
GET
/api/latest/data/transactions/{id}/transfers
List transfers for a payment
getTransactionChildren 1 param → 200
GET
/api/latest/data/transactions
List payments
listTransactions 4 params → 200
PATCH
/api/latest/data/billing-schedules/{id}
Update a billing schedule
updateBillingSchedule 1 param body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are Transfer (33 properties), BillingSchedule (33 properties), BillingItem (28 properties), Account (27 properties). Each schema is shown below with its type and property counts.

ExternalSource
object
3 properties 2 required
TransferSummaryRest
object
19 properties
BillingScheduleRequest
object
1 property 1 required
Address
object
17 properties
ObjectReference
object
5 properties
SyncEvent
object
12 properties
Transfer
object
33 properties 2 required
BillingSchedule
object
33 properties 13 required
BillingItem
object
28 properties 12 required
ProductUsage
object
10 properties 1 required
PaymentMethod
object
21 properties
Account
object
27 properties
Transaction
object
23 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cacheflow-payments-api-openapi.yml Raw ↑

Other APIs Cacheflow publishes across the network.

Cacheflow Accounts API
AE Profile APIs.io
Cacheflow Addresses API
AE Profile APIs.io
Cacheflow Approval Groups API
AE Profile APIs.io
Cacheflow Approval Requests API
AE Profile APIs.io
Cacheflow Attachments API
AE Profile APIs.io
Cacheflow Authentication API
AE Profile APIs.io
Cacheflow Branding API
AE Profile APIs.io
Cacheflow Checkout API
AE Profile APIs.io
Cacheflow Close API
AE Profile APIs.io
Cacheflow Contacts API
AE Profile APIs.io
Cacheflow Countries API
AE Profile APIs.io
Cacheflow CRM API
AE Profile APIs.io
#Payments
← Back to C APIs
API Details
ID
cacheflow:cacheflow-payments-api
Base URL
https://api.getcacheflow.com
Docs
https://developer.getcacheflow.com/reference
Provider
Cacheflow
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cacheflow-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cacheflow-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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