Q2
Q2 Holdings is a financial services software company that provides digital banking, lending, and embedded finance solutions to banks, credit unions, and fintechs. Its embedded finance platform, Helix by Q2 (formerly CorePro / Cambr), exposes a REST API that lets developers incorporate real, FDIC-insured savings and checking accounts, cards, transfers, and ACH into their own applications. The Helix API covers account, customer, card, external-account, transfer, transaction, statement, and program management, with a real-time Events Bus, SFTP batch files, and an administrative web application. Q2 serves over 1,000 financial institutions and 10M+ digital banking end users.
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.
API Evangelist profiles Q2 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 — Q2 scores 48.5/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). 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
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Q2'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/q2/"
title="Q2 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/q2.svg"
alt="Q2 Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/q2/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/q2/"
title="Q2 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/q2/card.svg"
alt="Q2 Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Q2
Each block below is one kind of artifact we hold for Q2. 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 28
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.
Q2 Account API
Endpoints for the account object
Q2 Account Beneficiary API
Endpoints for the accountBeneficiary object
Q2 Account - Entitlement API
Endpoints related to account entitlements
Q2 Account - Hold API
Endpoints related to account holds
Q2 Account - Limit API
Endpoints related to account limits
Q2 Account - Stop Pay API
Endpoints related to account stop payments
Q2 Bank Document API
Endpoints for the bankDocument object
Q2 Card API
Endpoints for the card object
Q2 Card Control API
Endpoints for the cardControl object
Q2 Card - Fraud Text Alert API
Endpoints related to fraud text alerts
Q2 Card - Limit API
Endpoints related to card limits
Q2 Card - Mock API
Endpoints related to simulating card workflows
Q2 Card - Provision API
Endpoints related to card provisioning
Q2 Card - Risk Factor API
Endpoints related to card risk factors
Q2 Customer API
Endpoints for the customer object
Q2 Customer Beneficiary API
Endpoints for the customerBeneficiary object
Q2 Customer Document API
Endpoints for the customerDocument object
Q2 Customer - Due Diligence API
Endpoints related to customer due diligence
Q2 Customer Relationship API
Endpoints for the customerRelationship object
Q2 External Account API
Endpoints for the externalAccount object
Q2 External Account Document API
Endpoints for the externalAccountDocument object
Q2 Fee API
Endpoints for the fee object
Q2 Program API
Endpoints for the program object
Q2 Statement API
Endpoints for the statement object
Q2 Transaction API
Endpoints for the transaction object
Q2 Transaction - Wire API
Endpoints related to wire transactions
Q2 Transfer API
Endpoints for the transfer object
Q2 Transfer - Wire API
Endpoints related to wire transfer objects
Scroll within the panel for all 28 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Q2 Rate Limits
RATE LIMITSEvent 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.
Q2 Events Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Q2 Context
JSON-LDSpectral 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.
Q2 API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountObject200Response
JSON SCHEMACardObject200Response
JSON SCHEMACustomerNoBusinessFieldsArray200Response
JSON SCHEMACustomerObject200Response
JSON SCHEMAProgramGet200Response
JSON SCHEMATransactionObject200Response
JSON SCHEMASecurity Posture 3
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.
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.
Resources
Every other property we hold for Q2 — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/q2 · machine-readable index on apis.io
This is an independent, third-party profile of Q2, 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.