Chrome River

Chrome River provides enterprise expense and invoice management solutions, now operating as part of Emburse. The platform offers automated expense reporting, compliance controls, analytics, and integration capabilities for large organizations, helping streamline travel and spend processes across global operations. It supports multi-currency handling, policy enforcement, receipt capture via mobile, and integrates with ERP, accounting, and travel booking systems, delivering comprehensive spend visibility and control for enterprises worldwide.

Chrome River publishes 15 API contracts indexed on the APIs.io network, including Accounts API, Allowances API, Cards API, and 12 more. Tagged areas include Finance, Expense Management, Software-as-a-Service, Enterprise, and Travel.

The Chrome River catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Chrome River’s developer surface includes support, pricing, engineering blog, documentation, authentication, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

45.3/100 developing ▼ -5.9 Agent 25/100 agent aware Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 5 Agent Skills

Finance Expense Management Software-as-a-Service Enterprise Travel

Kin Score

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

Composite quality — 45.3/100 · developing

Contract Quality 11.7 / 19

Developer Ergonomics 3.8 / 15

Access Clarity 9.7 / 15

Operational Transparency 0.8 / 10

Contract Governance 2.0 / 9

Discoverability 5.0 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 0.0 / 10

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 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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/chrome-river/"><img src="https://apis.io/badge/chrome-river/card.svg" alt="Chrome River 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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

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

Developer Ergonomics scores 25.6 — up to +14.9 composite points
Operational Transparency scores 7.9 — up to +12.0 composite points
Contract Quality scores 62.2 — up to +9.5 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/chrome-river/apis.yml: open an issue on github.com/api-evangelist/chrome-river 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.

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

APIs 15

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

Chrome River Accounts API

The Accounts API from Chrome River — 4 operation(s) for accounts.

Chrome River Allowances API

The Allowances API from Chrome River — 1 operation(s) for allowances.

Chrome River Cards API

The Cards API from Chrome River — 3 operation(s) for cards.

Chrome River Categories API

The Categories API from Chrome River — 2 operation(s) for categories.

Chrome River Company API

The Company API from Chrome River — 2 operation(s) for company.

Chrome River Departments API

The Departments API from Chrome River — 2 operation(s) for departments.

Chrome River Labels API

The Labels API from Chrome River — 2 operation(s) for labels.

Chrome River Locations API

The Locations API from Chrome River — 2 operation(s) for locations.

Chrome River Members API

The Members API from Chrome River — 3 operation(s) for members.

Chrome River Merchant Categories API

The Merchant Categories API from Chrome River — 1 operation(s) for merchant categories.

Chrome River OAuth API

The Oauth API from Chrome River — 3 operation(s) for oauth.

Chrome River Requisitions API

The Requisitions API from Chrome River — 2 operation(s) for requisitions.

Chrome River Shared Links API

The Shared Links API from Chrome River — 2 operation(s) for shared links.

Chrome River Shipping Addresses API

The Shipping Addresses API from Chrome River — 2 operation(s) for shipping addresses.

Chrome River Transactions API

The Transactions API from Chrome River — 2 operation(s) for transactions.

Scroll for all 15

Agent Skills 5

Packaged agent skills for driving this provider's APIs from an AI assistant.

chrome-river-create-and-retrieve-card

AGENT SKILL

chrome-river-create-member

AGENT SKILL

chrome-river-manage-location

AGENT SKILL

chrome-river-requisition-workflow

AGENT SKILL

chrome-river-shipping-addresses-create-and-retrieve

AGENT SKILL

Chrome River API pricing

Prices published by Chrome River, read 2026-10-08 from www.emburse.com/products/spend/pricing.

Plan	Price
Basic	$8 per user/month
Plus	$12 per user/month
Custom	Custom speak to sales

Plan details, limits and sources →

Billed by: seat · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Chrome River Plans Pricing

3 plans

PLANS

