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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Stack Moxie

Stack Moxie How To: Automate API

Use these calls to Schedule Scenario runs.

Documentation Provider Profile APIs.io OpenAPI GitHub

Stack Moxie How To: Automate API is one of 5 APIs that Stack Moxie publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include How To: Automate. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and rate-limit docs.

This API exposes 5 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://app.stackmoxie.com/api/.

5 operations 2 paths 10 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://app.stackmoxie.com/api/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Stack Moxie How To: Automate API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtBearerAuth). By default, every request must be authenticated.

Paths & Operations 5

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

How To: Automate 5

Use these calls to Schedule Scenario runs.

GET
/v1/organizations/{org}/schedules
List Schedules
1 param → 200401403
POST
/v1/organizations/{org}/schedules
Create a Schedule
1 param body → 200401403
GET
/v1/organizations/{org}/schedules/{id}
Get a Schedule
2 params → 200401403
PATCH
/v1/organizations/{org}/schedules/{id}
Update a Schedule
2 params body → 200401403
DELETE
/v1/organizations/{org}/schedules/{id}
Delete a Schedule
2 params → 204401403

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Scenario (18 properties), User (16 properties), Schedule (9 properties), Folder (8 properties). Each schema is shown below with its type and property counts.

LinkedScenarios
object
Scenarios that should run based on the outcome of this scenario.
2 properties
Steps
array
Folder
object
8 properties 1 required
Scenario
object
18 properties 2 required
ScenarioDefinition
object
4 properties 1 required
Error
object
2 properties
Schedule
object
Represents a Schedule on which an associated Scenario will be run.
9 properties 3 required
User
object
16 properties 3 required
LinkedScenarioOutcome
object
The scenario that should run based on the outcome of this scenario.
2 properties
NotificationGroup
object
Represents a notification group that can be notified during a scenario run.
8 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stack-moxie-how-to-automate-api-openapi.yml Raw ↑

Other APIs Stack Moxie publishes across the network.

Stack Moxie How To: Administer API
AE Profile APIs.io
Stack Moxie How To: Integrate API
AE Profile APIs.io
Stack Moxie How To: Organize API
AE Profile APIs.io
Stack Moxie How To: Test API
AE Profile APIs.io
#How To: Automate
← Back to S APIs
API Details
ID
stack-moxie:stack-moxie-how-to-automate-api
Base URL
https://app.stackmoxie.com/api/
Docs
https://api.stackmoxie.com/
Provider
Stack Moxie
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=stack-moxie-how-to-automate-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/stack-moxie-how-to-automate-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Stack Moxie How To: Automate 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.