Consumers
A consumer represents an end-customer of your API: a person, a tenant, a partner integration. Naming them lets EndpointOS attribute every request, log row, and usage event to the right entity.
Why consumers exist
Without consumers, you know how much traffic your API gets. With consumers, you know who. That distinction matters when one partner runs hot, when you want a per-customer monthly cap, or when you need to revoke access for a specific integrator without taking down the whole API.
Creating a consumer
Open the Consumers tab on a project, click New consumer, give them a name (e.g. "Acme Corp", "iOS app"), an external ID (optional, your own identifier), and a contact email. Then issue an API key attached to this consumer.
Per-consumer surfaces
- Consumer dashboard. Request volume, status distribution, top endpoints, per-consumer monthly usage.
- Per-consumer monthly cap. Set in the consumer's settings. When hit, the API returns
429until the next billing month. - Archive / unarchive. Soft-disable a consumer without losing their historical logs.