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 Payment Terms API

Payment term management operations

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

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

This API exposes 5 operations across 3 paths, and defines 15 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.

5 operations 3 paths 15 schemas 1 DELETE1 GET1 PATCH2 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 Payment Terms 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 5

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

Payment Terms 5

Payment term management operations

POST
/payment-terms/filter
Filter payment terms
filterPaymentTerms body → 200400401422429
POST
/payment-terms
Create payment term
createPaymentTerm body → 201400401422429
GET
/payment-terms/{id}
Get payment term
getPaymentTerm 2 params → 200401404429
PATCH
/payment-terms/{id}
Update payment term
updatePaymentTerm 2 params body → 200400401404422429
DELETE
/payment-terms/{id}
Delete payment term
deletePaymentTerm 2 params → 204401404429

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are PaymentTermFilter (14 properties), PaymentTerm (11 properties), StringFilter (11 properties), IntFilter (9 properties). Each schema is shown below with its type and property counts.

PaymentTerm
object
11 properties 4 required
FloatFilter
object
Filter options for float/number fields
7 properties
ValidationError
object
3 properties 3 required
BooleanFilter
object
Filter options for boolean fields
3 properties
Error
object
2 properties 2 required
ClientKeyFilter
object
Filter options for client key fields (limited operations - exact match only)
3 properties
PaginationInfo
object
4 properties 2 required
IntFilter
object
Filter options for integer fields
9 properties
PaymentTermPatch
object
Partial payment term update. All fields are optional. - Omitted fields: Not modified (current value preserved) - Provided fields: Updated to the new value - Nu…
7 properties
PaymentTermFilter
object
Filter criteria for payment terms with AND/OR logic support
14 properties
DatetimeFilter
object
Filter options for datetime fields
7 properties
IDFilter
object
Filter options for ID fields (limited operations - exact match only)
2 properties
PaymentTermFilterRequest
object
Request body for filtering payment terms
3 properties
StringFilter
object
Filter options for string fields
11 properties
PaymentTermInput
object
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mvmnt-payment-terms-api-openapi.yml Raw ↑

Other APIs MVMNT publishes across the network.

MVMNT Bill Payments API
MVMNT Bills 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
Where this information came from

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