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

AI Applyd Relay Inbox API

The relay-inbox API from AI Applyd — 12 operation(s) for relay-inbox.

AI Applyd Relay Inbox API is one of 46 APIs that AI Applyd publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include relay-inbox. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and 4 JSON Schemas.

This API exposes 13 operations across 12 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 115c47ce.

Requests are made against a single base URL, https://api.aiapplyd.com/api/v1.

13 operations 12 paths 26 schemas 6 GET4 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
115c47ce
Base URL
https://api.aiapplyd.com/api/v1
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

AI Applyd Relay Inbox API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Session token from signing in to AI Applyd, sent as Authorization: Bearer .

Paths & Operations 13

Across 12 paths, the API surfaces 13 operations — 6 GET, 4 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

relay-inbox 13
GET
/relay-inbox
List Inbox Emails
getRelayInbox 10 params → 200401404500
GET
/relay-inbox/counts
Inbox Counts
getRelayInboxCounts → 200401404500
POST
/relay-inbox/bulk
Bulk Inbox Action
postRelayInboxBulk body → 200400401404500
GET
/relay-inbox/{id}
Get Inbox Email Detail
getRelayInboxById 1 param → 200401404500
GET
/relay-inbox/{id}/thread
Get Inbox Email Thread
getRelayInboxByIdThread 1 param → 200401404500
GET
/relay-inbox/{id}/attachments/{partId}
Download Inbox Attachment
getRelayInboxByIdAttachmentsByPartId 2 params → 200401404500
PATCH
/relay-inbox/{id}/category
Re-categorize Inbox Email
patchRelayInboxByIdCategory 1 param body → 200400401404500
PATCH
/relay-inbox/{id}/read
Mark Inbox Email Read/Unread
patchRelayInboxByIdRead 1 param body → 200400401404500
PATCH
/relay-inbox/{id}/archive
Archive/Unarchive Inbox Email
patchRelayInboxByIdArchive 1 param body → 200400401404500
PATCH
/relay-inbox/{id}/star
Star/Unstar Inbox Email
patchRelayInboxByIdStar 1 param body → 200400401404500
POST
/relay-inbox/{id}/reply
Reply to Inbox Email
postRelayInboxByIdReply 1 param body → 200400401404429500
GET
/relay-inbox/forwarding/stop
Mute Non-Essential Emails (confirm page)
getRelayInboxForwardingStop 1 param → 200302404500
POST
/relay-inbox/forwarding/stop
Mute Non-Essential Emails (confirm)
postRelayInboxForwardingStop 1 param → 302404500

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are RelayInboxDetail (30 properties), RelayInboxItem (21 properties), RelayInboxByCategory (17 properties), RelayInboxThreadMessage (9 properties). Each schema is shown below with its type and property counts.

RelayReadRequest
object
1 property 1 required
ResponseMetadata
object
5 properties
RelayBulkResult
object
1 property 1 required
RelayInboxCounts
object
3 properties 2 required
RelayArchiveRequest
object
1 property 1 required
RelayInboxThreadMessage
object
9 properties 9 required
RelayCategoryUpdateResult
object
3 properties 3 required
RelayInboxThreadResponse
object
Successful API response
3 properties 2 required
RelayInboxItem
object
21 properties 21 required
RelayReplyResult
RelayCategoryUpdateResponse
object
Successful API response
3 properties 2 required
RelayInboxListResponse
object
Successful API response
3 properties 2 required
RelayStarRequest
object
1 property 1 required
RelayInboxStateResult
object
4 properties 4 required
RelayInboxDetail
object
30 properties 30 required
RelayInboxStateResponse
object
Successful API response
3 properties 2 required
RelayInboxAttachment
object
4 properties 4 required
RelayInboxByCategory
object
Active-inbox counts per visible effective category (every key present, 0 when none).
17 properties 17 required
RelayReplyResponse
object
Successful API response
3 properties 2 required
RelayCategoryUpdateRequest
object
1 property 1 required
RelayBulkResponse
object
Successful API response
3 properties 2 required
RelayBulkRequest
object
2 properties 2 required
RelayReplyRequest
object
3 properties 1 required
RelayInboxDetailResponse
object
Successful API response
3 properties 2 required
ApiErrorResponse
object
3 properties 2 required
RelayInboxCountsResponse
object
Successful API response
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aiapplyd-relay-inbox-api-openapi.yml Raw ↑

Other APIs AI Applyd publishes across the network.

AI Applyd MCP Server
AI Applyd Account API
AI Applyd Achievements API
AI Applyd AI API
AI Applyd AI Persona API
AI Applyd Analytics API
AI Applyd Application Profile API
AI Applyd Applications API
AI Applyd Ats API
AI Applyd Auth API
AI Applyd Billing API
AI Applyd Blog API
Where this information came from

This is an independent, third-party profile of AI Applyd Relay Inbox 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.