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
GoCardless website screenshot

GoCardless

GoCardless is a global account-to-account payments platform specializing in pull-based bank debit (UK Bacs, SEPA Direct Debit, ACH, BECS, PAD, Autogiro) and open-banking instant bank payments, used by businesses to collect recurring subscriptions, invoices, and one-off payments directly from customer bank accounts. The GoCardless REST API exposes customers, bank accounts, mandates, payments, payouts, subscriptions, refunds, events, webhooks, and verification flows. Authentication uses Bearer access tokens issued from the dashboard, with separate sandbox and live environments; every request must include a GoCardless-Version header.

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles GoCardless the way a machine reads it — 42 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — GoCardless scores 45.4/100 (developing), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
GoCardless Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from GoCardless's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/gocardless/"
   title="GoCardless on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/gocardless.svg"
       alt="GoCardless Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile GoCardless

Each block below is one kind of artifact we hold for GoCardless. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 16

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

GoCardless billing_request_flows API

The billing_request_flows API from GoCardless — 2 operation(s) for billing_request_flows.

GoCardless billing_requests API

The billing_requests API from GoCardless — 2 operation(s) for billing_requests.

GoCardless blocks API

The blocks API from GoCardless — 2 operation(s) for blocks.

GoCardless creditor_bank_accounts API

The creditor_bank_accounts API from GoCardless — 1 operation(s) for creditor_bank_accounts.

GoCardless creditors API

The creditors API from GoCardless — 2 operation(s) for creditors.

GoCardless customer_bank_accounts API

The customer_bank_accounts API from GoCardless — 2 operation(s) for customer_bank_accounts.

GoCardless customers API

The customers API from GoCardless — 2 operation(s) for customers.

GoCardless events API

The events API from GoCardless — 2 operation(s) for events.

GoCardless instalment_schedules API

The instalment_schedules API from GoCardless — 2 operation(s) for instalment_schedules.

GoCardless institutions API

The institutions API from GoCardless — 1 operation(s) for institutions.

GoCardless mandates API

The mandates API from GoCardless — 3 operation(s) for mandates.

GoCardless payer_authorisations API

The payer_authorisations API from GoCardless — 2 operation(s) for payer_authorisations.

GoCardless payments API

The payments API from GoCardless — 3 operation(s) for payments.

GoCardless payouts API

The payouts API from GoCardless — 2 operation(s) for payouts.

GoCardless refunds API

The refunds API from GoCardless — 2 operation(s) for refunds.

GoCardless subscriptions API

The subscriptions API from GoCardless — 3 operation(s) for subscriptions.

Scroll within the panel for all 16 ·

Open Collections 18

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 18 ·

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

GoCardless Webhooks

AsyncAPI description of the GoCardless webhook surface. GoCardless POSTs a JSON envelope containing one or more events (up to 250 per request) to each subscribed `webhook_endpoi...

ASYNCAPI

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

GoCardless API Rules

6 rules · 1 errors · 5 warnings

SPECTRAL

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gocardless Authentication

http · 1 scheme

SECURITY

Gocardless Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Gocardless Vulnerability Disclosure

security.txt · contact published

SECURITY

Gocardless Trust Center

ISO/IEC 27001, FCA authorisation, PCI DSS

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Gocardless Scopes

1 scope

1 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Gocardless Agentic Access

48 operations · 21 acting

48 operations · 21 acting

AGENTIC

Resources

Every other property we hold for GoCardless — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/gocardless · machine-readable index on apis.io

Where this information came from

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