API v1

Changed API keys Breaking

A key only gives the scopes it holds

Creating a key through the API refuses any scope the key making the request does not hold itself. Asking for sensitive fields from a key without them answers 422 on sensitive_fields.

Why this is a breaking change

An integration that asks for sensitive fields with a key that lacks them gets 422. Create that key from the security settings instead.

Why it changed

Any key could mint a second key reaching the sensitive fields its own owner had kept it away from.

Changes

Field Change Endpoints
sensitive_fields Changed
POST /api-keys

In the same release