How to create a read-only Level API key

At a glance

Create a dedicated read-only key in Level, save it securely, and use it to validate the RMMBackup connection before starting a backup. The steps below cover creation, permissions, and common connection errors.

Create and validate a dedicated read-only Level API key without exposing it in logs, URLs, exports, or browser content.

Published Updated

On this page

Create the key in Level

  1. Sign in to Level as an administrator.
  2. Open Settings > API keys.
  3. Choose Create API key and enter a description identifying RMMBackup.
  4. Select Read-only access.
  5. Copy the key once and place it in an approved secret manager until it is saved in RMMBackup.

Use one dedicated key per integration so it can be rotated or revoked independently. Never paste the key into chat, source control, a URL, screenshots, or support logs.

Enter and validate the key

In Settings > Integrations, choose Level and paste the key into the secret field. Select at least one source, save, and run the connection validation. The validation performs only documented Level GET requests and checks that each public list domain returns the expected pagination envelope.

The fixed API origin is https://api.level.io, and current public paths use /v2. There is no tenant hostname or region field to configure. RMMBackup sends the raw key in the Authorization header; adding Bearer would fail authentication.

Troubleshoot safely

  • 401 Unauthorized: recopy the key, confirm it is active, and verify that no Bearer prefix was added.
  • 403 Forbidden: confirm organization scope and that the requested object is visible to the key.
  • 429 Too Many Requests: allow RMMBackup to honor Retry-After; Level does not publish a fixed numeric limit in the cited public guide.
  • A collection fails while others work: inspect the sanitized collection category and verify the selected source. The failed collection remains partial or failed and cannot create deletions.

Do not include raw API responses or the key in a support request. RMMBackup's logs store exception types and sanitized categories rather than response bodies or credentials.

Rotate or revoke the key

Create a replacement read-only key, validate it against the existing Level connection, then save the rotated credential. Revoke the old key in Level only after the replacement succeeds. Before switching to a different Level organization, download the history you need and review the connection-switching rules.

Frequently asked questions

Does the Level Authorization header use Bearer?

No. Level requires the raw API key value in the Authorization header without a Bearer prefix.

Does RMMBackup need a read and write key?

No. Choose read-only access. RMMBackup never uses Level write or action endpoints.

Official source

Public API: Getting Started

Official Level instructions for creating keys, selecting read-only access, authenticating, paginating, and handling responses.

Related Level integration

Review current Level backup coverage and availability.