FAQs

1. "My request keeps saying 'invalid API key,' but I checked my key, and it is valid. What's the issue?"

If you are encountering an "invalid API key" error, it may not necessarily be a problem with your API key itself. This issue could be related to how our DNS (Domain Name System) is configured for security purposes.

Technical Explanation:

• Our DNS configuration designates the www subdomain (www.britelink.io) as the main domain for our API.
• This means that DNS records are typically set up to point to the IP address associated with the www subdomain, and the web server is configured accordingly.

Solution:

To resolve the "invalid API key" issue, we recommend that you adjust your URL requests by adding "www" to the domain. Instead of using https://www.britelink.io/api/v1/drugs, please use https://www.britelink.io/api/v1/drugs.

Why Adding "www" Helps:

• Adding "www" to the URL ensures that your requests go through the configured DNS records and reach our CORS (Cross-Origin Resource Sharing) server-side access control as intended.
• This adjustment helps our server authenticate your requests correctly, preventing the "invalid API key" error and ensuring a smooth API interaction.

By following this recommendation and including "www" in your API requests, you should be able to resolve the issue and access our API successfully. If you continue to experience any problems or have further questions, please feel free to reach out to our support team for assistance.