You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for taking the time to submit an issue with all the details shown below. Our engineering team monitors issues submitted and strives to respond with 1-2 business days.
PHP version: 8.3
SDK version: 3.9.0
Current behavior
When creating a entity on the endpoints: Chat Handle, Email, Phone, Social Profile and Website there isn't a ID of the created entity being returned.
Expected behavior
Returning a Resource-ID in the response so this can be saved and used for Update and Deletion of the entity. Just like on the Customer endpoint itself. This then can be used for the update en delete endpoints as this is mandatory according to the docs and the code in the SDK itself:
I have had contact with support. But no help is given other than a resources intensive one for both ends. I am posting this here because i feel like this a a bugg on the API end. I feel this should be a easy fix.
I would like to keep this issue open untill a fix is in place.
The text was updated successfully, but these errors were encountered:
Thank you for taking the time to submit an issue with all the details shown below. Our engineering team monitors issues submitted and strives to respond with 1-2 business days.
Current behavior
When creating a entity on the endpoints: Chat Handle, Email, Phone, Social Profile and Website there isn't a ID of the created entity being returned.
Expected behavior
Returning a Resource-ID in the response so this can be saved and used for Update and Deletion of the entity. Just like on the Customer endpoint itself. This then can be used for the update en delete endpoints as this is mandatory according to the docs and the code in the SDK itself:
I have had contact with support. But no help is given other than a resources intensive one for both ends. I am posting this here because i feel like this a a bugg on the API end. I feel this should be a easy fix.
I would like to keep this issue open untill a fix is in place.
The text was updated successfully, but these errors were encountered: