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

MyCarrier Payment Management API

The Payment Management API from MyCarrier — 2 operation(s) for payment management.

MyCarrier Payment Management API is one of 34 APIs that MyCarrier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version public.

Requests are made against a single base URL, https://invoice.mycarriertms.com.

2 operations 2 paths 5 schemas 1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
public
Base URL
https://api.mycarriertms.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

MyCarrier Payment Management API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth).

Paths & Operations 2

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

Payment Management 2
POST
/api/v2/Integrations/Payments/Record
Records payment on the identified invoice.
body → 200400401403404
PUT
/api/v2/Integrations/Payments/{paymentId}
Modify the specific payment for the identified invoice.
1 param body → 200400401403404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MC.Invoice.API.Dtos.Integrations.IntegrationInvoiceRecordPaymentRequest (8 properties), MC.Invoice.API.Dtos.Integrations.IntegrationInvoicePaymentResponse (5 properties), Microsoft.AspNetCore.Mvc.ProblemDetails (5 properties), MC.Invoice.API.Dtos.Integrations.IntegrationInvoicePaymentStatusResponse (3 properties). Each schema is shown below with its type and property counts.

Microsoft.AspNetCore.Mvc.ProblemDetails
object
5 properties
MC.Invoice.API.Dtos.Integrations.IntegrationInvoicePaymentResponse
object
5 properties
MC.Invoice.API.Dtos.Integrations.IntegrationInvoiceRecordPaymentRequest
object
8 properties 2 required
MC.Invoice.Data.Enums.InvoiceStatusType
string
MC.Invoice.API.Dtos.Integrations.IntegrationInvoicePaymentStatusResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mycarrier-payment-management-api-openapi.yml Raw ↑

Other APIs MyCarrier publishes across the network.

MyCarrier Bulk Import API
MyCarrier Carrier Invoice Setting API
MyCarrier Customer Invoice Setting API
MyCarrier Dispatch API
MyCarrier Dispute API
MyCarrier Download API
MyCarrier Export API
MyCarrier Freight Assist API
MyCarrier Freight Audit API
MyCarrier Import API
MyCarrier Integrations API
MyCarrier Invoice API
Where this information came from

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