E

emburse.com

Emburse provides spend management, expense management, travel, cards, invoice, and AP automation products for businesses. Its platform includes separate product lines such as Emburse Cards, Emburse Spend, and Emburse Enterprise (Chrome River).

3 integrations · REST

Emburse exposes three documented REST API surfaces: Emburse Cards (`api.emburse.com`), Emburse Spend (`spend.emburse.com` with OpenAPI YAML), and Emburse Enterprise REST APIs (`service.chromeriver.com`) documented as multiple Swagger/OpenAPI documents; no public GraphQL, MCP, or CLI surfaces were found on emburse.com.

discovered 2mo ago
REST · OpenAPI3
Credentials
Emburse Cards access tokenbearerGet token ↗

First create an app from the Applications page after Support grants developer permissions. Then generate an access token from the app's settings page as described in the Cards API docs. Use that token in API requests for your company.

Emburse Spend OAuth app (client_id + client_secret)oauth2Set up OAuth ↗

API access is limited to Partners and Enterprise customers. Contact your Emburse representative to have a client registered manually, providing your redirect_uri; Emburse then issues a client_id and client_secret. The auth flow and endpoints are documented in the Spend API portal and overview article Emburse Spend API.

Emburse Enterprise API keyapi_key

Have Emburse Support enable REST API access and API Key Management for your organization. Then an admin opens Security > API Key Management in Emburse Enterprise Admin Settings and clicks Generate API Key. The key is shown once and copied to the clipboard. Docs: REST Image API Migration Guide, REST API Integrations Overview.

Emburse Enterprise customer identifier (`customer-code` / `customer-id`)compound

Use the customer identifier Emburse provides for your organization when enabling REST integrations. Enterprise REST API docs require either customer-code or customer-id headers depending on the endpoint, alongside an API key. The setup references the same Enterprise integration enablement described in the REST API Integrations Overview and REST Image API Migration Guide.

conventions · 1/8 published

Publish these signals → /publishing