> ## Documentation Index
> Fetch the complete documentation index at: https://developer.zeeg.me/llms.txt
> Use this file to discover all available pages before exploring further.
# Delete a Routing Form
> Delete a routing form by ID via the Zeeg API, removing its questions, its routes and every submission it holds. This cannot be undone.
Deletes one routing form with its questions, its routes and every submission that it holds.
This endpoint requires the `routing_forms:write` scope. A token that carries `routing_forms:read` alone answers `403`.
This action is irreversible. Read the submissions with [List Routing Form Submissions](/api/routing-forms/list-routing-form-submissions) before you delete the routing form. The delete takes the submission history with it.
The public address of the routing form stops resolving as soon as the delete lands. An invitee who opens a saved link reaches nothing.
The id is a UUID. A malformed id answers `404`, not `422`. A routing form outside your workspace answers `404` as well.
## OpenAPI
````yaml DELETE /routing-forms/{id}
openapi: 3.0.0
info:
title: Zeeg Public API
description: >-
Zeeg public API documentation.
## Authentication
All endpoints require a Bearer token. You can generate an API token from
[your Zeeg dashboard](https://app.zeeg.me/account/settings/api-access).
Each token is scoped to specific permissions (e.g. `events:read`,
`webhooks:write`). Make sure your token has the required scopes for the
endpoints you want to use.
## Recommended Headers
We recommend including the `Accept: application/json` header in all API
requests to ensure you receive JSON responses.
version: 2.0.0
x-logo:
url: https://app.zeeg.me/img/logo-dark.2ca83593.svg
backgroundColor: '#f7f7f9'
altText: zeeg
contact:
name: Zeeg Support
email: support@zeeg.me
url: https://zeeg.me/en/contact
license:
name: Proprietary
url: https://zeeg.me/en/legal/terms
termsOfService: https://zeeg.me/en/legal/terms
servers:
- url: https://api.zeeg.me/v2
description: Production
security:
- bearer: []
tags:
- name: Scheduled Events
description: Management of events scheduled via Zeeg
- name: Scheduling Pages
description: Scheduling pages information and management
- name: Availability Schedule
description: Read and change availability for users
- name: Webhooks
description: Webhooks management
- name: Notes
description: Notes for scheduled events
- name: Workspaces & Teams
description: Workspace users and team member management
- name: AI Agent
description: AI Agent integration endpoints
- name: Payloads
description: Webhook payload schemas
- name: CRM - Objects
description: >-
Discover the schema of CRM objects (standard and custom) including all
attribute definitions
- name: CRM - Companies
description: Create, read, update, and delete CRM company records
- name: CRM - People
description: Create, read, update, and delete CRM person records
- name: Routing Forms - Forms
description: Read routing forms with their questions and their routes
- name: Routing Forms - Submissions
description: Read and delete the submissions that invitees send through a routing form
paths:
/routing-forms/{id}:
delete:
tags:
- Routing Forms - Forms
summary: Delete a routing form
description: >-
Deletes one routing form with its questions, its routes and every
submission that it holds.
**This action is irreversible.** Read the submissions with `GET
/routing-form-submissions?routingFormId={id}` before you delete the
routing form. The public address of the routing form stops resolving as
soon as the delete lands.
A routing form outside your workspace answers 404, so the response never
tells you that the routing form exists. An id that is not a UUID answers
404 as well.
**Required scope:** `routing_forms:write`
operationId: delete-routing-form
parameters:
- name: id
in: path
required: true
schema:
type: string
format: uuid
description: UUID of the routing form to delete.
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
status:
type: integer
example: 200
message:
type: string
example: Routing form deleted.
'401':
$ref: '#/components/responses/401'
'403':
description: >-
Forbidden — the token misses the scope, or the user may not delete
this routing form
content:
application/json:
schema:
oneOf:
- type: object
properties:
error:
type: object
properties:
type:
type: string
message:
type: string
error_id:
type: string
required_scopes:
type: array
items:
type: string
- type: object
properties:
success:
type: boolean
message:
type: string
status:
type: integer
examples:
Missing scope:
value:
error:
type: insufficient_scope
message: >-
Your token is missing the required scope:
routing_forms:write.
error_id: 9b3c5e71-4d28-4f6a-b0c9-3e7a1d5f8c20
required_scopes:
- routing_forms:write
No permission:
value:
success: false
message: You don't have permission to delete this routing form.
status: 403
'404':
description: Not Found
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
message:
type: string
status:
type: integer
examples:
Not found:
value:
success: false
message: Data Not Found
status: 404
security:
- bearer: []
components:
responses:
'401':
description: Unauthorized
content:
application/json:
schema:
type: object
properties:
message:
type: string
example: Unauthenticated.
examples:
Unauthenticated:
value:
message: Unauthenticated.
securitySchemes:
bearer:
type: http
scheme: bearer
description: ''
````