Skip to content
API Reference/
/
Update a service

MVMNT API (1.0.0)

The MVMNT API enables you to automate freight brokerage workflows by integrating directly with our Transportation Management System.

Postman setup guide: API Clients.

Authentication

OAuth 2.0 client credentials flow. See Authentication Guide for details.

Token Endpoint

POST https://api.mvmnt.io/oauth2/token

Request

Headers:

Content-Type: application/x-www-form-urlencoded

Body Parameters:

grant_type=client_credentials
client_id=YOUR_CLIENT_ID
client_secret=YOUR_CLIENT_SECRET

Example Request

curl -X POST https://api.mvmnt.io/oauth2/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET"

Success Response

Status: 200 OK

{
  "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...",
  "token_type": "Bearer",
  "expires_in": 3600
}

Response Fields:

  • access_token: JWT Bearer token to use for API requests
  • token_type: Always Bearer
  • expires_in: Token lifetime in seconds (3600 = 1 hour)

Idempotency

Mutating requests (POST, PATCH, DELETE) accept an optional Idempotency-Key header (up to 255 characters). Retrying a request with the same key and the same body returns the original result instead of repeating the operation; reusing a key with a different body fails. Keys are scoped to your organization — keys chosen by other tenants can never collide with yours. Use a stable identifier from your system (for example your own record id plus the action) rather than a random value per attempt.

Download OpenAPI description
openapi.json
openapi.yaml
openapi-3.0.yaml (legacy tooling)
Postman Collection
Postman Environment — Demo
Postman Environment — Production
Overview
URL
https://docs.mvmnt.io
MVMNT Support
support@mvmnt.io
License
Proprietary
Languages
Servers
Production
https://api.mvmnt.io/v1
Demo (non-production)
https://api.demo.mvmnt.io/v1

Carriers

Carrier management operations

Operations

Carrier Contacts

Carrier contact management operations

Operations

Carrier Factors

Carrier factor (factoring company) management operations

Operations

Carrier Payment Methods

Carrier payment method management operations

Operations

Companies

Company management operations

Operations

Credit Memos

AR credit memo management operations. Credit memos represent customer credits that can be applied to invoices.

Operations

Bills

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

Operations

Bill Payments

AP bill payment management operations. Bill payments record payments made to carriers and vendors.

Operations

Customers

Customer management operations

Operations

Customer Contacts

Customer contact management operations

Operations

Documents

Document management operations. Documents are files (PDFs, images) that can be attached to orders, loads, or services.

Operations

Invoices

AR invoice management operations. Invoices represent customer billing for shipment services.

Operations

Loads

Load management operations. Loads represent carrier execution - which carrier is moving the freight.

Operations

Locations

Location management operations

Operations

Location Contacts

Location contact management operations

Operations

Payment Terms

Payment term management operations

Operations

Reference Data

Read-only catalogs (equipment, charge codes, special requirements) referenced by id from other resources.

