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

M3ter DebitReason API

Endpoints for DebitReason operations such as creation, update, list, and delete. You can create DebitReasons for your Organization, and then use them when creating a debit line item on a bill, or applying a product debit to a bill. DebitReasons provide contextual information as to why a debit was applied.

M3ter DebitReason API is one of 58 APIs that M3ter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.m3ter.com.

5 operations 2 paths 7 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.m3ter.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

M3ter DebitReason API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials and authorizationCode flows, exposing 6 scopes. By default, every request must be authenticated.

  • OAuth2 — m3ter supports machine to machine authentication using the clientCredentials OAuth2 flow. The authorizationCode flow controls access for human users via the m3…

Paths & Operations 5

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

DebitReason 5

Endpoints for DebitReason operations such as creation, update, list, and delete. You can create DebitReasons for your Organization, and then use them when creating a debit line it…

GET
/organizations/{orgId}/picklists/debitreasons
List Debit Reasons
ListDebitReasons 6 params → 2004XX5XX
POST
/organizations/{orgId}/picklists/debitreasons
Create Debit Reason
CreateDebitReason 1 param body → 2004XX5XX
GET
/organizations/{orgId}/picklists/debitreasons/{id}
Retrieve Debit Reason
GetDebitReason 2 params → 2004XX5XX
PUT
/organizations/{orgId}/picklists/debitreasons/{id}
Update Debit Reason
UpdateDebitReason 2 params body → 2004XX5XX
DELETE
/organizations/{orgId}/picklists/debitreasons/{id}
Delete Debit Reason
DeleteDebitReason 2 params → 2004XX5XX

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are AbstractResponse (2 properties), PaginatedDebitReasonResponseData (2 properties), AbstractRequest (1 property). Each schema is shown below with its type and property counts.

DebitReasonResponse
object
PaginatedDebitReasonResponseData
object
2 properties
AbstractResponse
object
2 properties 1 required
DebitReasonRequest
object
AbstractPickListRequest
object
AbstractRequest
object
1 property
AbstractPickListResponse
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

m3ter-debitreason-api-openapi.yml Raw ↑

Other APIs M3ter publishes across the network.

M3ter Account API
M3ter AccountPlan API
M3ter Aggregation API
M3ter Auth API
M3ter BalanceChargeSchedule API
M3ter Balances API
M3ter BalanceTransactionSchedule API
M3ter Bill API
M3ter BillConfig API
M3ter BillGroupingKey API
M3ter BillJob API
M3ter Charge API
Where this information came from

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