Choose the right credential
Browser workflows use the HttpOnly session cookie. Mutations also require the current X-CSRF-Token from GET /api/v1/session and the allowed browser Origin. Creating secrets, managing webhooks, issuing license codes and other sensitive owner operations require recent authentication with verified MFA.
Publisher automation uses an expiring product credential created by an owner under Automation credentials & publisher signing identities. Send Authorization: Bearer psvc_… without Cookie or Origin headers. A token is valid only for its product, current issuer membership and declared release scopes. It cannot manage owners, signing keys, webhooks, license codes or billing.
Registered desktop clients use the separately configured native OAuth flow with PKCE and the system browser. Browser cookies and publisher automation credentials are not desktop identity credentials. Check the reference for each route’s supported authority.
A read-only automation request
Set PRAXICAL_API to your configured store origin. Store the token in CI secret storage and disable command tracing. Use release:read for workspace and validation reads, release:write for draft/upload work, and release:publish only where the route explicitly accepts it.
curl --fail-with-body \
-H 'Accept: application/json' \
-H "Authorization: Bearer $PRAXICAL_PUBLISHER_TOKEN" \
"$PRAXICAL_API/api/v1/publisher/products/$PRAXICAL_PRODUCT_ID"Handle errors and asynchronous work
API errors contain error.code and error.message; use the machine code for decisions and preserve X-Request-ID when asking for support. Unknown typed request fields are rejected. A 409 usually means a revision or idempotency conflict; reload the affected record before deciding whether to repeat the command.
For commands that require Idempotency-Key, create one opaque value per intended action and keep it across timeouts. Reusing the key with changed fields returns a conflict. A 202 response means work is queued, not complete: poll the returned order, release, delivery or redemption resource. Poll at a moderate interval and pause while your page is hidden.
Check the generated API reference for the exact request shape, revision field, response status, authority and pagination. The API candidate is not frozen for independent desktop compatibility yet.