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-approval-controller-v1 API

Approve, return and reassign expense reports.

Emburse expense-approval-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-approval-controller-v1. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 13 operations across 13 paths, and defines 23 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.

13 operations 13 paths 23 schemas 1 DELETE4 GET8 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 13

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

expense-approval-controller-v1 13

Approve, return and reassign expense reports.

GET
/v1/expense-report-approvals
Get list of reports for approval
getApprovalsUsingGET 4 params → 200400401403503
GET
/v1/expense-report-approvals/count
Get count of reports for approval
getExpenseReportCountUsingGET 4 params → 200400401403503
GET
/v1/expense-report-approvals/{reportId}
Get expense report details
getExpenseReportUsingGET 5 params → 200400401403404503
POST
/v1/expense-report-approvals/{reportId}/submit
Submit an expense report for approval
submitExpenseReportForApprovalUsingPOST 5 params body → 200400422503
POST
/v1/expense-reports/{report-id}/line-items/{report-line-item-id}/approve
Approve an expense report line item
approveExpenseReportLineItemUsingPOST 6 params body → 200400401403503
POST
/v1/expense-reports/{report-id}/line-items/{report-line-item-id}/reassign
Reassign an expense report line item
reassignExpenseReportLineItemUsingPOST 6 params body → 200400401403503
POST
/v1/expense-reports/{report-id}/line-items/{report-line-item-id}/return
Return an expense report line item
returnExpenseReportLineItemUsingPOST 6 params body → 200400401403503
DELETE
/v1/expense-reports/{reportId}
Delete an expense report
deleteExpenseReportUsingDELETE 5 params → 204401403404503
POST
/v1/expense-reports/{reportId}/approve
Approve an expense report
approveExpenseReportUsingPOST 5 params body → 200400401403503
POST
/v1/expense-reports/{reportId}/reassign
Reassign an expense report
reassignExpenseReportUsingPOST 5 params body → 200400401403503
POST
/v1/expense-reports/{reportId}/return
Return an expense report
returnExpenseReportUsingPOST 5 params body → 200400401403503
POST
/v1/expense-reports/{reportId}/submit
Submit an expense report
submitExpenseReportUsingPOST 5 params body → 200400401403422503
GET
/v1/trip-reports-summary
Get trips and expense reports summary details
getTripReportsSummaryUsingGET 4 params → 200400401403503

Schemas 23

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

TripReportSummary
object
13 properties
Comment
object
3 properties
ExpenseSubmit
object
3 properties
TripReportSummaryHeader
object
2 properties
LineItemAllocation
object
32 properties
PaLineItemType
object
4 properties
UserDefinedAttribute
object
9 properties
Person
object
8 properties
ExpenseSubmitResponse
object
3 properties
ExpenseReportLineItemPersonGuest
object
7 properties
ExpenseReportLineItem
object
55 properties
BudgetDetail
object
8 properties
RecordLocator
object
2 properties
NotesModel
object
1 property
ExpenseReport
object
24 properties
LineItemAllocationReference
object
16 properties
CountModel
object
1 property
PersonEntities
object
5 properties
ComplianceItem
object
5 properties
PerDiemLineItem
object
44 properties
PerDiemRate
object
2 properties
Entity
object
7 properties
ReassignModelV1
object
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emburse-expense-approval-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-approval-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.