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

Mage Pipeline Schedules API

Manage triggers (schedule, event, and API triggers).

Mage Pipeline Schedules API is one of 4 APIs that Mage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: http://localhost:6789/api, https://{host}/api.

3 operations 3 paths 5 schemas 1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
http://localhost:6789/api
Authentication
API Key, API Key
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

Mage Pipeline Schedules API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (ApiKeyAuth). An API key is passed in the header as OAUTH-TOKEN (OAuthToken). By default, every request must be authenticated.

  • ApiKeyAuth — API key passed as the apikey query parameter or in the request body.
  • OAuthToken — Decoded OAuth token passed in the OAUTH-TOKEN header, or the raw token passed via the oauthtoken cookie.

Paths & Operations 3

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

Pipeline Schedules 3

Manage triggers (schedule, event, and API triggers).

GET
/pipeline_schedules
List pipeline schedules
listPipelineSchedules 1 param → 200
POST
/pipelines/{uuid}/pipeline_schedules
Create a pipeline schedule (trigger) for a pipeline
createPipelineSchedule 1 param body → 200
PUT
/pipeline_schedules/{id}
Update a pipeline schedule
updatePipelineSchedule 1 param body → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PipelineSchedule (7 properties), UpdatePipelineScheduleRequest (1 property), PipelineSchedulesResponse (1 property), PipelineScheduleResponse (1 property). Each schema is shown below with its type and property counts.

CreatePipelineScheduleRequest
object
1 property 1 required
PipelineScheduleResponse
object
1 property
PipelineSchedulesResponse
object
1 property
PipelineSchedule
object
7 properties
UpdatePipelineScheduleRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mage-ai-pipeline-schedules-api-openapi.yml Raw ↑

Other APIs Mage publishes across the network.

Mage Blocks API
Mage Pipeline Runs API
Mage Pipelines API
Where this information came from

This is an independent, third-party profile of Mage Pipeline Schedules 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.