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: Administer API

Use these calls to provision Organizations (e.g. for your own clients/customers), and automatically grant them (or your own team members) access.

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

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

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

10 operations 7 paths 5 schemas 1 DELETE2 GET3 PATCH4 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: Administer API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtBearerAuth). By default, every request must be authenticated.

Paths & Operations 10

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

How To: Administer 10

Use these calls to provision Organizations (e.g. for your own clients/customers), and automatically grant them (or your own team members) access.

POST
/v1/organizations
Create an Organization
body → 200401403
PATCH
/v1/organizations/{org}
Update an Organization
1 param body → 200401403
GET
/v1/organizations/{org}/members
List Team Members
1 param → 200401403
POST
/v1/organizations/{org}/members
Invite a Team Member
1 param body → 200401403
GET
/v1/organizations/{org}/members/{id}
Get a Team Member
2 params → 200401403
PATCH
/v1/organizations/{org}/members/{id}
Update a team Member
2 params body → 200401403
DELETE
/v1/organizations/{org}/members/{id}
Remove a Team Member
2 params → 204401403
POST
/v1/organizations/{org}/members/{id}/reinvite
Re-Send Invitation
2 params → 200400401403
POST
/v1/organizations/{org}/notification-groups
Create a Notification Group
1 param body → 200401403
PATCH
/v1/organizations/{org}/notification-groups/{id}
Update a Notification Group
2 params body → 200401403

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are User (16 properties), Organization (10 properties), NotificationGroup (8 properties), OrganizationMember (8 properties). Each schema is shown below with its type and property counts.

OrganizationMember
object
A representation of the relationship between a User and an Organization, including the User's role in the organization.
8 properties 1 required
Error
object
2 properties
User
object
16 properties 3 required
Organization
object
Represents a company, client, or environment under which Credentials, Scenarios, Runs, and Folders are scoped.
10 properties 1 required
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-administer-api-openapi.yml Raw ↑

Other APIs Stack Moxie publishes across the network.

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

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