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

Mailosaur Usage API

Operations for inspecting your account's usage limits and recent transactional usage. These endpoints require authentication with an account-level API key.

Mailosaur Usage API is one of 7 APIs that Mailosaur publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

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

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://mailosaur.com/api
Authentication
HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Mailosaur Usage API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Auth using your Mailosaur API key as the username and an empty password, or your API key as both username and password.

Paths & Operations 2

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

Usage 2

Operations for inspecting your account's usage limits and recent transactional usage. These endpoints require authentication with an account-level API key.

GET
/api/usage/limits
Get usage limits
getUsageLimits → 200
GET
/api/usage/transactions
Get usage transactions
getUsageTransactions → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are UsageAccountLimits (4 properties), UsageTransaction (3 properties), UsageAccountLimit (2 properties), UsageTransactionListResult (1 property). Each schema is shown below with its type and property counts.

UsageTransaction
object
A usage transaction record.
3 properties
UsageAccountLimits
object
The account usage limits.
4 properties
UsageAccountLimit
object
A single account limit.
2 properties
UsageTransactionListResult
object
A list of usage transaction records.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mailosaur-usage-api-openapi.yml Raw ↑

Other APIs Mailosaur publishes across the network.

Mailosaur Analysis API
Mailosaur Devices API
Mailosaur Files API
Mailosaur Messages API
Mailosaur Previews API
Mailosaur Servers API
Where this information came from

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