API reference · Credential broker

CAIN decides on the call, then makes it with the stored credential

POST /fabric/broker/call

Last reviewed 2026-10-02

POST /fabric/broker/call

Request body

CallRequest (required)

Responses

Try it

The request goes from your browser straight to this site. Your key is not stored unless you tick the box, and then only in this tab's session storage.

Code

curl -sS -X POST 'https://cainstudio.online/fabric/broker/call' \
  -H "X-API-Key: $CAIN_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"credential": "credential", "method": "GET", "url": "url"}'

import json, os, urllib.request

req = urllib.request.Request('https://cainstudio.online/fabric/broker/call', method='POST',
    headers={"X-API-Key": os.environ["CAIN_API_KEY"], "Content-Type": "application/json"},
    data=json.dumps({
      "credential": "credential",
      "method": "GET",
      "url": "url"
    }).encode())
with urllib.request.urlopen(req, timeout=60) as r:
    print(r.status, json.load(r))

const res = await fetch("https://cainstudio.online/fabric/broker/call", {
  method: "POST",
  headers: {
    "X-API-Key": process.env.CAIN_API_KEY!,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "credential": "credential",
    "method": "GET",
    "url": "url"
  }),
});
console.log(res.status, await res.json());

Schemas used

CallRequest · HTTPValidationError · ValidationError

all 4 Credential broker calls · Brokered credentials (the secrets are never returned) →