Explore our FAQs for quick answers to common queries, ensuring a seamless experience. Equip yourself with valuable insights and effective solutions, maximizing your experience and interactions with our platform.

Should you have reviewed the FAQs and find yourself in need of further clarification, don’t hesitate to Reach out

Common causes of 401 responses include the following;

  • Absense of accountId in request headers
  • Invalid accountId passed in request headers
  • Invalid or expired access_token passed in request headers

It’s crucial to verify that your application is properly configured to handle the access_token obtained during authentication

It is of utmost importance to always pass your accountId in request headers. Failure to do so might lead to some potential errors.

For applications operating in a multi-instance environment, implementing a robust caching and locking mechanism is necessary. This ensures that only one instance authenticates with our system, and the same instance can efficiently update the access_token value in your cache.