SIsignalshq
MCP CONNECTOR

Create an MCP API key for your organization.

Mint a key and return the plaintext.

sha256(secret) drives authentication; a Fernet copy under a tenant-derived key is stored alongside so the Owner can read the credential back later. Several live keys per organization is intentional: rotating means issuing a new key, moving the connector over, then revoking the old one.

post/internal/api/mcp/keys

Request

  • Base URL
    https://api.signalshq.io (the document declares no server; this is the origin it was published from)
  • Auth
    OAuth 2
    Password
    Token URL: /auth/login

Request body

labelstring required

How this key will be identified later, e.g. 'Perplexity — tax team'. The secret is never shown again, so the label is the only way to tell two keys apart when deciding what to revoke.

expires_atstring date-time nullable

Optional expiry. Omit for a key that lasts until revoked.

Example request

{
  "label": "Perplexity — tax team"
}

Response

Successful Response

api_keystring required

The full credential. Copy it now — the Owner can read it back later from the key list, but nobody else can, and every read-back is recorded.

Changes

No recorded changes to this operation across all 1 revision of this API.