Authentication FAQs

The full message of the error you may encounter is:
RegistrationError: {Service}: Maximum number of unregistered requests exceeded. Your request was authenticated using {an HTTP request parameter|a cookie|an IP address|a SOAP header}. Your username is {username}. Please visit http://www.xignite.com/registration-help for more information.

There are a few possible reasons for encountering this error:
  • If you are a subscriber, you will never receive this error unless you are using an incorrect token to authenticate your requests. To fix the problem, simply review your list of authentication tokens and verify you are using a correct one. You can do this by navigating to My Account and clicking on Manage My API Tokens.
  • If you are not registered or subscribed to the service and did not pass any authentication tokens with your request, then it simply means that we could not authenticate your request and therefore it was rejected. Most likely in this case the error message will say that "Your request was authenticated using an IP address" and your username will be that IP address. This is simply because IP-based authentication is the default authentication method if none others are provided.
  • If you are registered or subscribed to the service and use IP-based authentication, then it could mean that your IP address changed and it is not included in your list of authentication tokens. To fix the problem, simply add the IP address provided in the message to your list of authentication tokens. You can do this by navigating to My Account and clicking on Manage My API Tokens.
  • If you are registered or subscribed to the service and use SOAP Header or HTTP RequestParameter authentication, then it could mean that you are passing the wrong authentication token. To fix the problem, simply review your list of authentication tokens and verify you are using a correct one. You can do this by navigating to My Account and clicking on Manage My API Tokens.
  • If you are only registered for a free trial, this could also mean that you have exceeded your free trial hit limit for this service. To verify this, go to My Account, click on Check My Free Trial Status and check if the Remaining Hits value is 0 for the service you are using. If it is, contact your sales representative or sales@xignite.com to request an extension of your free trial.
If you are not sure of which method you use to authenticate your request, please check the value of the Identity data element returned with your data. This is provided as a standard data element on all APIs. 
  • If Identity = IP, verify that the IP of your server is properly registered. If your IP is dynamic, you should probably use a different method for authentication. You may also believe that you are properly passing a SOAP Header with your requests but this header is not being recognized by our system. IP authentication is not recommended as it is common for IPs to change.
  • If Identity = Cookie, verify that you are passing the proper cookie with your requests. Note that when calling a service using your browser, the system will by default pass a cookie with your requests if it exists. Cookies are set up when you log into your account using your browser.
  • If Identity = Request, this means that our system is reading your username from the 'Header_Username' or '_token' value passed with your POST or GET requests. Verify that you are passing the proper value.
  • If Identity = Header, this means that our system is reading your username from the Username element from the SOAP Header value passed with your SOAP requests. Verify that you are passing the proper value.

IP authentication is discouraged because your application will break if your IP addresses change. We highly recommend using API token authentication to avoid this problem. If you still wish to use IP authentication, there are a few simple steps to follow in order to add or remove IP addresses on your User Account. When using IP authentication, it is critical the IP is added before any queries are executed or the queries will error.

First, you must log in to the Xignite Web Site - once logged in, follow the steps here:
  1. Go to the Manage My API Tokens page within the My Profile area
     
  2. On that page, click the  button
     
  3. In the Add Token box, change the first dropdown to “IP”
     
  4. In the 2nd blank box that appears, enter the full IP address
     
  5. Once you confirm it is entered correctly, press 
     
  6. Note: To lock in this change, press  or you will not actually Save this new IP to the account.

No, this is not permitted because our Services are hosted on in a virtual environment across many servers.
Due to load balancing or other server shuffling activities, the IP address for an API could change at any time without notice. You cannot rely on any IP address to remain static. The proper way to code to an Xignite API destination is via the API URL.

If you have any issues using an Xignite API, please send an e-mail to support@xignite.com so that we can assist you.

An API Token is an alphanumeric code, unique to your Xignite Account, which can be used from any system to validate your API calls. API tokens are passed in the Username field of any SOAP code.  It is also our preferred method of authentication over using IP or E-mail Addresses.  For example, an API Token can be used in a multi-server configuration without following up to add each IP address to your account. If load balancing switches the call to originate/execute from another server, this is seamless when using an API Token. This allows for a more dynamic and error-free configuration. 

To add an API Token to your account, follow these steps:

 

  1. Go to My Account > Manage My API Tokens: https://www.xignite.com/MyAccount/Tokens.aspx
     
  2. Click the blue  button, and select the option “API” from the dropdown
     
  3. The window will say “A random token will be generated.”, then click the blue  button
     
  4. Once you go back to the Token list/table, make sure to click  or it will not actually equip your account with the new Token.
     
  5. Once it saves, you will see the alphanumeric string in the table as a new row.