You’ll usually see a *401: Authentication error* when trying to connect to Bob’s API, either through Bob endpoints or tools like Postman. This happens when the system can’t verify the credentials being used.
This guide walks you through the quick checks that can help you resolve it:
- When you hit a 401, make sure the request is using the right authentication method and that your Service User is set up correctly.
- In your API client, set the Authorization type to Basic Auth and enter your Service User ID and token.
- Double-check the credentials you’re using. You can refresh the token on Bob and try to connect again.
- Confirm that your Service User has permission to access the data you’re trying to retrieve.
- Make sure the Service User account is active and assigned to a permission group.
- If are you are using personal API tokens, note that these are no longer supported for Bob API authentication. A Service User with Basic Authentication is the required method, and using anything else will trigger a 401. More details can be found here: Important API changes
Hopefully this can help. But if you run with this issue despite confirming all these, please, reach out to our support team.