Banyan Systems

Banyan is a privacy-first, item-level receipt data infrastructure platform that acts as middleware between merchants, banks, fintechs, and merchant service providers so they can securely share and enrich transaction data without bilateral contracts. Merchants send receipt and item detail to Banyan (via REST API or batch), and financial institutions submit card transactions to be matched and enriched with SKU-level line items, powering products like card-linked offers (CLO), expense management, and receipt display inside banking apps. Banyan has processed over 21 billion receipts across a network of 40,000+ merchant stores and 5,000+ financial institutions. Founded in 2013, backed by Battery Ventures, Fin Capital, M13, TTV Capital and others, and acquired by Bilt Rewards in March 2025. The public developer platform at developers.banyan.com exposes an OAuth2 REST API (api.banyan.com/rest/v1) plus a webhook egress surface for enriched transactions and offer redemptions.

Banyan Systems publishes 11 API contracts indexed on the APIs.io network, including Authentication API, Card Linked Offer API, Consent API, and 8 more. Tagged areas include Company, Receipt Data, Transaction Enrichment, Item-Level Data, and Card-Linked Offers.

The Banyan Systems catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Banyan Systems’ developer surface includes documentation, API reference, getting-started guide, engineering blog, support, changelog, authentication, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

49.2/100 developing ▬ flat Agent 29/100 agent ready Front door AI 1/6 silent Heartbeat 0/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

3 published contracts

CompanyReceipt DataTransaction EnrichmentItem-Level DataCard-Linked Offers Fintech Payments Data Collaboration Webhook Data Enrichment

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 49.2/100 · developing

Contract Quality 13.8 / 19

Developer Ergonomics 7.1 / 15

Access Clarity 1.6 / 15

Operational Transparency 2.3 / 10

Contract Governance 3.2 / 9

Discoverability 6.0 / 8

Regulatory Posture 4.2 / 15

Create-or-Update Ergonomics 3.3 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 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 0 / 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 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/banyan-systems/"><img src="https://apis.io/badge/banyan-systems/card.svg" alt="Banyan Systems 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
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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 10.5 — up to +17.9 composite points
Developer Ergonomics scores 47.6 — up to +10.5 composite points
Operational Transparency scores 23.7 — up to +9.9 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/banyan-systems/apis.yml: open an issue on github.com/api-evangelist/banyan-systems 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 →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 11

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

Banyan API

Banyan's OAuth2 REST API for submitting receipt and transaction data, retrieving enriched (item-level) transactions, managing card-linked-offer campaigns/offers/activations, rec...

Banyan Systems Authentication API

The Authentication API from Banyan Systems — 2 operation(s) for authentication.

Banyan Systems Card Linked Offer API

The Card Linked Offer API from Banyan Systems — 9 operation(s) for card linked offer.

Banyan Systems Consent API

The Consent API from Banyan Systems — 3 operation(s) for consent.

Banyan Systems Enriched Data API

The Enriched Data API from Banyan Systems — 3 operation(s) for enriched data.

Banyan Systems Enriched Data - Merchant Service Provider API

The Enriched Data - Merchant Service Provider API from Banyan Systems — 1 operation(s) for enriched data - merchant service provider.

Banyan Systems History API

The History API from Banyan Systems — 1 operation(s) for history.

Banyan Systems Receipt API

The Receipt API from Banyan Systems — 4 operation(s) for receipt.

Banyan Systems Tag Counter API

The Tag Counter API from Banyan Systems — 1 operation(s) for tag counter.

Banyan Systems Transaction API

The Transaction API from Banyan Systems — 2 operation(s) for transaction.

Banyan Systems Webhook API

The Webhook API from Banyan Systems — 5 operation(s) for webhook.

Scroll for all 11

Event Specifications 1

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

Banyan Systems Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Banyan Systems Context

117 classes · 230 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Banyan Systems API Rules

16 rules · 12 errors 3 warnings 1 info

SPECTRAL

JSON Schema 12

Standalone JSON Schema definitions for this provider's data models.

ConsentEgressJSON

5 properties

JSON SCHEMA

ConsentIngressJSON

5 properties

JSON SCHEMA

CreateConsentRecordIDJSON

1 properties

JSON SCHEMA

Error

3 properties

JSON SCHEMA

FindConsentInputJSON

4 properties

JSON SCHEMA

