Hello, Crazyers!
Starting with our next release, there will be an important change related to Datacrazy's internal routes.
The internal routes currently in use will no longer be available. After the update, the same data must be accessed exclusively through the public (external) routes.
______________________________________________________________________________
What is changing?
If you use a route in your system that has CRM, messaging and accounts in the URL, such as:
https://crm.g1.datacrazy.io/api/crm/
this means it is an internal route.
After the update, this endpoint will no longer be available at this URL and must be accessed through the corresponding public route.
In most cases, the change consists of replacing the internal address with the public address and adjusting the API version.
Examples of changes
Internal Route — stops working
Public Route — accessible to everyone
IMPORTANT: Webhooks are not affected.
How it was | How it will be |
|
|
|
|
|
|
______________________________________________________________________________
Attention
If your system, integration, automation, or application currently uses any of the internal routes, we recommend updating them before the next release to avoid downtime or integration failures.
Summary: routes that use internal domains, such as crm.g1.datacrazy.io and messaging.g1.datacrazy.io, must be replaced with the corresponding public routes available at api.g1.datacrazy.io.
We ask everyone to make the necessary adjustments before the update.
IMPORTANT: Webhooks are not affected.
Datacrazy Team