Skip to content

Rootly

This guide configures a Rootly Global API key so Trustle can securely discover your on-call configuration (users, teams, schedules, escalation policies, services, and roles) and grant or revoke just-in-time on-call access.

  • A Rootly organization admin who can manage API keys.
  • Access to the Trustle Connections page.

Log in to your Rootly organization at https://rootly.com as a user who can manage organization settings.

  1. Open Organization Settings.
  2. Select API Keys.
  1. Click to create a new API key.
  2. Enter a description (for example, “Trustle Integration”).
  3. Choose the Global scope, not Team or Personal.
  4. Assign roles to the key. Prefer custom, minimally scoped roles:
    • Custom On-Call role: read on all on-call resources; create, update, and delete on schedules, schedule overrides, escalation policies, and groups (teams); update on on-call roles and users.
    • Custom Incident Response role: read plus update on groups, services, roles, and users.
  5. Owner or Admin roles also work, but they grant more than Trustle needs.
  6. Note the key’s expiration date. Rootly keys expire explicitly.

The key looks like rootly_0123456789abcdef….

  1. Go to Trustle’s Connections page.
  2. Under SaaS Applications, find Rootly and click Connect.
  3. Fill in the connection form:
    1. Connection Name: enter a descriptive name for this connection.
    2. API Token: paste the Rootly Global API key you copied.
  4. Click Test Connection to verify the credentials work.
  5. Click Save Connection.
  • Use a Global key with custom minimal roles when possible. Do not use a Personal API key.
  • Rotate the key before it expires.
  • Store the token only in Trustle. Do not share it in chat or commit it to version control.