convex-http-actions

To create HTTP endpoints in Convex, define GET or POST routes with path and method matching that connect directly to Convex actions. This setup allows your application to receive external webhook callbacks and securely execute business logic.

Yes, Convex HTTP actions support integrations with services like Stripe, GitHub, and Clerk. You can process their third-party webhook callbacks to verify signatures and trigger mutations and queries to drive Convex data changes.

The best way to enforce authentication and CORS on custom API routes in Convex is by applying API keys, Bearer tokens, and configuring CORS headers for browser clients directly within your HTTP action logic.

Webhook signature verification with Convex actions works by processing incoming payloads to validate signatures before triggering mutations and queries. This ensures only authentic external requests drive data changes inside your Convex application.

Yes, if you need to route external API calls to your queries, you need Convex HTTP actions. They act as the necessary entry point to receive webhooks, route requests, and connect external services with your internal Convex actions.