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 invoice-api-external-controller API

Operations in Invoice Api

Emburse invoice-api-external-controller API is one of 48 APIs that Emburse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 9 operations across 9 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

9 operations 9 paths 11 schemas 2 GET5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 2 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

invoice-api-external-controller 9

Operations in Invoice Api

PUT
/v1/invoice-api/invoices
Returns invoices by InvoiceFilter.
getInvoicesUsingPUT 3 params body → 200
GET
/v1/invoice-api/invoices/images/pdf
Returns images/invoice-report in pdf file format.
getImagesInPdfUsingGET 7 params → 200
PUT
/v1/invoice-api/invoices/payments
Get invoice payment
getInvoicePaymentsUsingPUT 3 params body → 200401503
POST
/v1/invoice-api/invoices/sdi/xml
Post SDI invoice xml
postInvoicePaymentStatusUsingPOST 3 params body → 200201401503
POST
/v1/invoice-api/invoices/{invoiceId}/approve
Approve Specified Invoice
approveInvoiceUsingPOST 5 params body → 200400410
POST
/v1/invoice-api/invoices/{invoiceId}/assign
Assign Specified Invoice To Person Or Entity
assignInvoiceUsingPOST 5 params body → 200400410
GET
/v1/invoice-api/invoices/{invoiceId}/ocr/images
Get images uploaded for OCR
getInvoiceOcrImagesReportUsingGET 4 params → 200204401
POST
/v1/invoice-api/invoices/{invoiceId}/payment
Post paid invoice data
postInvoicePaymentStatusExternalUsingPOST 5 params body → 200422
POST
/v1/invoice-api/invoices/{invoiceId}/return
Return Specified Invoice
returnInvoiceUsingPOST 5 params body → 200400410

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are InvoicePaymentExternal (17 properties), InvoicePaymentCustomer (10 properties), InvoicePaymentOutput (9 properties), InvoiceAssignOptionsExternal (9 properties). Each schema is shown below with its type and property counts.

InvoicePaymentOutput
object
9 properties 5 required
InvoiceSubmitOptionsExternal
object
6 properties 4 required
InvoicePaymentExternal
object
17 properties 4 required
InvoiceError
object
9 properties
InvoiceHeaderSDI
object
6 properties
InvoicePaymentFilter
object
3 properties
InvoiceAssignOptionsExternal
object
9 properties 7 required
InvoicePaymentCustomer
object
10 properties 4 required
InvoiceFilter
object
2 properties 2 required
InvoiceSDIResponse
object
2 properties
Invoice
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emburse-invoice-api-external-controller-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 invoice-api-external-controller 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.