Static API key authentication using Bearer token scheme.
Include your API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY
API keys can be generated in your superglue dashboard.
Optional pre-generated run ID. If not provided, server generates one. Useful for idempotency and tracking runs before they start.
"7f3e9c1a-2b4d-4e8f-9a3b-1c5d7e9f2a4b"
Tool-specific input parameters
{
"query": "latest AI news",
"maxResults": 5
}Runtime credentials for systems (overrides stored system credentials if provided). WARNING: These credentials are not persisted. Use systems for stored credentials.
{
"apiKey": "sk_live_abc123def456",
"apiSecret": "secret_xyz789"
}Tool execution completed (sync)
Unique identifier for this run (maps to 'id' in GraphQL schema)
"7f3e9c1a-2b4d-4e8f-9a3b-1c5d7e9f2a4b"
ID of the tool that was executed
"550e8400-e29b-41d4-a716-446655440000"
Execution status:
running, success, failed, aborted "success"
Tool metadata (not full configuration, maps to 'toolConfig' in GraphQL)
The inputs and options provided when running the tool (maps to 'toolPayload' in GraphQL)
Tool execution results (only present when status is success, maps to 'toolResult' in GraphQL)
Error message (only present when status is failed or aborted)
"Connection timeout after 30 seconds"
Results from each execution step (only for multi-step tools)
Execution options that were used for this run
Source identifier for where the run was initiated
"api"
Trace ID for this run (for debugging and log correlation)
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"