# Generate a test webhook Generates a test Webhook. > Important: This operation uses server https://brandfolder.com/api/v1 (notice the version is v1). > Important: Ensure that your code is able to receive a Brandfolder Webhook using this endpoint before creating a production Webhook subscription. If you receive a 202 response at this endpoint, then a fake Webhook notification will POST to your callback_url. If you don't receive anything at your callback_url within a few minutes, it is likely that callback_url is invalid. Please ensure the URL begins with https:// and that it is a public domain (not localhost, behind a firewall, or any other domain requiring authentication) which can receive HTTP POST requests and respond with a 2xx HTTP status code. Endpoint: POST /webhooks/send Version: v4 Security: APIToken ## Header parameters: - `Content-Type` (string, required) Enum: "application/json" - `Authorization` (string, required) Bearer token for authentication ## Request fields (application/json): - `data` (object, required) - `data.attributes` (object, required) - `data.attributes.event_type` (string, required) Event type. Enum: "asset.create", "asset.update", "asset.delete" - `data.attributes.resource_key` (string, required) Brandfolder ID. Example: "oqgiju-21olts-ce9egi" - `data.attributes.resource_type` (string, required) The type of resource the event acts on. Currently, brandfolder is the only supported type. Enum: "brandfolder" - `data.attributes.callback_url` (string, required) An HTTPS URL where webhook data will be posted. Please ensure the URL begins with https:// and that it is a public domain (not localhost, behind a firewall, or any other domain requiring authentication) which can receive HTTP POST requests and respond with a 2xx HTTP status code. Example: "https://your_company.com/your_callback_url" - `data.attributes.asset_key` (string) Asset ID override Example: "oqgkkd-fr5iv4-443db" - `data.attributes.organization_key` (string) organization ID override. Example: "oqgkkd-fr5iv4-cocc75" ## Response 202 fields (application/json): - `message` (string) - `status` (string) ## Response 400 fields ## Response 403 fields ## Response 404 fields ## Response 409 fields