Emburse · Rate Limits

Emburse Rate Limits

Emburse does not publicly document specific numerical rate limits for its APIs. The Virtual Cards API (api.emburse.com) supports pagination with a maximum of 1000 records per request. The API returns HTTP 429 on throttling and uses standard retry-after semantics. Enterprise and partner API access is subject to limits negotiated with account managers. The Certify/Professional API base URL is api.certify.com/v1. Rate limit details for Enterprise REST APIs require contacting support@emburse.com.

Emburse Rate Limits is the machine-readable rate-limit profile for Emburse on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests and records per request.

Tagged areas include Expense Management, AP Automation, Corporate Cards, Virtual Cards, and Receipt Capture.

5 Limits
Expense ManagementAP AutomationCorporate CardsVirtual CardsReceipt CaptureReimbursementInvoice ProcessingFinanceFinTech

Limits

Virtual Cards API
requests · per minute
unspecified
Specific numerical limit not publicly documented. API returns 429 when throttled. Contact hi@emburse.com or account manager for current limits.
Virtual Cards API pagination
records per request · per request
1000
Maximum of 1000 records returned per paginated list request using limit and offset query parameters.
Enterprise REST APIs
requests · per minute
unspecified
Rate limits for Emburse Enterprise (Chrome River) REST APIs are not publicly documented. Contact support@emburse.com for specifications.
Professional API (Certify)
requests · per minute
unspecified
Rate limits for Emburse Professional (api.certify.com/v1) are not publicly documented. Contact hi@emburse.com for current limits.
Spend API
requests · per minute
unspecified
Available to Partners and Plus plan customers. Specific rate limits are not publicly documented. OAuth 2.0 access tokens do not expire but can be revoked by administrators.