tylerkohn
CCConvex Community
•Created by tylerkohn on 4/7/2023 in #support-community
Http endpoints for client sdks using api keys vs auth tokens (e.g. clerk)
Hi. We want to allow users to use an sdk (python or typescript) to interact with our convex actions. The provided clients don't seem to work since they require an auth token/configuration that is generally managed by our core auth provider (clerk in our case).
We'd like to set an http header with an api key that is used by our convex code to authenticate and authorize the request. http endpoints do seem to work for this. We've created them, can set a header, and validate that within the http endpoint. This is great, however we do need to then manually create a client that understands the request and response objects. Is there either: 1. a way to automatically generate client (like with openapi) 2. a way to use the provided clients with an api key that is managed within convex (btw, I wish clerk had support for api keys!) Thanks!
We'd like to set an http header with an api key that is used by our convex code to authenticate and authorize the request. http endpoints do seem to work for this. We've created them, can set a header, and validate that within the http endpoint. This is great, however we do need to then manually create a client that understands the request and response objects. Is there either: 1. a way to automatically generate client (like with openapi) 2. a way to use the provided clients with an api key that is managed within convex (btw, I wish clerk had support for api keys!) Thanks!
12 replies