FindConsentOutputJSON

1 properties

JSON SCHEMA

OfferEntityJSON

25 properties

JSON SCHEMA

OfferIngressJSON

21 properties

JSON SCHEMA

ReceiptHotelJSON

16 properties

JSON SCHEMA

ReceiptMerchantJSON

19 properties

JSON SCHEMA

ReceiptRetailJSON

16 properties

JSON SCHEMA

TransactionEgressJSON

12 properties

JSON SCHEMA

Scroll for all 12

Security Posture 2

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

Banyan Systems Authentication

oauth2 · 1 scheme

SECURITY

Banyan Systems Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Banyan Systems Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

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

Banyan Systems Agentic Access

40 operations · 17 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conventions

ErrorCatalog

Lifecycle

Conformance

Webhooks

Scroll for all 9

Access & Security 3

Authentication, authorization, and security posture

OAuthScopes

OAuthScopes

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: banyan-systems
name: Banyan Systems
description: Banyan is a privacy-first, item-level receipt data infrastructure platform that acts as middleware between merchants,
  banks, fintechs, and merchant service providers so they can securely share and enrich transaction data without bilateral
  contracts. Merchants send receipt and item detail to Banyan (via REST API or batch), and financial institutions submit card
  transactions to be matched and enriched with SKU-level line items, powering products like card-linked offers (CLO), expense
  management, and receipt display inside banking apps. Banyan has processed over 21 billion receipts across a network of 40,000+
  merchant stores and 5,000+ financial institutions. Founded in 2013, backed by Battery Ventures, Fin Capital, M13, TTV Capital
  and others, and acquired by Bilt Rewards in March 2025. The public developer platform at developers.banyan.com exposes an
  OAuth2 REST API (api.banyan.com/rest/v1) plus a webhook egress surface for enriched transactions and offer redemptions.
url: https://raw.githubusercontent.com/api-evangelist/banyan-systems/refs/heads/main/apis.yml
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/64cf554e262e35556d264e52/66423c7fdfa3c29d470e52e2_Banyan%20Logo_OGI.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: enriched
x-tier-reason: portfolio-lead-enriched
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-20
tags:
- Company
- Receipt Data
- Transaction Enrichment
- Item-Level Data
- Card-Linked Offers
- Fintech
- Payments
- Data Collaboration
- Webhook
- Data Enrichment
tags_raw:
- Company
- Receipt Data
- Transaction Enrichment
- Item-Level Data
- Card-Linked Offers
- Fintech
- Payments
- Data Collaboration
- Webhooks
- Data Enrichment
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/banyan-systems-agentic-access.yml
- type: Spectral
  url: rules/banyan-systems-rules.yml
- type: JSONLD
  url: json-ld/banyan-systems-context.jsonld
- type: Vocabulary
  url: vocabulary/banyan-systems-vocabulary.yml
- type: DataModel
  url: data-model/banyan-systems-data-model.yml
- type: Hosts
  url: hosts/banyan-systems-hosts.yml
- type: Vendors
  url: vendors/banyan-systems-vendors.yml
- type: Newsroom
  url: https://www.banyan.com/press
- type: OAuthScopes
  url: scopes/banyan-systems-scopes.yml
- type: Website
  url: https://www.banyan.com/
- type: DeveloperPortal
  url: https://developers.banyan.com/docs
- type: Documentation
  url: https://developers.banyan.com/docs
- type: APIReference
  url: https://developers.banyan.com/reference
- type: GettingStarted
  url: https://developers.banyan.com/docs/getting-started
- type: Blog
  url: https://www.banyan.com/blog-featured
- type: Support
  url: https://www.banyan.com/contact
- type: PrivacyPolicy
  url: https://www.banyan.com/privacy-policy
- type: ChangeLog
  url: https://developers.banyan.com/changelog
- type: ChangeLog
  url: changelog/banyan-systems-changelog.yml
- type: Authentication
  url: authentication/banyan-systems-authentication.yml
- type: Conventions
  url: conventions/banyan-systems-conventions.yml
- type: ErrorCatalog
  url: errors/banyan-systems-problem-types.yml
- type: Lifecycle
  url: lifecycle/banyan-systems-lifecycle.yml
- type: Conformance
  url: conformance/banyan-systems-conformance.yml
- type: Webhooks
  url: asyncapi/banyan-systems-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/banyan-systems-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/banyan-systems-llms.txt
