DocsIntegrations
Integrations
Small runnable apps that take a file through Videxo in the stack you already use, with the API key kept on your server.
Small apps that take a file through Videxo in the stack you already use. Each one does the same four things:
- Creates a job from JSON, from a per-operation endpoint and from
POST /v1/jobswith several outputs, with an idempotency key. - Receives the webhook and verifies its signature (Webhooks).
- Uploads a file straight from the browser with a one-time URL your server makes (Files).
- Downloads the outputs through a fresh signed link.
The API key and the webhook secret stay on your server, in environment variables. Errors arrive as problem details, and each app shows them. Every snippet on these pages comes from the example projects themselves, which are typechecked and tested, and each page links the whole project as a download.
| Stack | Shape | Webhook check |
|---|---|---|
| curl | Shell commands for every call | None: a shell cannot receive webhooks |
| Node with Express | Routes for jobs, uploads, downloads and the webhook | @videxo/sdk (npm) |
| React with Next.js | Route handlers and a client component that uploads | @videxo/sdk (npm) |
| SvelteKit | A form action, +server.ts endpoints and a page that uploads | @videxo/sdk (npm) |
| Python with FastAPI | Async routes with httpx | standardwebhooks (PyPI) |
| Go | net/http and the standard library | standard-webhooks Go library |
| PHP | One file per endpoint, with cURL | standard-webhooks/standard-webhooks (Composer) |
| Laravel | An Http service, a controller and a queued job | standard-webhooks/standard-webhooks (Composer) |
| Ruby on Rails | A Net::HTTP service, controllers and an Active Job | standardwebhooks (RubyGems) |
| iOS with Swift | The app gets an upload URL from your backend, uploads, and your backend creates the job | On your backend |
| Android with Kotlin | The same flow with OkHttp | On your backend |
The Express, Next.js and SvelteKit examples call the API with the TypeScript SDK,
@videxo/sdk, which also checks the webhook; the others call it with plain HTTP. For an iOS or macOS
app that holds a client token, see the Swift SDK.