403 Forbidden Error with Basic Auth

[Lukas-Merckens]

Hello,

I am trying to authenticate with the API using Basic Auth but consistently receive a "403 Forbidden - Authentication failed: Invalid key-value pair" error.

• My Application ID is: a562f428-8501-4446-aef7-89714bf7e636
• My server's IP address (the Origin) is: 95.216.154.127

I have double-checked the credentials and the Origin setting in my dashboard. The manual curl command also fails with the same error. Could you please check if my account is active and if there are any issues with my credentials or IP address?

Thank you for your help.

Kind regards,

Lukas

[astroanu]

Hi, seems you're using the account credentials in the basic auth. You need to use the application id and the secret you get, when you create the application from the dashboard.

You can find this information on the docs here

[Lukas-Merckens]

Hi astroanu, Thank you for the quick reply. I understand. I can confirm I am using the Application ID and Secret from the dashboard, not my account login credentials. I have deleted and recreated the application already to be absolutely sure. My current, active Application ID is a562f428-8501-4446-aef7-89714bf7e636. The Origin is correctly set to my server's IP, http://95.216.154.127. I have also triple-checked for any copy-paste errors. The `curl` command test from the server also fails with the exact same "403 Forbidden - Invalid key-value pair" error. Since I am certain the credentials are correct, the issue must have another cause. Could you please investigate the following on your end. 1. Can you confirm from your server logs that my Application ID is fully active and has permissions to access the `/api/v2/bodies/positions` endpoint? 2. Can you please check if there is any kind of firewall rule or block affecting my server's IP address (`95.216.154.127`)? 3. Is it possible there is a bug on your side that is causing the "Invalid key-value pair" error, even with a correctly formatted Basic Auth header? Thank you for looking into this more deeply. Best regards, Lukas ============================== L U K A S M E R C K E N S BENDLGASSE 16, A-1120 WIEN E-MAIL: ***@***.*** MOBIL: + 43 676 318 71 49 [Folie01.jpg] astroanu ***@***.***> schrieb am Mittwoch, 1. Oktober 2025 um 18:22:

…

astroanu left a comment [(AstronomyAPI/Samples#216)](#216 (comment)) Hi, seems you're using the account credentials in the basic auth. You need to use the application id and the secret you get, when you create the application from the dashboard. You can find this information on the docs [here](https://docs.astronomyapi.com/) — Reply to this email directly, [view it on GitHub](#216 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BTLBQZP44N2NEVPCQOBZVJT3VP5TLAVCNFSM6AAAAACIATJRRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNJXGE3DMNBRHE). You are receiving this because you authored the thread.Message ID: ***@***.***>

[bjutii]

Hi @Lukas-Merckens ! Did you get this to work? I'm facing the same issue. I've followed the exact steps on the Getting Started page.

How does the Origin work in the Create Application? I'm testing this through Bruno and not from a specific URL. That shouldn't be a problem right?

[astroanu]

@bjutii We had origin as an extra cors security but later removed that validation. I'd still recommend using it if you're calling the API from a web browser, so we can see who's using your API key, otherwise it's not needed and you can put your website there.

[astroanu]

@Lukas-Merckens Can you post the example code you're using ? It could be you're not sending the basic auth header correctly. You can read about how basic auth works at https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Authentication