orkestra-api-test

Generate JWTs and test protected Orkestra API endpoints with curl and jq.

1|1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-api-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orkestra-api-test
Source: https://github.com/orkestra-cc/orkestra/tree/main/.claude/skills/orkestra-api-test
Command: npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-api-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the complex process of authenticating against protected Orkestra backend endpoints, managing environment-specific host headers, and verifying role-based access control (RBAC) without manual token handling.

Core Features & Use Cases

  • Synthetic Token Minting: Quickly generate valid JWTs for any user role (e.g., administrator, guest) to test API surfaces.
  • Environment-Aware Requests: Automatically handles the Host header requirements for staging versus development environments to prevent 421 Misdirected Request errors.
  • RBAC Validation: Provides a structured way to verify that specific roles have the correct permissions by testing both authorized and unauthorized access scenarios.

Quick Start

Use the orkestra-api-test skill to mint an administrator token and perform a GET request to the users endpoint.

Frequently Asked Questions about orkestra-api-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a JWT for testing backend API endpoints with different user roles?▼

You can automate JWT generation for backend API endpoint testing by minting synthetic tokens for specific user roles like administrator or guest to test API surfaces.

Why do I get a 421 Misdirected Request error when testing staging or development environments?▼

A 421 Misdirected Request error occurs when environment-specific host headers are missing. Environment-aware request configuration automatically handles host header routing for staging versus development environments to prevent this error.

What is the best way to verify role-based access control (RBAC) permissions for protected API endpoints?▼

The best way to verify role-based access control (RBAC) permissions is by testing both authorized and unauthorized access scenarios using minted tokens, providing a structured method to validate that specific roles have correct permissions.

Do I need curl and jq to test protected backend API endpoints?▼

Yes, you need curl and jq installed to execute authenticated requests against protected backend API endpoints and parse JSON responses from the local API surface.

Can I test administrator versus guest access on local API surfaces without manual token handling?▼

Yes, you can test administrator versus guest access on local API surfaces without manual token handling by automating JWT generation and verifying role-based access control through environment-aware request configuration.