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

Lago Customers API

Everything about Customer collection

Lago Customers API is one of 17 APIs that Lago 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 9 operations across 7 paths, and defines 26 schemas. It is described by OpenAPI 3.1.0, at version 1.15.0.

Requests are made against 2 base URLs: https://api.getlago.com/api/v1, https://api.eu.getlago.com/api/v1.

9 operations 7 paths 26 schemas 2 DELETE5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.15.0
Servers
https://api.getlago.com/api/v1
https://api.eu.getlago.com/api/v1
Authentication
HTTP Bearer
License
AGPLv3
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 9

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

Customers 9

Everything about Customer collection

POST
/customers
Lago Create a customer
createCustomer body → 200400401422
GET
/customers
Lago List all customers
findAllCustomers 2 params → 200401
GET
/customers/{external_id}
Lago Retrieve a customer
findCustomer 1 param → 200401404
DELETE
/customers/{external_id}
Lago Delete a customer
destroyCustomer 1 param → 200401404
DELETE
/customers/{external_customer_id}/applied_coupons/{applied_coupon_id}
Lago Delete an applied coupon
deleteAppliedCoupon 2 params → 200401404
GET
/customers/{external_customer_id}/portal_url
Lago Get a customer portal URL
getCustomerPortalUrl 1 param → 200401404
GET
/customers/{external_customer_id}/current_usage
Lago Retrieve customer current usage
findCustomerCurrentUsage 2 params → 200401404
GET
/customers/{external_customer_id}/past_usage
Lago Retrieve customer past usage
findAllCustomerPastUsage 6 params → 200401404422
POST
/customers/{external_customer_id}/checkout_url
Lago Generate a Customer Payment Provider Checkout URL
generateCustomerCheckoutURL 1 param → 200401404422

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are AppliedCouponObject (17 properties), TaxObject (11 properties), CustomerUsageObject (9 properties), CustomerChargeUsageObject (8 properties). Each schema is shown below with its type and property counts.

CustomerObjectExtended
PaginationMeta
object
5 properties 3 required
CustomerChargeUsageObject
object
8 properties 7 required
AppliedCouponObject
object
17 properties 9 required
Address
object
Configuration specific to the payment provider, utilized for billing the customer. This object contains settings and parameters necessary for processing paymen…
6 properties
Customer
object
1 property 1 required
IntegrationCustomer
object
Configuration specific to the accounting and tax integrations. This object contains settings and parameters necessary for syncing documents and payments.
6 properties
CustomerMetadata
object
Set of key-value pairs that you can attach to a customer. This can be useful for storing additional information about the customer in a structured format
5 properties 5 required
Timezone
string
Country
string
ApiErrorNotFound
object
3 properties 3 required
CustomerUsageObject
object
9 properties 7 required
CustomerCreateInput
object
1 property 1 required
ApiErrorUnprocessableEntity
object
4 properties 4 required
CustomerPastUsage
object
2 properties 2 required
CustomerBillingConfiguration
object
Configuration specific to the payment provider, utilized for billing the customer. This object contains settings and parameters necessary for processing paymen…
8 properties
ApiErrorUnauthorized
object
2 properties 2 required
ApiErrorBadRequest
object
2 properties 2 required
Currency
string
CustomerUsage
object
1 property 1 required
CustomerChargeGroupedUsageObject
array
Array of aggregated fees, grouped by the event properties defined in a standard charge model.
5 required
CustomerObject
AppliedCoupon
object
1 property 1 required
CustomerChargeFiltersUsageObject
array
Array of filter object, representing multiple dimensions for a charge item.
4 required
CustomersPaginated
object
2 properties 2 required
TaxObject
object
11 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lago-customers-api-openapi.yml Raw ↑

Other APIs Lago publishes across the network.

Lago Add_ons API
Lago Analytics API
Lago Billable_metrics API
Lago Coupons API
Lago Credit_notes API
Lago Events API
Lago Fees API
Lago Invoices API
Lago Organizations API
Lago Payment_requests API
Lago Plans API
Lago Subscriptions API
Where this information came from

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