Flywire

Flywire is a global payments enablement and software company that operates a proprietary cross-border payment network spanning more than 140 currencies and 240 countries and territories, serving the education, healthcare, travel, and business-to-business verticals. The Flywire Payments API is an HTTP-based REST API (JSON request/response bodies, API-Key authorization) that lets platforms integrate Flywire's payment network directly — creating and capturing one-off, recurring, pre-authorization, refund, and 529 payments, managing payors, recipients, checkout sessions and documents, and receiving real-time payment status callbacks (webhooks) signed with an HMAC-SHA256 shared secret. Flywire also ships client-side JavaScript and React libraries (Flywire Elements, Checkout, Pay-By-Link) for embedding hosted payment experiences.

Flywire is listed with 3 APIs on the APIs.io network. Tagged areas include Company, Payments, Cross-Border Payments, Fintech, and Education Payments.

The Flywire catalog on APIs.io includes 2 event-driven AsyncAPI specifications.

Flywire’s developer surface includes engineering blog, documentation, API reference, getting-started guide, sandbox, authentication, changelog, and 30 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

58.4/100 strong ▬ flat Agent 25/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

AccessApproval

3 APIs

Company Payments Cross-Border Payments FintechEducation PaymentsHealthcare PaymentsTravel PaymentsB2B Payments Checkout Webhook

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 58.4/100 · strong

Contract Quality 8.3 / 21

Developer Ergonomics 12.1 / 17

Access Clarity 8.5 / 17

Operational Transparency 8.4 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 8.0 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/flywire/"><img src="https://apis.io/badge/flywire/card.svg" alt="Flywire on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/flywire/apis.yml: open an issue on github.com/api-evangelist/flywire to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Gulf and Southeast Asia Open Finance	regulated	56.8	-	1
Payer Interoperability (CAQH CORE, X12, Da Vinci, WEDI)	regulated	56.8	-	1
EU/EEA Payment and E-Money Institutions (PSD2 passports)	regulated	56.8	-	1
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	56.8	-	1
TX-RAMP Certified Cloud Products (Texas DIR)	regulated	56.8	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 3

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

Flywire Payments API

REST API for integrating Flywire's global payment network — one-off, recurring, pre-authorization, refund and 529 payments, checkout sessions, payors, recipients, and documents,...

Flywire Invoicing API

REST API for the Flywire Invoicing Platform — contacts, invoices, credit notes and invoice payments for a company, with search, count and export on each resource. Authorized wit...

Flywire Payment Request API

REST API for creating, retrieving, updating and removing payer-facing payment requests for a company, including instalment schedules. Requests are authenticated with an HMAC-SHA...

Pricing Plans 1

Published pricing tiers and plan structures.

Flywire Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Flywire Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Flywire Finops

FINOPS

Event Specifications 2

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

Flywire Non Payment Webhooks

ASYNCAPI

Flywire Payments Webhooks

ASYNCAPI

Security Posture 4

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

Flywire Authentication

apiKey/oauth2/http-signature · 3 schemes

SECURITY

Flywire Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Flywire Vulnerability Disclosure

Intigriti · security.txt · contact published

SECURITY

Flywire Trust Center

SOC 2, PCI DSS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Flywire Scopes

16 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Components

Conventions

ErrorCatalog

Lifecycle

Webhooks

Conformance

DataModel

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 8

Authentication, authorization, and security posture

TrustCenter

Compliance

Security

Authentication

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

OAuthScopes

OAuthScopes

Scroll for all 8

Operate 5

Status, limits, changes, and where to get help

StatusPage

ChangeLog

RateLimits

Support

HelpCenter

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Blog

Blog

Website

Website

Source (apis.yml)