Every catalog also answers on its short top-level path, so GET /v1/charge-codes and GET /v1/reference-data/charge-codes are the same endpoint. The documented /reference-data/* form is canonical — it keeps the catalogs grouped here as more are added (port codes, cities, zip codes) — and the short form is a convenience alias.

Operations

Payments

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

Operations

Quotes

Quote management operations. Quotes are pricing requests/responses that can be converted to shipments.

Operations

Saved Searches

Saved search management operations

Operations

Services

Service (vended service) management operations. Services represent non-carrier vendor work (drayage, customs, warehousing).

Operations

Filter services

Request

Search for services using filter criteria.

Common Filters

  • By shipment: { "filter": { "shipmentId": { "equalTo": "uuid" } } }
  • By vendor: { "filter": { "vendorId": { "equalTo": "uuid" } } }
  • Awaiting invoice: { "filter": { "status": { "equalTo": "AWAITING_INVOICE" } } }
Security
BearerAuth
Bodyapplication/jsonrequired
filterobject(ServiceFilter)
pageSizeinteger[ 1 .. 100 ]
Default 50
cursorstring
curl -i -X POST \
  https://api.mvmnt.io/v1/services/filter \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "filter": {
      "shipmentId": {
        "equalTo": "550e8400-e29b-41d4-a716-446655440000"
      }
    }
  }'

Responses

Services matching filter criteria

Bodyapplication/json
dataArray of objects(Service)required
idstring(uuid)required
Example: "550e8400-e29b-41d4-a716-446655440000"
keystring or null

Human-readable service ID

Example: "SVC-12345"
shipmentIdstring(uuid)

Parent shipment

shipmentKeystring or null

Parent shipment friendly ID

vendorobject(VendorReference)

Enhanced reference to a vendor profile. Includes full vendor details in addition to id/key.

vendorContactobject
statusstring(ServiceStatus)required

Current status of the service.

Active states:

  • ACTIVE: Service is active/in progress

Billing states (AP):

  • AWAITING_INVOICE: Waiting for vendor invoice
  • INVOICE_IN_REVIEW: Invoice received, under review
  • APPROVED_TO_PAY: Approved for payment
  • PAID: Paid to vendor

Final states:

  • CANCELED: Service canceled
Enum"ACTIVE""AWAITING_INVOICE""INVOICE_IN_REVIEW""APPROVED_TO_PAY""PAID""CANCELED"
descriptionstring or null

Service description

chargesArray of objects(ServiceCharge)

Flattened charges array

totalCostnumber or null

Sum of all charges

scheduledDatestring or null(date)
completedDatestring or null(date)
referenceNumberstring or null

Vendor reference number

createdAtstring(date-time)required
updatedAtstring or null(date-time)
paginationobject(PaginationInfo)required
pageSizeintegerrequired

Number of items per page

Example: 50
hasNextPagebooleanrequired

Whether there are more pages

Example: true
hasPreviousPageboolean

Whether there are previous pages

Example: false
endCursorstring or null

Cursor for the next page (null if no next page)

Example: "eyJpZCI6IjU1MGU4NDAwLWUyOWItNDFkNC1hNzE2LTQ0NjY1NTQ0MDAwMCJ9"
Response
application/json
{
  "data": [
    { … }
  ],
  "pagination": {
    "pageSize": 50,
    "hasNextPage": true,
    "hasPreviousPage": false,
    "endCursor": "eyJpZCI6IjU1MGU4NDAwLWUyOWItNDFkNC1hNzE2LTQ0NjY1NTQ0MDAwMCJ9"
  }
}

Create a service

Request

Create a new service for a shipment.

What happens

  • Service is created for the specified shipment
  • Vendor is associated with the service
  • Charges are recorded

Note

Services are typically created as part of shipment creation. Use this endpoint to add additional services to an existing shipment.

Security
BearerAuth
Bodyapplication/jsonrequired
shipmentIdstring(uuid)required

Parent shipment ID

serviceobject(ServiceInput)required
vendorobject(ResourceReferenceInput)required
One of:

Vendor reference

idstring(uuid)required

Resource UUID

keystring

Client-defined reference ID

vendorContactobject(ResourceReferenceInput)
One of:

Vendor contact

descriptionstring<= 2000 characters
chargesArray of objects
scheduledDatestring(date)
referenceNumberstring
curl -i -X POST \
  https://api.mvmnt.io/v1/services \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "shipmentId": "550e8400-e29b-41d4-a716-446655440000",
    "service": {
      "vendor": {
        "id": "660e8400-e29b-41d4-a716-446655440001"
      },
      "description": "Port drayage from Long Beach",
      "charges": [
        {
          "chargeCode": {
            "key": "DRAY"
          },
          "amount": 450
        }
      ],
      "scheduledDate": "2025-01-20"
    }
  }'

Responses

Service created successfully

Bodyapplication/json
idstring(uuid)required
Example: "550e8400-e29b-41d4-a716-446655440000"
keystring or null

Human-readable service ID

Example: "SVC-12345"
shipmentIdstring(uuid)

Parent shipment

shipmentKeystring or null

Parent shipment friendly ID

vendorobject(VendorReference)

Enhanced reference to a vendor profile. Includes full vendor details in addition to id/key.

vendorContactobject
statusstring(ServiceStatus)required

Current status of the service.

Active states:

  • ACTIVE: Service is active/in progress

Billing states (AP):

  • AWAITING_INVOICE: Waiting for vendor invoice
  • INVOICE_IN_REVIEW: Invoice received, under review
  • APPROVED_TO_PAY: Approved for payment
  • PAID: Paid to vendor

Final states:

  • CANCELED: Service canceled
Enum"ACTIVE""AWAITING_INVOICE""INVOICE_IN_REVIEW""APPROVED_TO_PAY""PAID""CANCELED"
descriptionstring or null

Service description

chargesArray of objects(ServiceCharge)

Flattened charges array

totalCostnumber or null

Sum of all charges

scheduledDatestring or null(date)
completedDatestring or null(date)
referenceNumberstring or null

Vendor reference number

createdAtstring(date-time)required
updatedAtstring or null(date-time)
Response
application/json
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "key": "SVC-12345",
  "shipmentId": "47efd5a2-af91-4417-950a-7f546cd1b5cf",
  "shipmentKey": "string",
  "vendor": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "key": "ERP-VENDOR-ABC-001",
    "friendlyId": "V123456",
    "name": "ABC Warehouse Services",
    "email": "billing@abcwarehouse.com",
    "phone": "+1-555-123-4567",
    "status": "ACTIVE",
    "currency": "USD",
    "createdAt": "2025-01-15T10:00:00Z",
    "updatedAt": "2025-01-15T14:30:00Z"
  },
  "vendorContact": {
    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
    "name": "string",
    "phone": "string",
    "email": "string"
  },
  "status": "ACTIVE",
  "description": "string",
  "charges": [
    { … }
  ],
  "totalCost": 0,
  "scheduledDate": "2019-08-24",
  "completedDate": "2019-08-24",
  "referenceNumber": "string",
  "createdAt": "2019-08-24T14:15:22Z",
  "updatedAt": "2019-08-24T14:15:22Z"
}

Get a service

Request

Retrieve a service by ID.

The response includes vendor info and charges.

Security
BearerAuth
Path
idstringrequired

Resource ID (UUID) or client key

Example: 550e8400-e29b-41d4-a716-446655440000
Query
bystring

Specify lookup type for faster retrieval. If omitted, defaults to looking up by ID first, then falls back to client key if not found. Use by=key when you know you're providing a client key for best performance.

Enum"id""key"
Example: by=key
curl -i -X GET \
  'https://api.mvmnt.io/v1/services/550e8400-e29b-41d4-a716-446655440000?by=key' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Service retrieved successfully

Bodyapplication/json
idstring(uuid)required
Example: "550e8400-e29b-41d4-a716-446655440000"
keystring or null

Human-readable service ID

Example: "SVC-12345"
shipmentIdstring(uuid)

Parent shipment

shipmentKeystring or null

Parent shipment friendly ID

vendorobject(VendorReference)

Enhanced reference to a vendor profile. Includes full vendor details in addition to id/key.

vendorContactobject
statusstring(ServiceStatus)required

Current status of the service.

Active states:

  • ACTIVE: Service is active/in progress

Billing states (AP):

  • AWAITING_INVOICE: Waiting for vendor invoice
  • INVOICE_IN_REVIEW: Invoice received, under review
  • APPROVED_TO_PAY: Approved for payment
  • PAID: Paid to vendor

Final states:

  • CANCELED: Service canceled
Enum"ACTIVE""AWAITING_INVOICE""INVOICE_IN_REVIEW""APPROVED_TO_PAY""PAID""CANCELED"
descriptionstring or null

Service description

chargesArray of objects(ServiceCharge)

Flattened charges array

totalCostnumber or null

Sum of all charges

scheduledDatestring or null(date)
completedDatestring or null(date)
referenceNumberstring or null

Vendor reference number

createdAtstring(date-time)required
updatedAtstring or null(date-time)
Response
application/json
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "key": "SVC-12345",
  "shipmentId": "47efd5a2-af91-4417-950a-7f546cd1b5cf",
  "shipmentKey": "string",
  "vendor": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "key": "ERP-VENDOR-ABC-001",
    "friendlyId": "V123456",
    "name": "ABC Warehouse Services",
    "email": "billing@abcwarehouse.com",
    "phone": "+1-555-123-4567",
    "status": "ACTIVE",
    "currency": "USD",
    "createdAt": "2025-01-15T10:00:00Z",
    "updatedAt": "2025-01-15T14:30:00Z"
  },
  "vendorContact": {
    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
    "name": "string",
    "phone": "string",
    "email": "string"
  },
  "status": "ACTIVE",
  "description": "string",
  "charges": [
    { … }
  ],
  "totalCost": 0,
  "scheduledDate": "2019-08-24",
  "completedDate": "2019-08-24",
  "referenceNumber": "string",
  "createdAt": "2019-08-24T14:15:22Z",
  "updatedAt": "2019-08-24T14:15:22Z"
}

Update a service

Request

Update service fields.

Note: Status changes happen automatically based on billing workflow.

Security
BearerAuth
Path
idstringrequired

Resource ID (UUID) or client key

Example: 550e8400-e29b-41d4-a716-446655440000
Query
bystring

Specify lookup type for faster retrieval. If omitted, defaults to looking up by ID first, then falls back to client key if not found. Use by=key when you know you're providing a client key for best performance.

Enum"id""key"
Example: by=key
Bodyapplication/jsonrequired
vendorContactobject(ResourceReferenceInput)
One of:

Reference to another resource by either ID or client key (used in create/update requests)

descriptionstring or null
scheduledDatestring or null(date)
completedDatestring or null(date)
referenceNumberstring or null
curl -i -X PATCH \
  'https://api.mvmnt.io/v1/services/550e8400-e29b-41d4-a716-446655440000?by=key' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "scheduledDate": "2025-01-22"
  }'

Responses

Service updated successfully

Bodyapplication/json
idstring(uuid)required
Example: "550e8400-e29b-41d4-a716-446655440000"
keystring or null

Human-readable service ID

Example: "SVC-12345"
shipmentIdstring(uuid)

Parent shipment

shipmentKeystring or null

Parent shipment friendly ID

vendorobject(VendorReference)

Enhanced reference to a vendor profile. Includes full vendor details in addition to id/key.

vendorContactobject
statusstring(ServiceStatus)required

Current status of the service.

Active states:

  • ACTIVE: Service is active/in progress

Billing states (AP):

  • AWAITING_INVOICE: Waiting for vendor invoice
  • INVOICE_IN_REVIEW: Invoice received, under review
  • APPROVED_TO_PAY: Approved for payment
  • PAID: Paid to vendor

Final states:

  • CANCELED: Service canceled
Enum"ACTIVE""AWAITING_INVOICE""INVOICE_IN_REVIEW""APPROVED_TO_PAY""PAID""CANCELED"
descriptionstring or null

Service description

chargesArray of objects(ServiceCharge)

Flattened charges array

totalCostnumber or null

Sum of all charges

scheduledDatestring or null(date)
completedDatestring or null(date)
referenceNumberstring or null

Vendor reference number

createdAtstring(date-time)required
updatedAtstring or null(date-time)
Response
application/json
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "key": "SVC-12345",
  "shipmentId": "47efd5a2-af91-4417-950a-7f546cd1b5cf",
  "shipmentKey": "string",
  "vendor": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "key": "ERP-VENDOR-ABC-001",
    "friendlyId": "V123456",
    "name": "ABC Warehouse Services",
    "email": "billing@abcwarehouse.com",
    "phone": "+1-555-123-4567",
    "status": "ACTIVE",
    "currency": "USD",
    "createdAt": "2025-01-15T10:00:00Z",
    "updatedAt": "2025-01-15T14:30:00Z"
  },
  "vendorContact": {
    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
    "name": "string",
    "phone": "string",
    "email": "string"
  },
  "status": "ACTIVE",
  "description": "string",
  "charges": [
    { … }
  ],
  "totalCost": 0,
  "scheduledDate": "2019-08-24",
  "completedDate": "2019-08-24",
  "referenceNumber": "string",
  "createdAt": "2019-08-24T14:15:22Z",
  "updatedAt": "2019-08-24T14:15:22Z"
}

Delete a service

Request

Soft delete a service.

Prerequisites

  • Service must not be paid
Security
BearerAuth
Path
idstringrequired

Resource ID (UUID) or client key

Example: 550e8400-e29b-41d4-a716-446655440000
Query
bystring

Specify lookup type for faster retrieval. If omitted, defaults to looking up by ID first, then falls back to client key if not found. Use by=key when you know you're providing a client key for best performance.

Enum"id""key"
Example: by=key
curl -i -X DELETE \
  'https://api.mvmnt.io/v1/services/550e8400-e29b-41d4-a716-446655440000?by=key' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

Service deleted successfully

Response
No content

Shipments

Shipment tracking and management operations. Shipments contain orders, loads, and services.

Operations

Teams

Team management operations

Operations

Users

User management operations

Operations

Vendors

Vendor management operations

Operations

Vendor Contacts

Vendor contact management operations

Operations

Vendor Payment Methods

Vendor payment method management operations

Operations

Event Notifications

Webhooks