Skip to content

API Keys

How to create and manage API keys for programmatic access to Sproobo

API keys let you authenticate against the Sproobo API for automated workflows and integrations.

What are API Keys?

API keys are authentication tokens you can use to interact with your Sproobo account programmatically — for example, to trigger deployments from a CI/CD pipeline.

Use Cases

  • Trigger deployments from CI/CD pipelines
  • Automate resource management via the Sproobo API
  • Integrate Sproobo with external tooling

  • Use the Sproobo MCP server from Cursor, Claude Desktop, or other MCP clients

Creating an API Key

  1. 1

    Navigate to API Keys

    Go to Settings → API Keys and click "Create API key".
    Sproobo API keys page
    Create and manage API keys from Settings.
  2. 2

    Give It a Name

    Enter a descriptive name so you can identify the key later (e.g. "GitHub Actions CI").
  3. 3

    Copy the Key Immediately

    Click "Create". Copy the full API key value now — it is only shown once. Sproobo stores only a hash of the key and the first 12 characters as an identifier.
    ✕

    Important: Store the API key in a secure location (e.g. your password manager or CI secrets). You cannot view it again after closing this dialog.

Using API Keys

Authenticate API requests by including the key in the Authorization header:

bash
curl -H "Authorization: Bearer YOUR_API_KEY" 

https://dashboard.sproobo.com/api/...

The same key works for the HTTP API and for the MCP server; set SPROOBO_API_KEY when configuring the MCP host. See Model Context Protocol (MCP).

Managing API Keys

  1. 1

    View Keys

    Go to Settings → API Keys to see all your keys with their name, key prefix, and creation date.
  2. 2

    Revoke a Key

    Click "Revoke" next to a key to immediately invalidate it. Any requests using that key will be rejected.
    ⚠️

    Revoking a key immediately stops all integrations using it. Update your systems to use a new key before revoking the old one.

  3. 3

    Rotate Keys

    To rotate a key: create a new key, update your integrations to use the new key, then revoke the old one.

Security Best Practices

Best Practices

  • Never commit API keys to version control
  • Store keys in CI/CD secret stores (e.g. GitHub Actions secrets)
  • Rotate keys regularly and revoke any that may have been exposed
  • Use separate keys for different integrations so you can revoke them independently