billions-minister-2901
02/23/2024, 7:11 PMchilly-king-10285
02/23/2024, 7:11 PMchilly-king-10285
02/23/2024, 7:11 PMbillions-minister-2901
02/23/2024, 7:13 PMchilly-king-10285
02/23/2024, 7:13 PMchilly-king-10285
02/23/2024, 7:13 PMAuthorization
header of your HTTP requests. Here's an example: bash GET /admin/identities HTTP/1.1 Host: {{project.slug}}.<http://projects.oryapis.com|projects.oryapis.com> Accept: application/json Authorization: Bearer {{API-Key}}
Replace {{API-Key}}
with your actual API Key. Including sensitive information like API Keys in the query string is generally not recommended due to security concerns. It's best to follow the recommended practices for using API Keys in Ory. For more information, you can refer to the [Authorization with API Keys](https://www.ory.sh/docs/concepts/personal-access-token) documentation. Sources: - [Authorization with API Keys](https://www.ory.sh/docs/concepts/personal-access-token) - [Ory APIs](https://www.ory.sh/docs/getting-started/local-development#ory-apis)billions-minister-2901
02/23/2024, 7:13 PMchilly-king-10285
02/23/2024, 7:13 PMchilly-king-10285
02/23/2024, 7:14 PMAuthorization
header of your HTTP requests. While some APIs may allow authentication via query parameters, it's generally considered less secure and not a best practice. Query parameters are often logged in various places, cached, and can be exposed in the browser history, which can lead to potential security risks. Therefore, even if it technically works, it's not recommended due to the security implications. Always follow the recommended practices for using API Keys in Ory, which is to include them in the Authorization
header. For more information, you can refer to the [Authorization with API Keys](https://www.ory.sh/docs/concepts/personal-access-token) documentation. Sources: - [Authorization with API Keys](https://www.ory.sh/docs/concepts/personal-access-token) - [Ory APIs](https://www.ory.sh/docs/getting-started/local-development#ory-apis)