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 Payments API

AR payment management operations.Payments represent received customer payments applied to invoices.

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

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

This API exposes 6 operations across 4 paths, and defines 19 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.

6 operations 4 paths 19 schemas 1 DELETE2 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 Payments 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 6

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

Payments 6

AR payment management operations. Payments represent received customer payments applied to invoices.

POST
/payments/filter
Filter payments
filterPayments body → 200400401422
POST
/payments
Create a payment
createPayment body → 201400401422
GET
/payments/{id}
Get a payment
getPayment 2 params → 200401404
PATCH
/payments/{id}
Update a payment
updatePayment 2 params body → 200400401404422
DELETE
/payments/{id}
Delete a payment
deletePayment 2 params → 204401404409
GET
/payments/{id}/applications
Get payment applications
getPaymentApplications 2 params → 200401404

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Payment (18 properties), PaymentFilter (12 properties), StringFilter (11 properties), CustomerReference (10 properties). Each schema is shown below with its type and property counts.

PaymentFilterRequest
object
3 properties
FloatFilter
object
Filter options for float/number fields
7 properties
ValidationError
object
3 properties 3 required
Error
object
2 properties 2 required
PaymentInput
object
7 properties 3 required
PaymentPatch
object
6 properties
PaymentCreditApplication
object
4 properties
PaymentCreditApplicationInput
object
2 properties 2 required
PaginationInfo
object
4 properties 2 required
UUIDFilter
object
Filter options for UUID fields (all operations)
5 properties
PaymentApplication
object
6 properties 3 required
CustomerReference
object
Enhanced reference to a customer resource (returned in responses). Includes full customer details in addition to id/key. Note: Does NOT include nested referenc…
10 properties 6 required
DatetimeFilter
object
Filter options for datetime fields
7 properties
StringFilter
object
Filter options for string fields
11 properties
payments_PaymentMethodTypeFilter
object
3 properties
PaymentFilter
object
12 properties
payments_PaymentMethodType
string
Payment method type. - ACHWIRE: ACH or wire transfer - ZELLE: Zelle payment - VENMO: Venmo payment - CHECK: Paper check - EFTDIRECTDEPOSIT: EFT direct deposit…
PaymentApplicationInput
object
2 properties 2 required
Payment
object
18 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mvmnt-payments-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 Payments 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.