Skip to main content
All endpoints use bearer authentication. Create and manage keys in Your Rubie dashboard.

​
Header Format

If the header is missing or invalid, the API returns 401.

​
Example Request

​
Base URL

Production base URL: https://app.rubiehq.com/api/v1

​
What a Key Grants

Keys are scoped to a single Rubie account. Every resource you reference — a credential, a session, a Blueprint, a run — must belong to that same account, or the request returns 404 (for resources you can’t see) or 403 (for resources you can see but aren’t authorized for). Blueprints add a second layer: a Blueprint can have specific API keys linked to it, in which case only those keys may trigger it or read its runs. If no keys are linked, any valid key on the owning account works. Ask your Rubie contact which applies to your Blueprint.

​
Best Practices

  • Never embed API keys in frontend bundles — every endpoint here is server-to-server
  • Store keys in your secret manager
  • Redact Authorization headers from logs