Scoped APIs, synthetic sandboxes, and what a key cannot do.

A key is a secret shown once and stored as a hash. It can carry scopes such as reading studies. It cannot carry platform administration or audit access. The catalog omits those paths. A sandbox organization rejects participant codes that do not start with SYN-. Example payloads on a real study should be synthetic.

What this covers

Token

Shown once. Only the hash is kept.

Scopes

Forbidden names are rejected at creation.

Catalog

The routes a tenant key may discover. Not the audit log.

Sandbox

SYN- participant codes only.

Webhooks

Public HTTPS only. Signing exists. Delivery is not a finished demonstration.

Versions

The current API is /api/v1. A second version is not claimed.

How a team uses it

Create

An administrator makes the key.

Call

Use only the scopes granted.

Fail closed

A private webhook URL is refused.

Rotate

Rotation retires the old key.

Related reading

Questions

Can a key read the audit trail?

No.

What does a sample participant look like?

A sandbox code starts with SYN-. Do not send real participant data to a test.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.