Stuck? Please see some frequently asked questions
Troubleshooting 401 responses
401
responses include the following;accountId
in request headersaccountId
passed in request headersaccess_token
passed in request headersaccess_token
obtained during authenticationaccountId
in request headers. Failure to do so might lead to some potential errors.access_token
value in your cache.Troubleshooting 403 responses
403
responses consistently pertain to permission issues, indicating that the actor lacks the necessary permissions to access the desired resource. While it might not initially appear as a severe error, it can significantly impede your interaction with the Nomba API.In the Nomba ecosystem, accounts represent a collection of resources, requiring proper permissions for access. For instance, without adequate permissions within an account, accessing transaction data for that account is restricted.As outlined in the authentication documentation, your API Keys are endowed with default Admin privileges, granting access to all accounts affiliated with your business or organization. However, you have the flexibility to manage resource access through the grant permissions to account document.If you encounter persistent 403 errors, kindly contact us via the designated support page for assistance.Interactions with the Sandbox environment