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

MVMNT Bills API

AP bill management operations.Bills represent carrier and vendor invoices to be paid.

MVMNT Bills API is one of 27 APIs that MVMNT publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bills. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.

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

Requests are made against a single base URL, https://api.mvmnt.io/v1.

11 operations 9 paths 24 schemas 1 DELETE3 GET1 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.mvmnt.io/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

MVMNT Bills API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — OAuth 2.0 access token obtained via client credentials flow

Paths & Operations 11

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

Bills 11

AP bill management operations. Bills represent carrier and vendor invoices to be paid.

POST
/bills/filter
Filter bills
filterBills body → 200400401422
POST
/bills
Record a bill
createBill body → 201400401409422
GET
/bills/{id}
Get a bill
getBill 2 params → 200401404
PATCH
/bills/{id}
Update a bill
updateBill 2 params body → 200400401404409422
DELETE
/bills/{id}
Delete a bill
deleteBill 2 params → 204401404409
POST
/bills/{id}/approve
Approve bill for payment
approveBill 2 params → 200401404409
POST
/bills/batch-approve
Batch approve bills
batchApproveBills body → 200400401
POST
/bills/{id}/unapprove
Unapprove bill
unapproveBill 2 params → 200401404409
POST
/bills/{id}/revert
Revert bill to awaiting invoice
revertBill 2 params body → 200401404
GET
/bills/{id}/payments
Get bill payments
getBillPayments 2 params → 200401404
GET
/bills/aging-report
Get AP aging report
getApAgingReport 5 params → 200401

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Bill (28 properties), BillFilter (17 properties), PaymentTermReference (11 properties), VendorReference (10 properties). Each schema is shown below with its type and property counts.

FloatFilter
object
Filter options for float/number fields
7 properties
ValidationError
object
3 properties 3 required
Error
object
2 properties 2 required
CarrierFactorReference
object
Enhanced reference to a carrier factor (factoring company). Includes full carrier factor details in addition to id/key.
8 properties 4 required
CarrierReference
object
Enhanced reference to a carrier resource (returned in responses). Includes full carrier details in addition to id/key. Note: Does NOT include nested references…
8 properties 4 required
BillFilter
object
17 properties
Bill
object
28 properties 6 required
BillPaymentApplied
object
5 properties
BillFilterRequest
object
3 properties
RevertBillRequest
object
1 property
PaginationInfo
object
4 properties 2 required
PaymentTermReference
object
Enhanced reference to a payment term resource (returned in responses). Includes full payment term details in addition to id/key.
11 properties 4 required
UUIDFilter
object
Filter options for UUID fields (all operations)
5 properties
BillStatus
string
Current status of the bill (AP invoice). - AWAITINGINVOICE: Waiting for carrier/vendor to submit invoice - INREVIEW: Invoice received, under review - APPROVEDT…
BillEntityType
string
Type of entity the bill is for. - CARRIER: Bill for a carrier (LoadCarrier) - VENDOR: Bill for a vendor service (VendedService)
DatetimeFilter
object
Filter options for datetime fields
7 properties
BillInput
object
8 properties 4 required
ApproveBillsResponse
object
2 properties
ApproveBillsRequest
object
1 property 1 required
BillStatusFilter
object
4 properties
ApAgingReportResponse
object
4 properties 4 required
BillPatch
object
5 properties
VendorReference
object
Enhanced reference to a vendor profile. Includes full vendor details in addition to id/key.
10 properties 5 required
BillEntityTypeFilter
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mvmnt-bills-api-openapi.yml Raw ↑

Other APIs MVMNT publishes across the network.

MVMNT Bill Payments API
MVMNT Carrier Contacts API
MVMNT Carrier Factors API
MVMNT Carrier Payment Methods API
MVMNT Carriers API
MVMNT Companies API
MVMNT Credit Memos API
MVMNT Customer Contacts API
MVMNT Customers API
MVMNT Documents API
MVMNT Invoices API
MVMNT Loads API
Where this information came from

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