Mixed MediaType Conversations and API time limits on get call conversation and get callback conversation

[RomanSmoll]

Hello.

Imagine a scenario where the conversation has 2 or more mediaTypes
For instance: callback that becomes a call when addressed.

You can see it in a timeline based on sessions,
You can see call and callback entities when you use API getConversation.
Here is one participant of that conversation structure:

"participants": [
    {
      "id": "id",
      "startTime": "time",
      "endTime": "time",
      "connectedTime": "time",
      "name": "Mobile Number",
      "queueId": "queueId",
      "queueName": "queueu",
      "purpose": "customer",
      "participantType": "External",
      "address": "some address",
      "ani": "some ani",
      "aniName": "Mobile Number",
      "dnis": "tel",
      "wrapupRequired": false,
      "attributes": {
      "some attributes"
      },
      "calls": [ HERE:"some info here"],
      "callbacks": [HERE:"Some info here too"],
      "chats": [],
      "cobrowsesessions": [],
      "emails": [],
      "messages": [],
      "screenshares": [],
      "socialExpressions": [],
      "videos": []
    },

So it makes sense to say that you can fetch this conversation 3 different ways:

• by using getConversation (id)
• by using getConversationCall(id)
• by using getConversationCallBack(id)

The issue here is, that his conversation is only available through the first API() after some time;
For cinversations that are 2 months prior we get

• getConversation(id) gives 200 OK
  *getConversationCall and getConversationCallBack(id) gives Not Found (i do not recall the error code..prolly 404)

For cases within last month we get 200 OK for all of the three API

Does this make any sense to you , former Forumers ?
We cannot find it in API description but what is the Time (Date) limitations on these mediatype-specific API?
Have a great day!

[tim.smith]

Per https://developer.genesys.cloud/routing/conversations/#request-a-conversation:

Conversations may be queried for up to 60 days at which point we will return a 404 error. To retrieve historical conversation data, customers will need to utilize the analytics API GET /api/v2/analytics/conversations/{conversationId}/details. For retrieving custom participant attributes linked to an interaction beyond that 60 days a developer needs to use the async GET /api/v2/analytics/conversations/details/jobs/{jobId} as they will not be available in GET /api/v2/analytics/conversations/{conversationId}/details. Note that not all conversation data is maintained.

Use analytics queries or jobs for accessing historical data.