POST
Bulk import license keys into a pool

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Path Parameters

configId
string
required
poolId
string
required

Body

application/json

WRITE-ONLY INGESTION. The keys you send are encrypted at rest and no read on this API ever hands one back, so importing teaches a key nothing it did not arrive with. The response is two counts and nothing else: it does not echo the keys, name the duplicates, or return row ids. Re-sending a batch is safe: duplicates dedupe, so a replay reports imported 0 and skipped n rather than failing.

keys
string[]
required

Up to 10000 plaintexts per request, each at most 512 characters. Duplicates inside the batch and keys already in the pool are counted as skipped rather than refused.

Response

Success

data
object