• Share
    • Twitter
    • LinkedIn
    • Facebook
    • Email
  • Feedback
  • Edit
Show / Hide Table of Contents

PUT Person/{id}/Consent/{purpose}

Some tooltip text!
• 1 minute to read
 • 1 minute to read
PUT /api/v1/Person/{personId}/Consent/{purpose}

Set a specified type of consent on the person.

Path Part Type Description
personId int32 The person id Required
purpose string The Key of the purpose this affects. e.g. 'STORE' or 'EMARKETING'. Required

Query String Parameters

Parameter Name Type Description
source string Required The Key of the source of this consent. e.g. 'USER', 'WEBFORM' or 'API'.
legalBase string Required The Key of the legal base for this consent. e.g. '61A', '61B', '61F'
comment string A comment regarding this consent. May be null or empty.
PUT /api/v1/Person/{personId}/Consent/{purpose}?source=adipisci
PUT /api/v1/Person/{personId}/Consent/{purpose}?legalBase=dolor
PUT /api/v1/Person/{personId}/Consent/{purpose}?comment=quia

Request Headers

Parameter Name Description
Authorization Supports 'Basic', 'SoTicket' and 'Bearer' schemes, depending on installation type.
X-XSRF-TOKEN If not using Authorization header, you must provide XSRF value from cookie or hidden input field
Accept Content-type(s) you would like the response in:
SO-AppToken The application token that identifies the partner app. Used when calling Online WebAPI from a server.

Response:

No Content

Response Description
204 No Content

Response body: TimeZoneData

Sample request

PUT /api/v1/Person/{personId}/Consent/{purpose}
Authorization: Basic dGplMDpUamUw
Accept: application/json; charset=utf-8
Accept-Language: sv

Sample response

HTTP/1.1 204 No Content
Content-Type: application/json; charset=utf-8

null
© SuperOffice. All rights reserved.
SuperOffice |  Community |  Release Notes |  Privacy |  Site feedback |  Search Docs |  About Docs |  Contribute |  Back to top