Chargeflow API Documentation

This is the complete API documentation for connecting to the Chargeflow API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Chargeflow: Automate chargebacks, alerts, disputes, webhooks, evidence generation, and Chargeflow Connect account operations through the Chargeflow public API. Keep reading to get started.

Quickstart

Before you run your first Chargeflow request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Chargeflow connection — create or choose one in Connections. Note its connectionId.

Every Chargeflow action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/chargeflow/latest/actions/{actionSlug}

You need a MindCloud API Key and a Chargeflow connection. Then call an action such as Get Account By ID:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/chargeflow/latest/actions/get-account-by-id" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Chargeflow account that should run the action. MindCloud stores and refreshes the Chargeflow credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Chargeflow actions

All 34 published actions for this Chargeflow version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Account
• POSTCreate Customer Communication
• POSTCreate Data Subject Removal Request
• POSTCreate Dispute
• POSTCreate Integration
• POSTCreate Order
• POSTCreate Subscription
• POSTCreate Transaction
• POSTCreate User Event Log
• POSTCreate Webhook
• DELETEDelete Webhook
• PUTEnrich Dispute
• POSTGenerate Evidence
• GETGet Account By ID
• GETGet Alert By ID
• GETGet Dispute By ID
• GETGet Evidence By ID
• GETGet Integration By ID
• GETGet Removal Request Status
• GETList Accounts
• GETList Alerts
• GETList Disputes
• GETList Evidence
• GETList Integrations
• GETList Webhooks
• DELETERevoke Integration Access
• PUTUpdate Account
• PUTUpdate Alert Outcome
• PUTUpdate Dispute Order
• PUTUpdate Integration
• POSTUpload Evidence
• GETValidate Access Key
• GETVerify Access Key
• GETVerify Service Health

Related apps

More Commerce apps on the Universal API, behind the same REST shape. Or browse all apps.

StripeShopifySquareWooCommerceXeroThinkificWhopGumroad