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

Amigo Billing API

The Billing API from Amigo — 17 operation(s) for billing.

Amigo Billing API is one of 72 APIs that Amigo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 20 operations across 17 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 5 base URLs: https://api.amigo.ai, https://internal-api.amigo.ai, https://api-eu-central-1.amigo.ai, https://api-ap-southeast-2.amigo.ai, https://api-ca-central-1.amigo.ai.

20 operations 17 paths 18 schemas 1 DELETE11 GET6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.amigo.ai
Authentication
HTTP Bearer, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

Amigo Billing API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer-Authorization). An API key is passed in the header as X-ORG-ID (Bearer-Authorization-Organization). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • Bearer-Authorization — Amigo issued JWT token that identifies an user. It's issued either after logging in through the frontend, or manually through the [SignInWithAPIKey](sign-in-wi…
  • Bearer-Authorization-Organization — An optional organization identifier that indicates from which organization the token is issued. This is used in rare cases where the user to authenticate is ma…
  • Basic — The username should be set to {orgid}{userid}, and the password should be the Amigo issued JWT token that identifies the user.

Paths & Operations 20

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

Billing 20
GET
/v1/{workspace_id}/billing/dashboard
Get Billing Dashboard
get-billing-dashboard 1 param → 200
GET
/v1/{workspace_id}/billing/usage
Get Workspace Usage
get-billing-usage 1 param → 200
GET
/v1/{workspace_id}/billing/usage/trends
Get Workspace Usage Trends
get-billing-usage-trends 5 params → 200422
GET
/v1/{workspace_id}/billing/invoices
List Workspace Invoices
list-billing-invoices 6 params → 200422
GET
/v1/{workspace_id}/billing/invoices/{invoice_id}
Get Workspace Invoice
get-billing-invoice 2 params → 200422
GET
/v1/{workspace_id}/billing/invoices/{invoice_id}/pdf
Get Invoice Pdf
get-billing-invoice-pdf 2 params → 200422
GET
/v1/billing/customers
List Customers
list-billing-customers 4 params → 200422
POST
/v1/billing/customers
Create Customer
create-billing-customer body → 201422
GET
/v1/billing/customers/{customer_id}
Get Customer
get-billing-customer 1 param → 200422
PUT
/v1/billing/customers/{customer_id}
Update Customer
update-billing-customer 1 param body → 200422
POST
/v1/billing/customers/{customer_id}/workspaces
Attach Workspace
attach-billing-workspace 1 param body → 201422
DELETE
/v1/billing/customers/{customer_id}/workspaces/{workspace_id}
Detach Workspace
detach-billing-workspace 2 params → 204422
GET
/v1/billing/customers/{customer_id}/config
Get Config
get-billing-config 1 param → 200422
PUT
/v1/billing/customers/{customer_id}/config
Update Config
update-billing-config 1 param body → 200422
GET
/v1/billing/customers/{customer_id}/usage
Get Customer Usage
get-customer-usage 6 params → 200422
GET
/v1/billing/customers/{customer_id}/invoices
List Customer Invoices
list-customer-invoices 6 params → 200422
POST
/v1/billing/customers/{customer_id}/generate-invoice
Generate Invoice
generate-billing-invoice 1 param → 201422
POST
/v1/billing/customers/{customer_id}/invoices/{invoice_id}/send
Send Invoice
send-billing-invoice 2 params → 200422
POST
/v1/billing/customers/{customer_id}/invoices/{invoice_id}/paid
Mark Paid
mark-billing-invoice-paid 2 params → 200422
POST
/v1/billing/customers/{customer_id}/invoices/{invoice_id}/void
Void Invoice
void-billing-invoice 2 params → 200422

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are InvoiceItem (15 properties), MeterValueItem (10 properties), CustomerItem (10 properties), UpdateConfigRequest (8 properties). Each schema is shown below with its type and property counts.

PaginatedResponse_MeterValueItem_
object
4 properties 2 required
CreateCustomerRequest
object
6 properties 3 required
MeterValueItem
object
10 properties 9 required
MeterBreakdown
object
Breakdown of a meter value by sub-category.
1 property
UpdateConfigRequest
object
8 properties
CustomerAddress
object
Customer billing address.
6 properties
MeterSummary
object
5 properties 4 required
HTTPValidationError
object
1 property
UpdateCustomerRequest
object
6 properties
UsageTrendPoint
object
6 properties 5 required
BillingDashboardResponse
object
8 properties 8 required
ValidationError
object
5 properties 3 required
InvoiceLineItem
object
A single line item on an invoice. meteringsource defaults to "production" for backward compatibility with invoices generated before the meteringsource dimensio…
6 properties 4 required
PaginatedResponse_CustomerItem_
object
4 properties 2 required
AttachWorkspaceRequest
object
3 properties 1 required
InvoiceItem
object
15 properties 15 required
CustomerItem
object
10 properties 10 required
PaginatedResponse_InvoiceItem_
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-billing-api-openapi.yml Raw ↑

Other APIs Amigo publishes across the network.

Amigo Account API
Amigo Admin API
Amigo Agent Definitions API
Amigo Agent Runs API
Amigo Agents API
Amigo Analytics API
Amigo API Keys API
Amigo Audit API
Amigo Auth API
Amigo Calls API
Amigo Command Center API
Amigo Compliance API
Where this information came from

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