Developer API¶
The GloriaMundo Developer API lets you trigger workflows from your own applications via HTTP. Build internal tools, connect to third-party platforms, or automate workflows programmatically.
What You Can Do¶
- Execute workflows — Trigger any workflow with custom input data
- Poll for results — Check execution progress and retrieve outputs
- Manage API keys — Create, list, and revoke access keys
- Control spending — Set daily, weekly, or monthly spend limits
Base URL¶
All API endpoints are served from:
Quick Example¶
# 1. Execute a workflow
curl -X POST https://app.gloriamundo.com/api/v1/workflows/{workflow_id}/execute \
-H "Authorization: Bearer gm_live_..." \
-H "Content-Type: application/json" \
-d '{"input": {"customer_name": "Acme Corp"}}'
# Response: {"run_id": "abc-123", "status": "queued", "poll_url": "/api/v1/runs/abc-123/status"}
# 2. Poll for results
curl https://app.gloriamundo.com/api/v1/runs/abc-123/status \
-H "Authorization: Bearer gm_live_..."
# Response: {"run_id": "abc-123", "status": "completed", "result": {...}, "cost_cents": 15}
Endpoints¶
| Method | Endpoint | Purpose |
|---|---|---|
POST | /api/v1/workflows/{id}/execute | Execute a workflow |
GET | /api/v1/runs/{id}/status | Poll for results |
POST | /api/v1/keys | Create an API key |
GET | /api/v1/keys | List API keys |
DELETE | /api/v1/keys/{id} | Revoke an API key |
GET | /api/v1/spend-limit | Get spend limits |
PUT | /api/v1/spend-limit | Set spend limits |
GET | /api/v1/usage | View usage history |
Authentication¶
All API requests require an API key. Include it as a Bearer token or via the X-API-Key header.
Learn more about authentication
Rate Limiting¶
Rate limits are applied per-user, per-endpoint. The following table shows the default limits:
| Endpoint pattern | Limit |
|---|---|
/api/chat | 20 requests / 60 seconds |
/api/workflow/run/ (status polls) | 60 requests / 60 seconds |
/api/workflow/run (execution) | 10 requests / 60 seconds |
| All other endpoints | 100 requests / 60 seconds |
When a limit is exceeded the API returns 429 Too Many Requests with a retry_after field indicating the window length in seconds.