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 Vendor Contacts API

Vendor contact management operations

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

Tagged areas include Vendor Contacts. 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 14 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 14 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 Vendor Contacts 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.

Vendor Contacts 5

Vendor contact management operations

POST
/vendor-contacts/filter
Filter vendor contacts
filterVendorContacts body → 200400401500
POST
/vendor-contacts
Create a new vendor contact
createVendorContact body → 201400401409500
GET
/vendor-contacts/{id}
Get a vendor contact by ID
getVendorContactById 1 param → 200400401404500
PATCH
/vendor-contacts/{id}
Update a vendor contact
updateVendorContact 1 param body → 200400401404409500
DELETE
/vendor-contacts/{id}
Delete a vendor contact
deleteVendorContact 1 param → 204400401404500

Schemas 14

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

Error
object
2 properties 2 required
VendorContactInput
object
5 properties 1 required
PaginationInfo
object
4 properties 2 required
VendorContactPatch
object
Partial vendor contact update. All fields are optional. - Omitted fields: Not modified (current value preserved) - Provided fields: Updated to the new value -…
4 properties
VendorContact
object
9 properties 2 required
VendorContactFilterRequest
object
Request body for filtering vendor contacts
3 properties
UUIDFilter
object
Filter options for UUID fields (all operations)
5 properties
VendorContactRole
string
Type of vendor contact role
DatetimeFilter
object
Filter options for datetime fields
7 properties
UserReference
object
Enhanced reference to a user resource (returned in responses). Includes full user details in addition to id/key. Note: Does NOT include nested references (team…
11 properties 5 required
ResourceReference
object
Reference to another resource (returned in responses)
2 properties 1 required
StringFilter
object
Filter options for string fields
11 properties
VendorContactRoleFilter
object
Filter for contact role enum array field
3 properties
VendorContactFilter
object
Filter criteria for vendor contacts with AND/OR logic support
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mvmnt-vendor-contacts-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 Vendor Contacts 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.