aid: flywire
name: Flywire
description: Flywire is a global payments enablement and software company that operates a proprietary cross-border payment
  network spanning more than 140 currencies and 240 countries and territories, serving the education, healthcare, travel,
  and business-to-business verticals. The Flywire Payments API is an HTTP-based REST API (JSON request/response bodies, API-Key
  authorization) that lets platforms integrate Flywire's payment network directly — creating and capturing one-off, recurring,
  pre-authorization, refund, and 529 payments, managing payors, recipients, checkout sessions and documents, and receiving
  real-time payment status callbacks (webhooks) signed with an HMAC-SHA256 shared secret. Flywire also ships client-side JavaScript
  and React libraries (Flywire Elements, Checkout, Pay-By-Link) for embedding hosted payment experiences.
url: https://raw.githubusercontent.com/api-evangelist/flywire/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- accel
- bain-capital-ventures
- balderton-capital
- qed-investors
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: medium
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-02'
tags:
- Company
- Payments
- Cross-Border Payments
- Fintech
- Education Payments
- Healthcare Payments
- Travel Payments
- B2B Payments
- Checkout
- Webhook
tags_raw:
- Company
- Payments
- Cross-Border Payments
- FinTech
- Education Payments
- Healthcare Payments
- Travel Payments
- B2B Payments
- Checkout
- Webhooks
image: https://www.flywire.com/favicon.ico
apis:
- name: Flywire Payments API
  description: REST API for integrating Flywire's global payment network — one-off, recurring, pre-authorization, refund and
    529 payments, checkout sessions, payors, recipients, and documents, with real-time payment-status callbacks.
  humanURL: https://developers.flywire.com/education/Content/api-landing-page.htm
  baseURL: https://api-platform.flywire.com/payments/v1/
  tags:
  - Payments
  - Cross-Border Payments
  - Refunds
  properties:
  - type: Documentation
    url: https://developers.flywire.com/education/Content/api-basics.htm
  - type: APIReference
    url: https://developers.flywire.com/education/Content/api-reference.htm
  - type: Sandbox
    url: sandbox/flywire-sandbox.yml
  - type: Authentication
    url: authentication/flywire-authentication.yml
  - type: ErrorCatalog
    url: errors/flywire-problem-types.yml
  - type: Webhooks
    url: asyncapi/flywire-payments-webhooks.yml
  - type: Conventions
    url: conventions/flywire-conventions.yml
  - type: DataModel
    url: data-model/flywire-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/flywire-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: RateLimits
    url: rate-limits/flywire-rate-limits.yml
- name: Flywire Invoicing API
  description: 'REST API for the Flywire Invoicing Platform — contacts, invoices, credit notes and invoice payments for a
    company, with search, count and export on each resource. Authorized with OAuth 2.0 client credentials and enforced on
    two axes: the token must carry the scope for the resource and operation, and it must be scoped to the company named in
    the URL. Documented on Flywire''s Solutions documentation estate, separately from the Payments API.'
  humanURL: https://solutions.flywire.com/en/invoicing/invoicing-api
  baseURL: https://invoicing.flywire.com
  tags:
  - Invoicing
  - Accounts Receivable
  - B2B Payments
  - Credit Notes
  properties:
  - type: Documentation
    url: https://solutions.flywire.com/en/invoicing/invoicing-api
  - type: APIReference
    url: https://solutions.flywire.com/en/invoicing/invoicing-api
  - type: Authentication
    url: authentication/flywire-authentication.yml
  - type: OAuthScopes
    url: scopes/flywire-scopes.yml
  - type: ErrorCatalog
    url: errors/flywire-problem-types.yml
  - type: Webhooks
    url: asyncapi/flywire-non-payment-webhooks.yml
  - type: ChangeLog
    url: changelog/flywire-changelog.yml
  - type: Conventions
    url: conventions/flywire-conventions.yml
  - type: DataModel
    url: data-model/flywire-data-model.yml
