Skip to main content

Connect an API that has no card

Some services have no card in the gallery. When a task still needs to call one, store its key as a Generic API key. You tell Jaah where the API lives and how it reads the key, and agents send the key the same way on every call.

Use a service's own card when it has one: the card already knows the address and how the key is sent. If your whole team uses the same unlisted API, an Org Owner or Admin can define it once as a custom connector instead; see Add a custom API or MCP server.

Who can do this: everyone. The key you add is yours unless an Org Owner or Admin picks another Owner.

Before you start, have the key and the service's own documentation open. It says which header carries the key, such as Authorization or X-API-Key, and whether a word such as Bearer goes before it.

Add the keyโ€‹

The Custom category of the gallery: Custom connector and Custom MCP server with Add custom, Generic API key and Generic login with Connect

  1. In the sidebar, select Directory, then the Secrets tab.
  2. Select Add secret. In Category, pick Custom, or type generic in Search integrations.
  3. Select Connect on the Generic API key card. The form opens with its Name, URL and API key.
  4. Change the Name from generic_api_key to one that says what the key is for, such as billing-api. Tasks find the secret by this name, so keep it short.
  5. In URL (optional), enter the service's root address, for example https://api.example.com/v1. Leave it blank only for a key that names no host, such as one a Jaah feature reads directly.
  6. Paste the key into API key, on its own. Leave out any word such as Bearer: that goes in the next step.
  7. Open Advanced and set how the key is sent:
    • Header name: the header the API reads the key from, spelled as its documentation spells it. Leave it blank to send the key in Authorization.
    • Value prefix: the word sent before the key, such as Bearer or Token. Leave it blank to send the key alone.
  8. Optional: add a Description under Advanced, such as which account or environment the key belongs to. It helps people and tasks pick the right secret.
  9. Select Save. The secret appears in the list.

The Generic API key form with Advanced open: Name, URL (optional), API key, Owner, Owned by, Description, Header name, Value prefix, Cancel and Save

Two common pairs:

The service's documentation saysHeader nameValue prefix
Authorization: Bearer <key>blankBearer
X-API-Key: <key>X-API-Keyblank

If Save refuses itโ€‹

  • The header name is refused. Spell it as the documentation does, with no spaces and no colon. Headers Jaah sets itself, such as Host and Content-Length, can't be used.
  • The value prefix is refused. A prefix is one word, such as Bearer.

Jaah doesn't know the service's endpoints. Agents work from the service's own documentation, so link it in the task that uses the key.

Next stepsโ€‹