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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
MVMNT

MVMNT Customer Contacts API

Customer contact management operations

Documentation Provider Profile APIs.io OpenAPI GitHub

MVMNT Customer 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 Customer 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 22 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 22 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
Contact
MVMNT Support
License
Proprietary
Resource Areas
1

Authentication & Security 1

MVMNT Customer 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.

Customer Contacts 5

Customer contact management operations

POST
/customer-contacts/filter
Filter customer contacts
filterCustomerContacts body → 200400401500
POST
/customer-contacts
Create customer contact
createCustomerContact body → 201400401409500
GET
/customer-contacts/{id}
Get customer contact
getCustomerContactById 1 param → 200400401404500
PATCH
/customer-contacts/{id}
Update customer contact
updateCustomerContact 1 param body → 200400401404409500
DELETE
/customer-contacts/{id}
Delete customer contact
deleteCustomerContact 1 param → 204400401404500

Schemas 22

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

ContactInfo
object
Contact information details (nested, without id). This is an embedded object representing a Contact record. The id is managed internally and not exposed in the…
4 properties 1 required
CustomerContactPatch
object
Partial contact update. All fields are optional. - Omitted fields: Not modified (current value preserved) - Provided fields: Updated to the new value - Null va…
7 properties
ContactInfoInput
object
Contact information for creating a new contact record
4 properties 1 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
CustomerContactFilter
object
Filter criteria for contacts with AND/OR logic support
17 properties
CustomerContactType
string
Type of customer contact role
UUIDFilter
object
Filter options for UUID fields (all operations)
5 properties
CustomerContactFilterRequest
object
Request body for filtering contacts
3 properties
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
ContactInfoPatch
object
Partial contact information update. All fields are optional. - Omitted fields: Not modified (current value preserved) - Provided fields: Updated to the new val…
4 properties
CustomerContactInput
object
8 properties 3 required
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
DatetimeFilter
object
Filter options for datetime fields
7 properties
IDFilter
object
Filter options for ID fields (limited operations - exact match only)
2 properties
StringFilter
object
Filter options for string fields
11 properties
CustomerContact
object
14 properties 6 required
CustomerContactNotificationTypeFilter
object
Filter for notification type enum array field
3 properties
CustomerContactTypeFilter
object
Filter for contact type enum array field
3 properties
CustomerContactNotificationType
string
Types of shipment notifications the contact should receive

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mvmnt-customer-contacts-api-openapi.yml Raw ↑

Other APIs MVMNT publishes across the network.

MVMNT Bill Payments API
AE Profile APIs.io
MVMNT Bills API
AE Profile APIs.io
MVMNT Carrier Contacts API
AE Profile APIs.io
MVMNT Carrier Factors API
AE Profile APIs.io
MVMNT Carrier Payment Methods API
AE Profile APIs.io
MVMNT Carriers API
AE Profile APIs.io
MVMNT Companies API
AE Profile APIs.io
MVMNT Credit Memos API
AE Profile APIs.io
MVMNT Customers API
AE Profile APIs.io
MVMNT Documents API
AE Profile APIs.io
MVMNT Invoices API
AE Profile APIs.io
MVMNT Loads API
AE Profile APIs.io
#Customer Contacts
← Back to M APIs
API Details
ID
mvmnt:mvmnt-customer-contacts-api
Base URL
https://api.mvmnt.io/v1
Docs
https://docs.mvmnt.io/
Provider
MVMNT
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=mvmnt-customer-contacts-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mvmnt-customer-contacts-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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