- type: WellKnown
  url: well-known/banyan-systems-well-known.yml
- type: DomainSecurity
  url: security/banyan-systems-domain-security.yml
apis:
- name: Banyan API
  description: Banyan's OAuth2 REST API for submitting receipt and transaction data, retrieving enriched (item-level) transactions,
    managing card-linked-offer campaigns/offers/activations, receipt search, consumer consent, and webhook endpoint management.
    Base URL https://api.banyan.com with versioned paths under /rest/v1.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  properties:
  - type: Documentation
    url: https://developers.banyan.com/docs
  - type: APIReference
    url: https://developers.banyan.com/reference
  - type: GettingStarted
    url: https://developers.banyan.com/docs/getting-started
  - type: Authentication
    url: authentication/banyan-systems-authentication.yml
  aid: banyan-systems:banyan-api
- aid: banyan-systems:banyan-systems-authentication-api
  name: Banyan Systems Authentication API
  description: The Authentication API from Banyan Systems — 2 operation(s) for authentication.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-authentication-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-card-linked-offer-api
  name: Banyan Systems Card Linked Offer API
  description: The Card Linked Offer API from Banyan Systems — 9 operation(s) for card linked offer.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Card Linked Offer
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-card-linked-offer-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-consent-api
  name: Banyan Systems Consent API
  description: The Consent API from Banyan Systems — 3 operation(s) for consent.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Consent
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-consent-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-enriched-data-api
  name: Banyan Systems Enriched Data API
  description: The Enriched Data API from Banyan Systems — 3 operation(s) for enriched data.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Enriched Data
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-enriched-data-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-enriched-data-merchant-service-provider-api
  name: Banyan Systems Enriched Data - Merchant Service Provider API
  description: The Enriched Data - Merchant Service Provider API from Banyan Systems — 1 operation(s) for enriched data -
    merchant service provider.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Enriched Data - Merchant Service Provider
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-enriched-data-merchant-service-provider-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-history-api
  name: Banyan Systems History API
  description: The History API from Banyan Systems — 1 operation(s) for history.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - History
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-history-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-receipt-api
  name: Banyan Systems Receipt API
  description: The Receipt API from Banyan Systems — 4 operation(s) for receipt.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Receipt
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-receipt-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-tag-counter-api
  name: Banyan Systems Tag Counter API
  description: The Tag Counter API from Banyan Systems — 1 operation(s) for tag counter.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Tag Counter
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-tag-counter-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-transaction-api
  name: Banyan Systems Transaction API
  description: The Transaction API from Banyan Systems — 2 operation(s) for transaction.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Transaction
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-transaction-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
- aid: banyan-systems:banyan-systems-webhook-api
  name: Banyan Systems Webhook API
  description: The Webhook API from Banyan Systems — 5 operation(s) for webhook.
  humanURL: https://developers.banyan.com
  baseURL: https://api.banyan.com
  tags:
  - Webhook
  properties:
  - type: OpenAPI
    url: openapi/banyan-systems-webhook-api-openapi.yml
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-entity-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-offer-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-merchant-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-retail-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-receipt-hotel-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-transaction-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-egress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-consent-ingress-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-error-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-input-json-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-create-consent-record-idjson-schema.json
  - type: JSONSchema
    url: json-schema/banyan-systems-find-consent-output-json-schema.json
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence
x-readme-harvest:
  date: '2026-10-14'
  ops: 40
  tool: harvest-readme-openapi.py
  portal: https://developers.banyan.com

Banyan Systems API — frequently asked questions

Does Banyan Systems have an API?

Yes. APIs.io lists 11 APIs from Banyan Systems, including Banyan API, Banyan Systems Authentication API and Banyan Systems Card Linked Offer API, and 8 more.

Is there an OpenAPI specification for the Banyan Systems API?

Yes. APIs.io indexes 10 OpenAPI specifications for Banyan Systems, each linked for download from this page.

How do I authenticate with the Banyan Systems API?

Banyan Systems documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Banyan Systems Authentication.

Is the Banyan Systems API ready for AI agents?

Banyan Systems has a Kin Score of 49.2 out of 100 (developing) and an Agent Readiness score of 28.9 (agent-ready), scored by API Evangelist on 2026-11-06.

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/banyan-systems"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/banyan-systems/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.