Authentication & keys

Use Authorization: Bearer YOUR_VEZAPI_KEY for model requests. Your VezAPI account session is used only for dashboard operations. Never put a secret API key in public frontend code.

Create up to 20 active keys per account. A new key is displayed once; only a keyed hash is retained. Revocation prevents future requests but does not cancel previously accepted tasks.

Task and file ownership

Query, edit and extension operations require a task belonging to the same account. Media links are signed and expire. Keep the full signed URL private.