Source: https://www.revvly.ai/docs/concepts/apiKey

Pricing engine

# API Key

A scoped credential pair for usage ingestion and read access.

## Overview

Programmatic access to Revvly uses API Keys: a Bearer token plus a signing secret. When you issue a key the plaintext is shown once — capture it then or rotate. Keys can be scoped to specific subscriptions or meters, carry READ or WRITE capabilities (plus narrower ones for Support tokens, Forms and knowledge sync), and have their own rate limits: 10 requests per second and 100 per minute by default, adjustable up to 500 per second. Rotating a key issues a successor with a 30-day grace period on the old one; revoking is immediate.

## How it connects

This concept highlighted in context. Click a peer to navigate.

Related

Meter

Subscription

API Key

Related

Invoice

- Authorises the Event Ingestion API
- Authorises the invoice payment webhook
- Authorises the MCP server (POST /mcp)
- Issued and rotated per tenant

## Key fields

What you’ll see when creating or editing a API Key.

- **Name**: Human-friendly label

- **Scope**: Subscriptions, meters, read/write

- **Rate limits**: Per-key throttling

- **Bearer token**: Plaintext shown once at issuance

- **Signing secret**: Plaintext shown once at issuance

- **Status**: Active / Rotated / Revoked

## Example

usage-ingest · prod

Scope

subscription:663b… · meter:api-calls

Rate limit

10 req / sec · 100 req / min (default)

Issued

2026-05-01