You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current reliance on Bearer-Token for API authentication can be restrictive for environments where managing headers is less practical. Some users may find it easier to pass authentication details as part of the query or request body, especially in certain automated or legacy systems.
Describe the solution you'd like
Implement a secret_key parameter that can be used as an alternative authentication method. This parameter would allow users to authenticate their API requests by appending secret_key=[USER_SECRET_KEY] to the query parameters, offering flexibility for different integration scenarios.
justinh-rahb
changed the title
Introduce secret_key Parameter for Authentication as an Alternative to Bearer Token
[Feature Request] Introduce secret_key Parameter for Authentication
Jan 24, 2024
Is your feature request related to a problem? Please describe.
The current reliance on Bearer-Token for API authentication can be restrictive for environments where managing headers is less practical. Some users may find it easier to pass authentication details as part of the query or request body, especially in certain automated or legacy systems.
Describe the solution you'd like
Implement a
secret_key
parameter that can be used as an alternative authentication method. This parameter would allow users to authenticate their API requests by appendingsecret_key=[USER_SECRET_KEY]
to the query parameters, offering flexibility for different integration scenarios.References
https://github.com/apilayer/screenshotlayer-API/blob/master/docs/specifications.md
The text was updated successfully, but these errors were encountered: