Overview

In the CRM Datacrazy, when a conversation is archived (hidden), it no longer appears in the standard list of tickets.

If you need to show this conversation again, you can change its status without having to open a ticket, using an API call.

The operation basically consists of:

1. Identifying the conversation ID and the token

2. Sending a request to the system API

3. Changing the archived status to false

After that, once the API returns status 200 (OK), the conversation goes back to appearing normally in the CRM.

Comfort and Agility

For your convenience, here’s a ready-made link for ReqBin, just fill in idConversation and token and send it.
ReqBin link for the API call → ReqBin link → https://reqbin.com/uewupbd9

Video Tutorial

If you want to learn a bit more, check out how to do it the hard way below!

API Endpoint

Method:

POST

URL:

https://messaging.g1.datacrazy.io/api/messaging/conversations/__idConversation__/archive

URL Parameters

Replace:

__idConversation__

with the conversation ID you want to unhide.

You can get this ID as shown in the reference video.

Required headers

The request must contain the authorization header:

Authorization: Bearer __token__

Replace:

__token__

with one of the following:

• Admin user token → See how to get it in the video

• API token generated by an admin

Request body (JSON)

Send the following JSON:

{
  "archived": false
}

This field defines that the conversation is no longer archived.

Full call example

URL:

https://messaging.g1.datacrazy.io/api/messaging/conversations/123456/archive

Headers:

Authorization: Bearer SEU_TOKEN_AQUI
Content-Type: application/json

Body:

{
  "archived": false
}

Expected result

After executing the call:

• The conversation will be unarchived

• It will show again in the CRM conversation list

Important notes

Only users with a valid token can run this operation.

The conversation ID needs to be correct for the change to work.

If the conversation is still hidden, check:

• If the token has permission

• If the provided ID matches the correct conversation.