Skip to main content
Do not expose a secret API key in browser JavaScript or a mobile binary. Send requests from your server and apply user-level authorization there.
Use a secret manager or server-side environment variable. For local tools, use their encrypted credential store or a user-level configuration excluded from version control.
Delete the key immediately under Console > API Keys, create a new one, update the affected environments, and review request logs for unexpected use.
Prefer separate development, staging, production, and tool-specific keys. This limits blast radius and makes usage attribution easier.
Every webhook needs a webhook_secret of 16 to 256 characters. Verify the X-Gateway-Webhook-Signature header over the raw request body, reject timestamps more than five minutes old, and deduplicate deliveries on the event id.
No. Public http or https URLs must use a public hostname. Private, loopback, local, credentialed, and reserved destinations are rejected. GPT Image 2.5 Ext also accepts PNG, JPEG, or WebP Data URLs in image_urls. Video references remain public URLs only.