Skip to main content
POST
/
api
/
v1
/
widget
/
users
/
{userId}
/
disclosures
curl -X POST https://api.zbdpay.com/api/v1/widget/users/{userId}/disclosures \
  -H "apikey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "acceptedDisclosureTypeIds": [6]
  }'

{
  "success": true,
  "message": "Publisher user disclosure agreements recorded successfully.",
  "data": {
    "acceptedDisclosureTypeIds": [6]
  },
  "error": null
}

​
Description

Records the user’s acceptance of the latest version of each disclosure type in acceptedDisclosureTypeIds. Use this from your server only if your integration collects disclosure acceptance outside the hosted widget. Do not call this endpoint from a browser, mobile client, game client, or WebView.

​
Configuration

​
Header Parameters

​
apikey
string
required
Your ZBD project API key.
​
Content-Type
string
Content Type

​
Path Parameters

​
userId
string
required
The ZBD user ID returned when the widget user is created or resolved.

​
Body Parameters

​
acceptedDisclosureTypeIds
array
required
Disclosure type IDs accepted by the user. ZBD records acceptance for the latest version of each type.
curl -X POST https://api.zbdpay.com/api/v1/widget/users/{userId}/disclosures \
  -H "apikey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "acceptedDisclosureTypeIds": [6]
  }'

{
  "success": true,
  "message": "Publisher user disclosure agreements recorded successfully.",
  "data": {
    "acceptedDisclosureTypeIds": [6]
  },
  "error": null
}

​
Disclosure Type IDs

Disclosure typeType ID
Terms of Service2
Privacy Policy3
Electronic Funds Transfer6

​
Existing Users

If a user already exists and needs to accept a current disclosure, call this endpoint. Do not rely on an idempotent user-create call to update disclosure acceptance for an existing user.

​
Errors

StatusReason
400acceptedDisclosureTypeIds is empty, missing, or contains an unknown disclosure type
401Missing or invalid API key
403The API key is not allowed to access widget disclosure APIs
404userId does not belong to the project associated with the API key