Chrome River Price Estimates

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Chrome River

SLA

FinOps 1

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

Chrome River Finops

FINOPS

Semantic Vocabularies 1

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

Chrome River Context

14 classes · 101 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Chrome River API Rules

16 rules · 12 errors 1 warnings 3 info

SPECTRAL

JSON Schema 6

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

APIAccount

13 properties

JSON SCHEMA

APICard

22 properties

JSON SCHEMA

APICompany

9 properties

JSON SCHEMA

APIRequisition

23 properties

JSON SCHEMA

APIStatementLine

16 properties

JSON SCHEMA

APITransaction

28 properties

JSON SCHEMA

Security Posture 3

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

Chrome River Authentication

http · 1 scheme

SECURITY

Chrome River Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Chrome River Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 7

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

TrustCenter

Security

Authentication

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Scroll for all 7

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

PrivacyPolicy

PrivacyPolicy

Pricing

Pricing

Company 3

The organization behind the API

Newsroom

Newsroom

Blog

Blog

Website

Website

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Leadership

Leadership

Source (apis.yml)

aid: chrome-river
name: Chrome River
description: Chrome River provides enterprise expense and invoice management solutions, now operating as part of Emburse.
  The platform offers automated expense reporting, compliance controls, analytics, and integration capabilities for large
  organizations, helping streamline travel and spend processes across global operations. It supports multi-currency handling,
  policy enforcement, receipt capture via mobile, and integrates with ERP, accounting, and travel booking systems, delivering
  comprehensive spend visibility and control for enterprises worldwide.
url: https://raw.githubusercontent.com/api-evangelist/chrome-river/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-08 (modular-v1; was harvest)
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.20'
created: '2026-10-08'
modified: '2026-10-08'
tags:
- Finance
- Expense Management
- Software-as-a-Service
- Enterprise
- Travel
tags_raw:
- Finance
- Expense Management
- SaaS
- Enterprise
- Travel
image: https://cdn.sanity.io/images/l5mo20ew/production/426919841ea68610738e9779779d780ee71f3dd0-138x24.svg
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/chrome-river-plans-pricing.yml
- type: Spectral
  url: rules/chrome-river-rules.yml
- type: JSONLD
  url: json-ld/chrome-river-context.jsonld
- type: Vocabulary
  url: vocabulary/chrome-river-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/chrome-river-data-model.yml
- type: ErrorCatalog
  url: errors/chrome-river-problem-types.yml
- type: Conformance
  url: conformance/chrome-river-conformance.yml
- type: LLMsTxt
  url: llms/chrome-river-llms.txt
- type: SecurityTxt
  url: well-known/chrome-river-security.txt
- type: SecurityTxt
  url: well-known/chrome-river-my-security.txt
- type: WellKnown
  url: well-known/chrome-river-well-known.yml
- type: Hosts
  url: hosts/chrome-river-hosts.yml
- type: Vendors
  url: vendors/chrome-river-vendors.yml
- type: TrustCenter
  url: https://trust.emburse.com/
- type: Support
  url: https://help.emburse.com/hc/en-us
- type: Security
  url: https://www.emburse.com/uk/legal/security
- type: PrivacyPolicy
  url: https://www.emburse.com/uk/legal/privacy-policy
- type: Pricing
  url: https://www.emburse.com/products/spend/pricing
- type: Newsroom
  url: https://www.emburse.com/company/news
- type: Login
  url: https://www.emburse.com/login
- type: Leadership
  url: https://www.emburse.com/company/leadership
- type: Blog
  url: https://www.emburse.com/blog
- type: Documentation
  url: https://help.billing.emburse.com/
- type: GitHubOrganization
  url: https://github.com/emburse
- type: Authentication
  url: authentication/chrome-river-authentication.yml
- type: VulnerabilityDisclosure
  url: security/chrome-river-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/chrome-river-domain-security.yml
- type: Website
  url: https://www.emburse.com/products/chrome-river-is-enterprise
