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

Outreach Mailbox API

## Mailbox Relationships## Mailbox Resource Metadata| **METADATA NAME**| **DESCRIPTION** | **QUERY PARAM** || --- | --- | --- || canWrite | A boolean value indicating whether the current API user has write access to this resource. | provideAuthorizationMeta || canDelete | A boolean value indicating whether the current API user has delete access to this resource. | provideAuthorizationMeta |## ⌵ Mailbox Actions

Outreach Mailbox API is one of 55 APIs that Outreach publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Mailbox. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and 1 JSON Schema.

This API exposes 9 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.outreach.io/api/v2.

9 operations 6 paths 3 schemas 1 DELETE2 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.outreach.io/api/v2
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Outreach Mailbox API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP bearer tokens (JWT) (s2sAuthToken). By default, every request must be authenticated.

Paths & Operations 9

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

Mailbox 9

Mailbox Relationships Mailbox Resource Metadata | METADATA NAME| DESCRIPTION | QUERY PARAM | | --- | --- | --- | | canWrite | A boolean value indicating whether the current API us…

GET
/mailboxes
Get a Collection of Mailboxes
→ 200422
POST
/mailboxes
Create a New Mailbox
body → 201422
DELETE
/mailboxes/{id}
Delete an Existing Mailbox by ID
1 param → 204422
GET
/mailboxes/{id}
Get a Mailbox by ID
1 param → 200404
PATCH
/mailboxes/{id}
Update a Mailbox
1 param body → 200422
POST
/mailboxes/{id}/actions/linkEwsMasterAccount
Link Ews Master Account
1 param → 200422
POST
/mailboxes/{id}/actions/testSend
Test Send
1 param → 200422
POST
/mailboxes/{id}/actions/testSync
Test Sync
1 param → 200422
POST
/mailboxes/{id}/actions/unlinkEwsMasterAccount
Unlink Ews Master Account
1 param → 200422

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are mailbox (50 properties), mailboxRelationships (5 properties), mailboxResponse (4 properties). Each schema is shown below with its type and property counts.

mailboxRelationships
object
5 properties
mailboxResponse
object
4 properties
mailbox
object
A representation of an email mailbox, used within the application for sending and syncing emails.
50 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

outreach-mailbox-api-openapi.yml Raw ↑

Other APIs Outreach publishes across the network.

Outreach MCP Server
Outreach Client Extensions API
Outreach Data Sharing
Outreach Webhooks
Outreach Account API
Outreach Account Note API
Outreach Audit Log API
Outreach Batch API
Outreach Batch Item API
Outreach Call API
Outreach Call Disposition API
Outreach Call Purpose API
Where this information came from

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