Obtain the preference center ID from the OneTrust UI; authenticate with YOUR_ONETRUST_TOKEN scoped to PreferenceCenter.Read.
Fetch the preference center schema via GET https://{hostname}/api/consentmanager/v3/preference-centers/{preferenceCenterId}/schema; the response defines available purposes, their descriptions, and current user-consent state.
Render your custom UI using the schema: for each purpose in the schema, display a toggle mapped to the purpose's id and defaultStatus fields; pre-populate toggles from the user's existing consent via the GET preferences endpoint.
On form submit, POST the updated preferences to https://{hostname}/api/consentmanager/v3/receipt with a body containing the identifier (e.g., email), consentDate, and updated purposes array (each with purposeId and status OPTED_IN or OPTED_OUT).
Capture the receiptId from the response and display a confirmation to the user; store the receiptId server-side linked to the user's account for audit retrieval.
Integrate the preference center into account-settings pages and any transactional emails containing a 'Manage Preferences' link; the link should carry a short-lived token that auto-authenticates the user to pre-populate their current state.
Known gotchas
The preference center schema can change when privacy teams update OneTrust configurations; your custom UI must re-fetch the schema on each load rather than caching it long-term to avoid rendering stale or removed purposes.
OneTrust's default preference center uses its own hosted iframe; a custom schema-API-driven UI is a separate configuration and requires the Enhanced Preference Center feature to be enabled in your OneTrust subscription.
POSTing a receipt without all required fields (particularly identifier type and consentDate) results in a 400 error; the error message may not specify which field is missing — validate against the schema before submission.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp