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

Stack Moxie How To: Test API

Use these calls to define test Scenarios, Run them, and retrieve their results.

Stack Moxie How To: Test 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: Test. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and rate-limit docs.

This API exposes 15 operations across 11 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0.

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

15 operations 11 paths 12 schemas 1 DELETE10 GET1 PATCH3 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: Test API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtBearerAuth). By default, every request must be authenticated.

Paths & Operations 15

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

How To: Test 15

Use these calls to define test Scenarios, Run them, and retrieve their results.

GET
/v1/organizations/{org}/scenarios
List Scenarios
1 param → 200401403
POST
/v1/organizations/{org}/scenarios
Create a Scenario
1 param body → 200401403422
GET
/v1/organizations/{org}/scenarios/{id}
Get a Scenario
2 params → 200401403
PATCH
/v1/organizations/{org}/scenarios/{id}
Update a Scenario
2 params body → 200401403422
DELETE
/v1/organizations/{org}/scenarios/{id}
Delete a Scenario
2 params → 204401403
POST
/v1/organizations/{org}/asyncScenario
Create an Async Scenario
1 param body → 200400401403
GET
/v1/organizations/{org}/job/{jobId}
Get Async Job Status
2 params → 200401403
GET
/v1/organizations/{org}/scenarios/allTemplates
List Templates
1 param → 200401403
GET
/v1/organizations/{org}/scenarios/linkableTemplates
List Linkable Templates
1 param → 200401403
GET
/v1/organizations/{org}/scenarios/exposedTemplates
List Exposed Templates
1 param → 200401403
GET
/v1/organizations/{org}/scenarios/{id}/runs
List Scenario Runs
6 params → 200401403
POST
/v1/organizations/{org}/scenarios/{id}/runs
Create a Scenario Run
2 params body → 200400401403
GET
/v1/organizations/{org}/scenarios/{scenarioId}/runs/{id}
Get a Scenario Run
3 params → 200401403
GET
/v1/organizations/{org}/scenarios/{scenarioId}/mostRecentRun
Get a Scenario's Most Recent Run
2 params → 200401403
GET
/v1/organizations/{org}/scenarios/{scenarioId}/runs/{runId}/log/{id}
Get a Scenario Run Log
4 params → 200401403

Schemas 12

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

Run
object
Represents a single run of a Test Scenario.
9 properties
Scenario
object
18 properties 2 required
LinkedScenarioOutcome
object
The scenario that should run based on the outcome of this scenario.
2 properties
Job
object
The status of the job that is running asynchronously.
7 properties
NotificationGroup
object
Represents a notification group that can be notified during a scenario run.
8 properties 1 required
LinkedScenarios
object
Scenarios that should run based on the outcome of this scenario.
2 properties
RunLog
object
Represents a detailed log associated with a specific test Scenario Run.
5 properties
Steps
array
Error
object
2 properties
User
object
16 properties 3 required
ScenarioDefinition
object
4 properties 1 required
Folder
object
8 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Stack Moxie publishes across the network.

Stack Moxie How To: Administer API
Stack Moxie How To: Automate API
Stack Moxie How To: Integrate API
Stack Moxie How To: Organize API
Where this information came from

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