apis:
- aid: chrome-river:chrome-river-accounts-api
  name: Chrome River Accounts API
  description: The Accounts API from Chrome River — 4 operation(s) for accounts.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-accounts-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-allowances-api
  name: Chrome River Allowances API
  description: The Allowances API from Chrome River — 1 operation(s) for allowances.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Allowances
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-allowances-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-cards-api
  name: Chrome River Cards API
  description: The Cards API from Chrome River — 3 operation(s) for cards.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Cards
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-cards-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-categories-api
  name: Chrome River Categories API
  description: The Categories API from Chrome River — 2 operation(s) for categories.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Categories
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-categories-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-company-api
  name: Chrome River Company API
  description: The Company API from Chrome River — 2 operation(s) for company.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Company
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-company-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-departments-api
  name: Chrome River Departments API
  description: The Departments API from Chrome River — 2 operation(s) for departments.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Departments
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-departments-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-labels-api
  name: Chrome River Labels API
  description: The Labels API from Chrome River — 2 operation(s) for labels.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Labels
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-labels-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-locations-api
  name: Chrome River Locations API
  description: The Locations API from Chrome River — 2 operation(s) for locations.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Location
  tags_raw:
  - Locations
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-locations-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-members-api
  name: Chrome River Members API
  description: The Members API from Chrome River — 3 operation(s) for members.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Members
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-members-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-merchant-categories-api
  name: Chrome River Merchant Categories API
  description: The Merchant Categories API from Chrome River — 1 operation(s) for merchant categories.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Merchant Categories
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-merchant-categories-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-oauth-api
  name: Chrome River OAuth API
  description: The Oauth API from Chrome River — 3 operation(s) for oauth.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - Oauth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-oauth-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-requisitions-api
  name: Chrome River Requisitions API
  description: The Requisitions API from Chrome River — 2 operation(s) for requisitions.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Requisitions
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-requisitions-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-shared-links-api
  name: Chrome River Shared Links API
  description: The Shared Links API from Chrome River — 2 operation(s) for shared links.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Shared Links
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-shared-links-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-shipping-addresses-api
  name: Chrome River Shipping Addresses API
  description: The Shipping Addresses API from Chrome River — 2 operation(s) for shipping addresses.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Shipping Addresses
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-shipping-addresses-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
- aid: chrome-river:chrome-river-transactions-api
  name: Chrome River Transactions API
  description: The Transactions API from Chrome River — 2 operation(s) for transactions.
  humanURL: https://www.emburse.com/products/chrome-river-is-enterprise
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/chrome-river-transactions-api-openapi.yml
  - type: JSONSchema
    url: json-schema/chrome-river-apicard-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apistatement-line-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apirequisition-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apitransaction-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apicompany-schema.json
  - type: JSONSchema
    url: json-schema/chrome-river-apiaccount-schema.json
x-enrichment:
  date: '2026-10-08'
  status: enriched
  artifacts_added: 30
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Chrome River API — frequently asked questions

Does Chrome River have an API?

Yes. APIs.io lists 15 APIs from Chrome River, including Chrome River Accounts API, Chrome River Allowances API and Chrome River Cards API, and 12 more.

Is there an OpenAPI specification for the Chrome River API?

Yes. APIs.io indexes 15 OpenAPI specifications for Chrome River, each linked for download from this page.

How do I authenticate with the Chrome River API?

Chrome River uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Chrome River Authentication.

How much does the Chrome River API cost?

Chrome River publishes its prices; its Basic plan is $8 per user/month as of 2026-10-08. APIs.io lists 3 pricing plans for Chrome River, with each plan's price, limits and inclusions under Pricing on this page.

Is the Chrome River API ready for AI agents?

Chrome River has a Kin Score of 45.3 out of 100 (developing) and an Agent Readiness score of 25.3 (agent-aware), 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/chrome-river"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/chrome-river/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.