- name: Flywire Payment Request API
  description: REST API for creating, retrieving, updating and removing payer-facing payment requests for a company, including
    instalment schedules. Requests are authenticated with an HMAC-SHA256 digest of the request body sent in the X-Flywire-Digest
    header rather than a bearer token, and the surface has its own invoice/payment-request webhook lifecycle.
  humanURL: https://solutions.flywire.com/en/payment-requests/payment-request-api
  baseURL: https://app.flywire.com/rest/payment-request/public/company/
  tags:
  - Payment Requests
  - Instalments
  - Payments
  properties:
  - type: Documentation
    url: https://solutions.flywire.com/en/payment-requests/payment-request-api
  - type: APIReference
    url: https://solutions.flywire.com/en/payment-requests/payment-request-api
  - type: Authentication
    url: authentication/flywire-authentication.yml
  - type: Webhooks
    url: asyncapi/flywire-non-payment-webhooks.yml
  - type: ChangeLog
    url: changelog/flywire-changelog.yml
  - type: Sandbox
    url: sandbox/flywire-sandbox.yml
  - type: Conventions
    url: conventions/flywire-conventions.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Blog
  url: https://www.flywire.com/company/news
- type: TrustCenter
  url: security/flywire-trust-center.yml
- type: Website
  url: https://www.flywire.com
- type: DeveloperPortal
  url: https://developers.flywire.com/
- type: Documentation
  url: https://developers.flywire.com/education/Content/home.htm
- type: APIReference
  url: https://developers.flywire.com/education/Content/api-reference.htm
- type: GettingStarted
  url: https://developers.flywire.com/education/Content/api-basics.htm
- type: StatusPage
  url: https://status.flywire.com/
- type: TermsOfService
  url: https://www.flywire.com/legal/terms-of-use
- type: PrivacyPolicy
  url: https://www.flywire.com/legal/privacy-policy
- type: GitHubOrganization
  url: https://github.com/flywirecorp
- type: Compliance
  url: https://www.flywire.com/company/security
- type: Security
  url: https://app.intigriti.com/programs/flywire/flywirevulnerabilitydiscloseprogram/
- type: Packages
  url: packages/flywire-packages.yml
- type: SDKs
  url: packages/flywire-packages.yml
- type: Components
  url: components/flywire-components.yml
- type: Sandbox
  url: sandbox/flywire-sandbox.yml
- type: Authentication
  url: authentication/flywire-authentication.yml
- type: Conventions
  url: conventions/flywire-conventions.yml
- type: ErrorCatalog
  url: errors/flywire-problem-types.yml
- type: Lifecycle
  url: lifecycle/flywire-lifecycle.yml
- type: Webhooks
  url: asyncapi/flywire-payments-webhooks.yml
- type: Conformance
  url: conformance/flywire-conformance.yml
- type: DataModel
  url: data-model/flywire-data-model.yml
- type: WellKnown
  url: well-known/flywire-well-known.yml
- type: SecurityTxt
  url: well-known/flywire-security.txt
- type: VulnerabilityDisclosure
  url: security/flywire-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/flywire-domain-security.yml
- type: X-MCPServerCandidate
  url: mcp/flywire-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/flywire-llms.txt
- type: ChangeLog
  url: changelog/flywire-changelog.yml
- type: RateLimits
  url: rate-limits/flywire-rate-limits.yml
- type: Plans
  url: plans/flywire-plans-pricing.yml
- type: OAuthScopes
  url: scopes/flywire-scopes.yml
- type: Support
  url: https://www.flywire.com/support
- type: HelpCenter
  url: https://help.flywire.com/
- type: Login
  url: https://app.flywire.com/
x-enrichment:
  date: '2026-09-02'
  status: enriched
  artifacts_added: 5
  pass: local-v1

Flywire API — frequently asked questions

Does Flywire have an API?

Yes. APIs.io lists 3 APIs from Flywire, including Flywire Payments API, Flywire Invoicing API and Flywire Payment Request API.

How do I authenticate with the Flywire API?

Flywire uses bearer-token authentication (apiKey/oauth2/http-signature · 3 schemes). The details are profiled on APIs.io as Flywire Authentication.

Is the Flywire API ready for AI agents?

Flywire has a Kin Score of 58.4 out of 100 (strong) and an Agent Readiness score of 25.2 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/flywire"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/flywire/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/flywire/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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