One-shot challenge for API-key rotation
First step of `POST /maker/api-key/rotate`: request a one-shot challenge string, then sign it — as UTF-8 text, NOT a prepared-tx hash — with the maker's party key.
First step of POST /maker/api-key/rotate: request a one-shot
challenge string, then sign it — as UTF-8 text, NOT a prepared-tx hash
— with the maker's party key.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
curl -X POST "https://example.com/maker/challenge" \ -H "Content-Type: application/json" \ -d '{ "partyId": "string" }'{ "challenge": "string"}{ "error": "string", "code": "INSUFFICIENT_FUNDS"}Rotate the API key by proving party-key ownership POST
Recovery path for a lost API key: prove ownership of the party key by signing the `challenge` from `POST /maker/challenge` (as UTF-8 text), and get a fresh key back. The party key and party id are unchanged; the previous API key stops working immediately.
Re-drive the DevNet receive preapproval POST
Manual recovery for the auto-preapproval attempted at `register/complete`: on DevNet a party needs a `TransferPreapproval` before it can receive CC/cBTC. Idempotent (a no-op if one already exists) and a no-op entirely on the sandbox (MockRegistry needs none). Best-effort — always answers `{ok: true}` even if the underlying preapproval attempt failed; check `GET /wallet/incoming` / `GET /wallet/holdings` to confirm funds actually arrived.