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

Veem invoice-controller API

Invoice Controller

Veem invoice-controller API is one of 14 APIs that Veem publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version v1.2.1.

Requests are made against a single base URL, //sandbox-api.veem.com.

4 operations 4 paths 10 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1.2.1
Base URL
https://api.veem.com
Resource Areas
1

Paths & Operations 4

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

invoice-controller 4

Invoice Controller

POST
/veem/v1.2/invoices/{invoiceId}/approve
approveInvoice
approveInvoiceUsingPOST_2 1 param → 200400401403404500
POST
/veem/v1.2/invoices/{invoiceId}/cancel
cancelInvoice
cancelInvoiceUsingPOST_2 1 param → 200400401403404500
POST
/veem/v1.2/invoices
createInvoice
createInvoiceUsingPOST_2 body → 200201400401403404500
GET
/veem/v1.2/invoices/{invoiceId}
getInvoice
getInvoiceUsingGET_2 1 param → 200400401403404500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are InvoiceResponse (16 properties), InvoiceRequest (12 properties), SimpleAccount (8 properties), ExchangeRateResponse (8 properties). Each schema is shown below with its type and property counts.

InvoiceRequest
object
12 properties 3 required
ContactBusinessRequest
object
3 properties 3 required
InvoiceResponse
object
16 properties 7 required
SimpleAccount
object
8 properties 8 required
BusinessAddressRequest
object
6 properties 5 required
ExchangeRateResponse
object
8 properties 7 required
JSONObject
object
ErrorResponse
object
4 properties 3 required
FileAttachment
object
3 properties 3 required
AlignMonetaryAmount
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

veem-invoice-controller-api-openapi.yml Raw ↑

Other APIs Veem publishes across the network.

Veem attachment-controller API
Veem bank-account-controller API
Veem beneficial-owner-information-controller API
Veem claimless-payment-controller API
Veem contact-controller API
Veem crypto-wallet-controller API
Veem customer-controller API
Veem exchange-rate-controller API
Veem meta-controller API
Veem open-account-controller API
Veem payment-controller API
Veem wallet-controller API
Where this information came from

This is an independent, third-party profile of Veem invoice-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.