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

Omni Schedule recipients API

Manage schedule recipients

Omni Schedule recipients API is one of 38 APIs that Omni publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Schedule recipients. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://{instance}.omniapp.co/api, https://{instance}.playground.exploreomni.dev/api.

5 operations 5 paths 6 schemas 1 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://blobsrus.omniapp.co/api
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Omni Schedule recipients API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP bearer tokens (JWT) (orgApiKey). By default, every request must be authenticated.

  • bearerAuth — Can be either an [Organization API Key](/api/authenticationorganization-api-keys) or [Personal Access Token (PAT)](/api/authenticationtoken-types). Include in…
  • orgApiKey — Requires an [Organization API Key](/api/authenticationorganization-api-keys). Personal Access Tokens (PATs) are not supported for this endpoint. Include in the…

Paths & Operations 5

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

Schedule recipients 5

Manage schedule recipients

GET
/v1/schedules/{scheduleId}/recipients
List schedule recipients
listScheduleRecipients 1 param → 200400404405429
PUT
/v1/schedules/{scheduleId}/add-recipients
Add schedule recipients
addScheduleRecipients 1 param body → 200400404405429
PUT
/v1/schedules/{scheduleId}/remove-recipients
Remove schedule recipients
removeScheduleRecipients 1 param body → 200400404405429
POST
/v1/users/email-only
Manage email-only user
manageEmailOnlyUser body → 200400405429
POST
/v1/users/email-only/bulk
Bulk manage email-only users
bulkManageEmailOnlyUsers body → 200400405429

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ScheduleRecipientsS3 (7 properties), ScheduleRecipientsSftp (4 properties), ScheduleRecipientsSlack (2 properties), ScheduleRecipientsEmail (2 properties). Each schema is shown below with its type and property counts.

ScheduleRecipientsWebhook
object
Response for schedules with webhook destinations.
2 properties
ScheduleRecipientsSftp
object
Response for schedules with SFTP destinations.
4 properties
Error
object
2 properties
ScheduleRecipientsEmail
object
Response for schedules with email destinations.
2 properties
ScheduleRecipientsSlack
object
Response for schedules with Slack destinations.
2 properties
ScheduleRecipientsS3
object
Response for schedules with Amazon S3 destinations.
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

omni-schedule-recipients-api-openapi.yml Raw ↑

Other APIs Omni publishes across the network.

Omni AI API
Omni AI Credit Controls API
Omni AI Eval API
Omni AI Model Suggestions API
Omni AI Routines API
Omni API Tokens API
Omni Connection environments API
Omni Connections API
Omni Content API
Omni Content migration API
Omni Content validator API
Omni Dashboard downloads API
Where this information came from

This is an independent, third-party profile of Omni Schedule recipients 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.