RIPE Atlas Documentation

Authentication ​

The RIPE Atlas API supports two authentication methods:

  1. API Keys — the preferred method for programmatic access
  2. Session-Based Authentication — for browser-based JavaScript applications

Most API endpoints can also be used without any authentication. See Anonymous Access for details on what is available without credentials.

Why Authenticate? ​

While most read operations work without authentication, authenticated requests unlock additional capabilities:

  • Viewing non-public objects — access probe details (including IP addresses) and measurements marked as non-public
  • Creating measurements — schedule new network measurements on RIPE Atlas probes
  • Stopping measurements — halt your ongoing measurements
  • Managing probes — add or remove participation requests for probes you host

Permissions Model ​

Each action in the API requires a key with the appropriate permission. API keys are scoped so that each key only has the permissions explicitly granted to it.

Some permissions imply accumulated (lesser) permissions. For example, a key with create measurement permission can also view measurements. This means you do not need separate keys for creating and viewing your own measurements.

TIP

Geographic locations of probes are always obfuscated for all users, regardless of authentication status. See Anonymous Access for details.

Contents ​