GET | /userconsent/{UserId}/{Country} | ||
---|---|---|---|
GET | /userconsent |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserId | path | string | No | |
Country | path | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ConsentDefinitionId | form | string | No | |
Consents | form | Dictionary<string, bool> | No | |
ConsentedDate | form | DateTime | No | |
Lang | form | string | No | |
Consented | form | bool | No | |
Expired | form | bool | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /userconsent/{UserId}/{Country} HTTP/1.1 Host: hcbtas-q-albamfs-api.azurewebsites.net Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"consentDefinitionId":"String","consents":{"String":false},"consentedDate":"0001-01-01T00:00:00.0000000","lang":"String","consented":false,"expired":true,"id":"String"}