Skip to main content
POST
cURL
When Gumloop accepts the request, MCP execution failures such as target server authentication, policy blocks, invalid tools, upstream HTTP errors, and connection failures are returned in results[*].status and results[*].error. A credit check runs before the tool calls; insufficient credits return HTTP 402 credit_limit_exceeded. Top-level 4xx responses are reserved for Gumloop request, authentication, permission, and credit failures. 200 covers homogeneous execution outcomes (all calls succeeded or all calls failed); mixed success/failure batches return 207. If you previously treated non-2xx HTTP statuses as MCP execution failures, update your integration to inspect each result’s status and error.

Authorizations

Authorization
string
header
required

A personal API key or an OAuth 2.0 access token. Personal API keys also require the x-auth-key header with your user ID.

Body

application/json
calls
object[]
required

Tool calls to execute. Dispatched concurrently; the batch is capped at 5.

Required array length: 1 - 5 elements
team_id
string | null

Team the calls are scoped to.

Example:

"team_4f8c92ab"

Response

Batch processed. Inspect each result's status and error; this can include all-success and all-failed execution outcomes.

results
object[]