Emburse Enterprise REST APIs

REST discovered

Details

URL: https://service.chromeriver.com/
Spec: https://service.chromeriver.com/personapi-docs
Spec (service.chromeriver.com): https://service.chromeriver.com/allocationapi-docs
Spec (service.chromeriver.com): https://service.chromeriver.com/entityapi-docs
Spec (service.chromeriver.com): https://service.chromeriver.com/expenseapi-docs
Spec (service.chromeriver.com): https://service.chromeriver.com/exportapi-docs
Spec (service.chromeriver.com): https://service.chromeriver.com/invoice-api-docs
Docs: https://www.emburse.com/enterprise/implementation-toolkit/rest-api-specifications

Authentication

Emburse Enterprise API key x-api-key: <credential> + Emburse Enterprise customer identifier (`customer-code` / `customer-id`) customer-code: <credential> discovered

Emburse Enterprise API key api_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.

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

customer-id: <credential>