Skip to main content
The Benzinga API uses API Keys to authenticate requests. Your API Key is a unique identifier that grants access to specific data and features based on your subscription.
Keep your API Key secure. Do not share it in publicly accessible areas such as GitHub, client-side code, or unsecured communications. If you believe your key has been compromised, contact support immediately.
You can view and manage your API Key in your Benzinga Developer Console.

​
Authentication Methods

The Benzinga API supports two methods for authentication. We strongly recommend using the HTTP Header method for production applications as it is more secure and prevents your key from appearing in URL logs. To authenticate via the header, include the Authorization header with the value token <YOUR_API_KEY>. 
Authorization: token <YOUR_API_KEY>

​
2. Query Parameter

For quick testing or when header modification isn’t possible, you can pass your key as a query parameter named token. 
https://api.benzinga.com/api/v2/news?token=<YOUR_API_KEY>

​
Code Examples

Here are production-ready examples for connecting to the Benzinga API in common languages. 
# Recommended: Header Authentication
curl -L 'https://api.benzinga.com/api/v2/news?pageSize=1' \
-H 'Authorization: token YOUR_API_KEY' \
-H 'Accept: application/json'

# Alternative: Query Parameter
curl -L 'https://api.benzinga.com/api/v2/news?pageSize=1&token=YOUR_API_KEY'

​
Troubleshooting

Common authentication errors and how to resolve them.
Status CodeMessagePossible CauseResolution
401UnauthorizedInvalid API KeyCheck that your API key is correct and has not been regenerated. ensure no extra spaces are copied.
401UnauthorizedMissing API KeyEnsure the Authorization header is formatted correctly as token <KEY> or the token parameter is present.
403ForbiddenInsufficient PermissionsYour API key is valid, but your plan does not include access to the requested endpoint. Contact sales or support to upgrade your plan.