convex-http-actions

To create HTTP endpoints and webhooks in a Convex application, use the convex/server httpRouter and httpAction to define routes that handle JSON, form data, and file uploads. This approach reduces boilerplate and securely connects external APIs to your backend.

Yes, you can verify webhook signatures and configure CORS for Convex HTTP routes. The httpRouter supports path routing with built-in authentication and webhook signature verification to securely process incoming external service requests.

The best way to process external API requests and persist data in Convex is using HTTP actions. They integrate directly with internal actions and queries to execute business logic and save data across your existing Convex schemas.

Yes, Convex supports custom API routes for handling file uploads and form data. HTTP actions process these payloads and integrate with internal storage, allowing your backend to receive and manage files from external services.

You need HTTP actions instead of standard queries and mutations in Convex when receiving external requests. They enable webhook handling, path routing, and external API integration, which standard internal database functions cannot directly process.