Skip to main content
THE IDENTITY

One key, one integration

Partners authenticate with a registered RSA public key. The matching private key stays in your infrastructure. Bullring stores the public key and maps it to your team and store.

Required headers

X-Key-Id is public metadata. It selects the public key used for verification.

Store scope

The key is associated with an existing Bullring store integration. Your requests cannot access another store or an unrelated subaccount.

Optional IP allowlisting

When registering a partner integration in the dashboard, you can provide exact IPv4 or IPv6 addresses allowed to send requests for that integration.
  • Leave the list empty to allow requests from any source IP.
  • Separate multiple addresses with commas or new lines.
  • A request from an address that is not on the list returns 403 with code IP_NOT_ALLOWED.
  • The allowlist applies to the partner integration and its signing keys.
  • CIDR ranges are not accepted; add each exact source address.
Make sure the configured address is the public egress IP seen by Bullring, not an internal container or workstation address.

Key rotation

Register a new public key before retiring the old one. Both keys may be active during the overlap. Revoke the old key only after all workers use the new key.

Keep private material private

Do not send the PEM private key in an HTTP header, commit it, or log it. The only signature header value sent over HTTP is the Base64-encoded signature for that request.