Authorizations API

Save a physician signature

Store an authorized PNG signature for an active rendering provider, with an attestation.

POSThttps://app.mindbill.org/partner/v2/rfas/providers/{providerId}/signature

Run once per physician from an administrator setup screen before that physician signs RFAs. This does not sign any request; each generated form is reviewed and signed separately.

AuthenticationServer API key or browser session + Origin

Permissions by credentialServer: rfas:sign · Browser: rfas:sign + organization:manage

IdempotencyRequired for safe retries

Organization capabilitytreatmentBilling must be enabled

Use this URL with a server API key or a browser session and its exact allowed Origin. Both credentials use the same request and response contract. See the component API inventory for exact paths and SDK methods.

Path parameters

FieldTypeDescription

providerIdRequired

string

Saved rendering provider identifier.

Request body

FieldTypeDescription

contentBase64Required

string

Canonical base64 PNG without a data-URL prefix.

Decoded ≤ 512 KiB, ≤ 4096 px per side, ≤ 4 million pixels

physicianAuthorizedRequired

true

Confirms the physician authorized this signature for RFA use.

actorReferenceRequired

string

Stable identifier of the authenticated human saving the signature. Never an API key.

1–200 characters

Examples

curl 'https://app.mindbill.org/partner/v2/rfas/providers/rp_example/signature' \
  --request POST \
  --header "Authorization: Bearer $MINDBILL_API_KEY" \
  --header 'Idempotency-Key: signature-rp_example-1' \
  --header 'Content-Type: application/json' \
  --data '{
  "contentBase64": "iVBORw0KGgo...",
  "physicianAuthorized": true,
  "actorReference": "user_example"
}'

curl 'https://app.mindbill.org/partner/v2/rfas/providers/rp_example/signature' \
  --request POST \
  --header "Authorization: Bearer $MINDBILL_BROWSER_TOKEN" \
  --header 'Origin: https://your-app.example' \
  --header 'Idempotency-Key: signature-rp_example-1' \
  --header 'Content-Type: application/json' \
  --data '{
  "contentBase64": "iVBORw0KGgo...",
  "physicianAuthorized": true,
  "actorReference": "user_example"
}'

Response

200 OK

{ "data": { "providerId": "rp_example", "signatureConfigured": true } }

FieldTypeDescription

data.providerIdRequired

string

The provider whose signature was saved.

data.signatureConfiguredRequired

true

Always true on success.