SetConsentStatusRequestStay organized with collectionsSave and categorize content based on your preferences.
Page Summary
The JSON representation outlines the structure of a consent request, detailing the user's action and the time it was taken.
This structure uses two main fields:consentAction, indicating the type of user consent (e.g., accept, reject), andactionTimestamp, recording the precise time of the user's action.
consentActionis an enumerated value from theConsentActionresource, whileactionTimestampis a string formatted according to the Timestamp standard.
A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples:"2014-10-02T15:01:23Z"and"2014-10-02T15:01:23.045123456Z".
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-10-03 UTC."],[],["The core content defines the structure of a consent request from GTAF to DPA, represented in JSON. The request contains two key fields: `consentAction`, an enumeration indicating the user's action, and `actionTimestamp`, a string representing the precise time the action occurred. The timestamp follows the RFC3339 UTC \"Zulu\" format, with nanosecond resolution. These fields are the essential elements of the consent request, detailing what the user did and when.\n"]]
