Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Submit a new GDPR request gives a bad request

  • 1.  Submit a new GDPR request gives a bad request

    Posted 06-05-2025 18:13

    Tobias_Zackrisson | 2018-05-25 09:38:20 UTC | #1

    When adding all details and sending the request I'll get the bad request as a result. In the attached image I have scrambled the phone number just for this post. I have also added the new GDPR role on my user so that is not the issue either.

    { "status": 400, "code": "bad.request", "message": "Invalid data", "messageParams": {}, "contextId": "0068c85b-f659-4277-9846-28a47d7db217", "details": [], "errors": [] }

    Thanks! Tobias

    anon29353067 | 2018-05-25 16:29:01 UTC | #2

    Hi Tobias. The above request is invalid, which is why you are getting a 400. replacementTerms are only valid on GDPR_UPDATE requests, not on GDPR_EXPORT. Additionally, it is only necessary to include the fields being used. For example, exporting by both a name and a phone number may not yield the desired results.

    So a valid request for the phone number would be as simple as

    {
   "requestType": "GDPR_EXPORT",
   "subject": {
      "phoneNumbers": ["+46XXXXXXX"]
   }
}

    See https://help.mypurecloud.com/articles/how-is-genesys-purecloud-addressing-gdpr/ for more information.

    We will look at improving the API documentation, thank you for the feedback.

    Tobias_Zackrisson | 2018-05-28 09:58:10 UTC | #3

    Thanks for the help Adam! Will the result be presented in JSON? Would be cool to have a choice to select CSV and it's available for download in your inbox for "Exports".

    anon29353067 | 2018-05-31 17:48:03 UTC | #4

    Yes, results will generally be JSON format. Inbox as a delivery location and other data formats for export are items we will have to review for future development. Thanks again for the feedback!

    system | 2018-07-01 17:48:09 UTC | #5

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 2912



Related Content