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 Messages API

Operations for finding, retrieving, creating, forwarding, replying to, and deleting the email and SMS messages received by your Mailosaur inboxes.

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

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

This API exposes 9 operations across 6 paths, and defines 17 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.

9 operations 6 paths 17 schemas 2 DELETE2 GET5 POST

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 Messages 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 9

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

Messages 9

Operations for finding, retrieving, creating, forwarding, replying to, and deleting the email and SMS messages received by your Mailosaur inboxes.

GET
/api/messages
List messages
listMessages 5 params → 200
POST
/api/messages
Create a message
createMessage 1 param body → 200
DELETE
/api/messages
Delete all messages
deleteAllMessages 1 param → 204
POST
/api/messages/search
Search messages
searchMessages 6 params body → 200
GET
/api/messages/{messageId}
Get a message
getMessage 1 param → 200
DELETE
/api/messages/{messageId}
Delete a message
deleteMessage 1 param → 204
POST
/api/messages/{messageId}/forward
Forward a message
forwardMessage 1 param body → 200
POST
/api/messages/{messageId}/reply
Reply to a message
replyToMessage 1 param body → 200
POST
/api/messages/{messageId}/screenshots
Generate email previews
generateMessagePreviews 1 param body → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Message (13 properties), MessageSummary (10 properties), MessageCreateOptions (8 properties), Attachment (7 properties). Each schema is shown below with its type and property counts.

PreviewRequestOptions
object
Options to use when requesting email previews.
1 property
MessageHeader
object
An email header.
2 properties
MessageSummary
object
A summary of a message (used in list results).
10 properties
MessageListResult
object
The result of a request to list or search messages.
1 property
Image
object
An image found in a message body.
2 properties
MessageCreateOptions
object
Options to use when creating a new message.
8 properties
Attachment
object
A file attachment on a message.
7 properties
SearchCriteria
object
The criteria with which to find messages during a search.
5 properties
MessageForwardOptions
object
Options to use when forwarding a message.
4 properties 1 required
MessageContent
object
The HTML or plain text content of a message.
4 properties
MessageReplyOptions
object
Options to use when replying to a message.
4 properties
PreviewListResult
object
The result of a request to generate email previews.
1 property
Metadata
object
Further metadata related to the message, including email headers.
4 properties
Preview
object
A rendered email preview screenshot.
3 properties
MessageAddress
object
An email address or SMS phone number.
3 properties
Link
object
A hyperlink found in a message body.
2 properties
Message
object
An email or SMS message processed by Mailosaur.
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mailosaur-messages-api-openapi.yml Raw ↑

Other APIs Mailosaur publishes across the network.

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

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