Restricted Accesss

​

Overview

{
    "success": false,
    "message": "You are restricted to access the site. Contact to Niobi support for further information."
}

​

Common Causes and How to Resolve

1. IP Address Not Whitelisted
   The IP address used to initiate the API request has not been whitelisted on our system for either the sandbox or production environment. How to Resolve: Ensure you share your IP addresses that will be used to access our APIs for whitelisting by sending an email to us at support@niobi.co.
2. Dynamic or Changing IP Address
   If your network or system uses a dynamic IP or if you’re working from a location where the IP frequently changes, the request may come from an IP address that is not whitelisted with us. How to Resolve: Configure a static IP address on your server or system and share it with us. Alternatively, you can share updated IP addresses in case your system configuration changes during the course of your integration with us. Click here to learn more about configuring a static IP.
3. Environment Misconfiguration
   The IP address was not whitelisted for the correct environment (e.g., configured for sandbox but not for production). How to Resolve: Confirm that the IP addresses shared are configured for the specific environments you’d like them to be applied to. You can do this by sending an email to support@niobi.co with your specifications, and our team will confirm this for you.

​

Best Practices

• Verify your IP Address for Whitelisting
  • Ensure you share and specify all IPs that need access to our APIs along with the specified environments - sandbox and production.
• Use Static IPs for Development and Integration
  • Static IPs minimize the risk of access issues caused by IP changes.
• Test Before Going Live
  • Verify your IP configurations by performing some live tests before going live to ensure smooth access.