Skip to main content
Clausum uses three key types. The prefix on each key (clm_pub_, clm_sk_, clm_wh_) is only a technical identifier — in the Integraciones screen you create them under friendly names.

​
At a glance

Checkout (browser)

Prefix: clm_pub_
Use for: Risk check before payment (SDK or POST /api/v1/assess from the client).
Never for: Reporting fraud or merchant API.

Server (backend)

Prefix: clm_sk_
Use for: Your API: assess, report fraud, merchant endpoints.
Never in: Browser or mobile app bundles.

Event ingest

Prefix: clm_wh_
Use for: Sending events into Clausum (POST /api/webhooks/ingest).
Not for: Checkout SDK or assess in the store.

​
Create keys in the dashboard

1

Open Integraciones

Sign in at sandbox.clausum.ai and go to Integraciones → Claves de integración.
2

Choose the right section

  • Integración de pagos (Partner API) → Create checkout key or Create server key
  • Entrada de eventos → Create event ingest key (webhook pipe only)
3

Copy once

Clausum shows the full key one time. Store it in your secrets manager or .env immediately.
4

Pair with your API base URL

Keys only work against the hostname support assigned to your org. Set CLAUSUM_API_BASE — see Access & environments.
Checkout and event ingest keys are not interchangeable. If assess returns 401 with a clm_wh_ key, you created the wrong type.

​
Default permissions

Dashboard labelPrefixDefault permissions
Checkout (browser)clm_pub_assess
Server (backend)clm_sk_assess, fraud report, merchant read/write, etc.
Event ingestclm_wh_Valid webhook key (ingest only)

​
Troubleshooting

If the integrations page is empty or key creation fails after onboarding, contact api@clausum.ai with your organization name — workspace provisioning may still be in progress.

​
Next steps

Quickstart

First assess and fraud report.

Authentication

Headers, permissions, rate limits.