How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Emburse Expense Controller V1 API

Retrieve expense report information and create draft expense reports

Emburse Expense Controller V1 API is one of 48 APIs that Emburse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include expense-controller-v1. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 6 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://service.chromeriver.com.

7 operations 6 paths 19 schemas 1 DELETE4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.emburse.com/v1/
License
Terms of Service
Resource Areas
1

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

expense-controller-v1 7

Retrieve expense report information and create draft expense reports

GET
/v1/expense-reports
Get list of reports summary by expense owner
getExpenseReportsUsingGET 5 params → 200400401403503
POST
/v1/expense-reports
Create a draft expense report
createExpenseReportUsingPOST 5 params body → 200400401402503
GET
/v1/expense-reports/{reportId}
Get details of report
getExpenseReportUsingGET_2 5 params → 200400401403503
DELETE
/v1/expense-reports/{reportId}/line-items
Delete an expense report line item
deleteExpenseReportLineItemUsingDELETE 6 params → 204400401403404503
POST
/v1/expense-reports/{reportId}/notes
Add a note to an expense report
createExpenseHeaderNoteUsingPOST 5 params body → 200400401402503
GET
/v1/expense-reports/{reportId}/tracking
Get expense report tracking details
getReportForTrackingUsingGET 4 params → 200400401403404503
GET
/v1/open-expense-reports
Get list of open expense reports
getOpenExpenseReportsUsingGET 3 params → 200400401503

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are ExpenseReportLineItem (55 properties), PerDiemLineItem (44 properties), ExpenseRoutingTrackingItem (38 properties), LineItemAllocation (32 properties). Each schema is shown below with its type and property counts.

ExpenseReport
object
24 properties
LineItemAllocationReference
object
16 properties
ExpenseHeaderNote
object
10 properties
PerDiemRate
object
2 properties
ComplianceItem
object
5 properties
ExpenseReportLineItemPersonGuest
object
7 properties
BudgetDetail
object
8 properties
ExpenseReportLineItem
object
55 properties
PerDiemLineItem
object
44 properties
Entity
object
7 properties
UserDefinedAttribute
object
9 properties
Person
object
8 properties
Comment
object
3 properties
OpenExpenseReport
object
3 properties
PersonEntities
object
5 properties
ExpenseRoutingTrackingItem
object
38 properties
LineItemAllocation
object
32 properties
ExpenseReportHeaderCreateModel
object
3 properties 2 required
PaLineItemType
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emburse-expense-controller-v1-api-openapi.yml Raw ↑

Other APIs Emburse publishes across the network.

Emburse Professional API
Emburse Spend API
Emburse Accounts API
Emburse Allocation API Controller V 1 API
Emburse Allocation API Controller V 2 API
Emburse Allocation API Controller V 3 API
Emburse Allowances API
Emburse Cards API
Emburse Categories API
Emburse Company API
Emburse Departments API
Emburse Entity Type API
Where this information came from

This is an independent, third-party profile of Emburse Expense Controller V1 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.