Getting Started

Authentication

How Routera API keys work, how to send them, and what happens when they fail.

Public base URL

Routera publishes the API at https://routera.one/api/v1.

API keys live in your account

Create, copy, and revoke keys from the account area.

Manage API keys

Routera authenticates public API requests with bearer tokens.

Bearer authentication

Send your key in the Authorization header:

Authorization: Bearer rta_your_api_key

Requests without a valid API key return:

{
  "error": {
    "message": "Missing or invalid API key. Send Authorization: Bearer <api key>.",
    "type": "authentication_error",
    "code": "invalid_api_key"
  }
}

Managing keys

Current key behavior in Routera:

  • Keys are created by signed-in users from the account page.
  • Keys are stored hashed on the backend.
  • The raw key is only returned once at creation time.
  • Revoked keys stop working immediately.
  • Routera records lastUsedAt whenever a valid key is used.

Failed authentication

When authentication fails, Routera returns HTTP 401 with the invalid_api_key code.

Common causes:

  • The Authorization header is missing.
  • The token is malformed.
  • The key was revoked.
  • The key value was copied incorrectly.