Forum Discussion
EvanMartinez
7 years agoModerator
Hi Jack,
As a best practice for User Token you would want to keep them secure and be careful of sharing them. They function as a form of authentication within our API calls and can allow access to your data. To be on the safe side the end of this User Token has been cut out. If that was an actual User Token I would suggest deactivating it and instead replacing it with a new one if possible just to be on the safe side.
As for error code 11 that error often comes up when the body of a Webhook contains XML characters that the API has trouble differentiating from your actual Webhook code. They can cause the message to become garbled. Do any of these fields you are passing over contain text elements and possible unique characters or XML character? Common culprits can be ", ', <, >, and &.
As a best practice for User Token you would want to keep them secure and be careful of sharing them. They function as a form of authentication within our API calls and can allow access to your data. To be on the safe side the end of this User Token has been cut out. If that was an actual User Token I would suggest deactivating it and instead replacing it with a new one if possible just to be on the safe side.
As for error code 11 that error often comes up when the body of a Webhook contains XML characters that the API has trouble differentiating from your actual Webhook code. They can cause the message to become garbled. Do any of these fields you are passing over contain text elements and possible unique characters or XML character? Common culprits can be ", ', <, >, and &.