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
Metronome

Metronome Customers API

[Customers](https://docs.metronome.com/provisioning/create-customers/) in Metronome represent your users for all billing and reporting. Use these endpoints to create, retrieve, update, and archive customers and their billing configuration.

Documentation Provider Profile APIs.io OpenAPI GitHub

Metronome Customers API is one of 18 APIs that Metronome publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 15 operations across 14 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

15 operations 14 paths 28 schemas 2 GET13 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.metronome.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Metronome Customers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 15

Across 14 paths, the API surfaces 15 operations — 2 GET, 13 POST. Each is listed below with its method, path, parameters, and response codes.

Customers 15

[Customers](https://docs.metronome.com/provisioning/create-customers/) in Metronome represent your users for all billing and reporting. Use these endpoints to create, retrieve, up…

POST
/v1/customers/setBillableStatus
Set customer billable status
setCustomerBillableStatus-v1 body → 200400404
POST
/v1/customers/archive
Archive a customer
archiveCustomer-v1 body → 200400404
GET
/v1/customers/{customer_id}
Get a customer
getCustomer-v1 1 param → 200
GET
/v1/customers
List customers
listCustomers-v1 6 params → 200
POST
/v1/customers
Create a customer
createCustomer-v1 body → 200409
POST
/v1/customers/{customer_id}/setIngestAliases
Create or update customer ingest aliases
setIngestAliases-v1 1 param body → 200
POST
/v1/customers/{customer_id}/setName
Update a customer name
setCustomerName-v1 1 param body → 200
POST
/v1/customers/{customer_id}/updateConfig
Update a customer configuration
updateCustomerConfig-v1 1 param body → 200400404
POST
/v1/getCustomerBillingProviderConfigurations
Fetch billing provider configurations for a customer
getCustomerBillingProviderConfigurations-v1 body → 200400
POST
/v1/getCustomerRevenueSystemConfigurations
Fetch revenue system configurations for a customer
getCustomerRevenueSystemConfigurations-v1 body → 200400
POST
/v1/setCustomerBillingProviderConfigurations
Set billing provider configurations for a customer
setCustomerBillingProviderConfigurations-v1 body → 200400500
POST
/v1/archiveCustomerBillingProviderConfigurations
Archive billing provider configurations for a customer
archiveCustomerBillingProviderConfigurations-v1 body → 200400500
POST
/v1/setCustomerRevenueSystemConfigurations
Set revenue system configurations for a customer
setCustomerRevenueSystemConfigurations-v1 body → 200400500
POST
/v1/archiveCustomerRevenueSystemConfigurations
Archive revenue system configurations for a customer
archiveCustomerRevenueSystemConfigurations-v1 body → 200400500
POST
/v1/dashboards/getEmbeddableUrl
Get an embeddable customer dashboard
embeddableDashboard-v1 body → 200400

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are CustomerDetail (10 properties), CustomerRevenueSystemConfiguration (8 properties), CustomerBillingProviderConfiguration (8 properties), CustomerBillingProviderConfigurationOutput (6 properties). Each schema is shown below with its type and property counts.

CustomerConfig
object
1 property 1 required
SetIngestAliasesPayload
object
1 property 1 required
CustomField
object
Custom fields to be added eg. { "key1": "value1", "key2": "value2" }
ContractsBillingProviderType
string
Customer
object
5 properties 4 required
BillingProviderDeliveryMethodType
string
TaxProviderType
string
BillableStatus
string
CustomerBillingProviderConfiguration
object
8 properties 8 required
CustomerBillingProviderArchivePayload
object
2 properties 2 required
SetCustomerNamePayload
object
1 property 1 required
CustomerRevenueSystemConfigurationCreateCustomerInput
object
4 properties 1 required
CustomerRevenueSystemArchivePayload
object
2 properties 2 required
CustomerDetail
object
10 properties 8 required
CustomerRevenueSystemConfigurationInput
object
4 properties 3 required
EmbeddableDashboardPayload
object
5 properties 2 required
Error
object
1 property 1 required
Id
object
1 property 1 required
CustomerBillingProviderConfigurationInput
object
6 properties 2 required
RevenueSystemProviderType
string
CustomerBillingProviderConfigurationOutput
object
6 properties
BillingProviderType
string
LegacyCreateCustomerPayload
object
6 properties 1 required
CustomerConfigPayload
object
2 properties
CustomerBillingProviderConfigurationCreateCustomerInput
object
5 properties 1 required
CustomerRevenueSystemConfiguration
object
8 properties 5 required
RevenueSystemDeliveryMethodType
string
How revenue recognition records should be delivered to the revenue system.
SetCustomerBillableStatusPayload
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metronome-customers-api-openapi.yml Raw ↑

Other APIs Metronome publishes across the network.

Metronome Alerts API
AE Profile APIs.io
Metronome Billable Metrics API
AE Profile APIs.io
Metronome Contracts API
AE Profile APIs.io
Metronome Credits and commits API
AE Profile APIs.io
Metronome Custom fields API
AE Profile APIs.io
Metronome Integrations API
AE Profile APIs.io
Metronome Invoices API
AE Profile APIs.io
Metronome Named schedules API
AE Profile APIs.io
Metronome Notifications API
AE Profile APIs.io
Metronome Packages API
AE Profile APIs.io
Metronome Payments API
AE Profile APIs.io
Metronome Products API
AE Profile APIs.io
#Customers
← Back to M APIs
API Details
ID
metronome:metronome-customers-api
Base URL
https://api.metronome.com
Docs
https://docs.metronome.com/
Provider
Metronome
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=metronome-customers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/metronome-customers-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 Metronome Customers 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.