Deprecation: conversations/messages/inbound/open endpoint (UPDATED 18 April 2024)

[John_Carnell]

Hi Lenard,

If the old endpoints are removed and you are using them in the old .NET SDK you will need to upgrade. If you are not using the endpoints being removed you can still use the old SDK. I hope that helps clarify things.

Thanks,
John Carnell
Director, Developer Engagement

[LenardFurr]

It does, thanks.

[vmh.falcao]

Hi,

We have a question about the customAttributes. In the old endpoint, we have the object metadata/customAttributes; in the new endpoint, we have only the metadata object. We don't have the customAttributes inside the metadata.

When I create a new conversationid I can't see the attributes on Participant Data.

How can we pass this information when I create the new conversationid?

API: https://api.sae1.pure.cloud/api/v2/conversations/messages/{integrationid}/inbound/open/message

Request:

{
"channel": {
"from": {
"firstName": "name",
"lastName": "lastname",
"idType": "Phone",
"id": "5531999999",
"nickname": "nickname"
},
"time": "2025-01-10T18:37:16.274Z"
},
"text": "Teste ola 2222222",
"metadata": {
"brokerin": "55888888888",
"tipo": "open"
}
}

[Greg_Boston]

@vmh.falcao the request body channel.metadata.customattributes is the same in the old endpoint and the new one (api/v2/conversations/messages/{integrationid}/inbound/open/message). you should be able to pass it exactly the same as you did before.

[vmh.falcao]

Hi Greg,

Not worked.

Request:
{
"channel": {
"from": {
"firstName": "name",
"lastName": "lastname",
"idType": "Phone",
"id": "5599999999",
"nickname": "nickname"
},
"time": "2025-01-10T18:40:16.274Z",
"metadata": {
"customattributes": {
"context.gc.brokerin": "5599999999",
"context.gc.tipo": "open"
}
}
},
"text": "Teste ola 2222222"
}

[Greg_Boston]

actually the field is named customAttributes try that (notice the case)

"metadata": {
  "customAttributes": {
    "": ""
  }
}

[vmh.falcao]

It's working now. Thank you Greg.