> ## Documentation Index > Fetch the complete documentation index at: https://docs.crustdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Delete an entity watch > Cancels the watch and deletes its schedule. Returns `204` with no body, and `204` again if the watch was already cancelled. Deletion is terminal: the watch cannot be resumed. ## OpenAPI ````yaml /openapi-specs/2025-11-01/watch.yaml delete /watch/{dataset}/{watch_id} openapi: 3.0.3 info: title: Watch API version: '2025-11-01' description: > The Watch API turns a Crustdata query into a recurring feed. A watch runs on your schedule and delivers only what is new or what changed since its previous run, to a webhook, Slack, Google Chat, or email. There are two kinds of watch, and the kind decides the URL: - **Discovery watches** (`/watch/{dataset}/search`) re-run a *search filter* and deliver records that newly match it. Use one to find people, companies, or jobs you do not know yet. Available for `person`, `company`, and `job`. - **Entity watches** (`/watch/{dataset}`) monitor a *list you supply* and deliver a notification when a tracked field on one of those records changes. Use one to follow a known set. Available for `person` and `company`. Both kinds share the same `config`, `notifications`, and run-history surfaces, and both start with a free baseline run: a discovery watch delivers a sample of up to 5 current matches, an entity watch records each subject's starting values and never fires. Every request needs an `Authorization` Bearer API key and the `x-api-version: 2025-11-01` header. **Credits.** A discovery watch is charged per new record delivered: 0.5 for a person, 2 for a company, 0.5 for a job. An entity watch is charged per notification, tiered by `config.refresh_frequency_days`: 5 credits at the 30-day default, 10 at 14 days, 20 at 7 days, 50 at 3 days, 150 at 1 day. A run that finds nothing costs nothing, and the baseline run is free for both kinds. **Rate limit.** Watch-management requests are limited to 10 requests per minute per API key. **Access.** Creating a watch is open to any authenticated API customer, and the 10-requests-per-minute limit is what bounds abuse. What is gated is the data underneath: a create is rejected with `403` when the key is not entitled to the dataset, or when `fields` or `track` name field groups the key may not receive. Contact info@crustdata.com to request access. servers: - url: https://api.crustdata.com description: Production API server security: - bearerAuth: [] tags: - name: Watch APIs description: Recurring feeds over the Crustdata datasets - name: Discovery Watches description: Watches that re-run a search filter and deliver newly matching records - name: Entity Watches description: >- Watches that monitor a supplied list of people or companies for field changes - name: Watch Runs description: Run history and per-run delivery detail, shared by both watch kinds paths: /watch/{dataset}/{watch_id}: delete: tags: - Watch APIs - Entity Watches summary: Delete an entity watch description: > Cancels the watch and deletes its schedule. Returns `204` with no body, and `204` again if the watch was already cancelled. Deletion is terminal: the watch cannot be resumed. operationId: cancelEntityWatch parameters: - $ref: '#/components/parameters/EntityDatasetPath' - $ref: '#/components/parameters/WatchId' - $ref: '#/components/parameters/ApiVersion' responses: '204': description: The watch is deleted. No body is returned. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/WatchForbidden' '404': $ref: '#/components/responses/WatchNotFound' '429': $ref: '#/components/responses/RateLimited' components: parameters: EntityDatasetPath: name: dataset in: path required: true description: > The dataset the watch is built on. Entity watches support `person` and `company`; there is no job entity watch, and `job` returns `404` here. Use `/watch/job/search` for jobs. schema: type: string enum: - person - company example: person WatchId: name: watch_id in: path required: true description: The watch's `id`, returned when it was created. schema: type: integer example: 46936 ApiVersion: name: x-api-version in: header required: true schema: type: string enum: - '2025-11-01' default: '2025-11-01' example: '2025-11-01' description: > API version to use. `2025-11-01` is the only accepted value. Send it on every call: it is enforced today on `POST /watch/{dataset}/search`, where a missing or unrecognized value returns `400`, and the other watch routes accept a request without it rather than relying on that. responses: Unauthorized: description: The API key is missing or not valid. content: application/json: schema: $ref: '#/components/schemas/AuthErrorResponse' examples: invalid_api_key: summary: Bearer token present but not a valid key value: message: Invalid API key in request missing_api_key: summary: No Authorization header at all value: message: Missing API key in request WatchForbidden: description: > The key is not entitled to this dataset, or to a field group the request names. The watch surface itself is open to any authenticated API customer. content: application/json: schema: $ref: '#/components/schemas/SimpleErrorResponse' example: error: >- You do not have access to the person dataset. Contact info@crustdata.com to request access. WatchNotFound: description: No watch with that id belongs to this key on this dataset. content: application/json: schema: $ref: '#/components/schemas/SimpleErrorResponse' example: error: Watch not found RateLimited: description: > Too many watch requests. The per-endpoint limit is 10 requests per minute per API key, which is what bounds bursty create and update loops. Steady use is unaffected. content: application/json: schema: $ref: '#/components/schemas/StructuredErrorResponse' example: error: type: rate_limit_error message: >- Rate limit exceeded for this endpoint. Please write to gtm@crustdata.co. metadata: [] schemas: AuthErrorResponse: type: object description: > Authentication error payload. The message distinguishes the two failures: `Missing API key in request` when no `Authorization` header was sent, and `Invalid API key in request` when the Bearer token is not a valid key. required: - message example: message: Invalid API key in request properties: message: type: string description: Human-readable authentication error message. example: Invalid API key in request SimpleErrorResponse: type: object description: Error payload with a single human-readable message. required: - error example: error: Watch not found properties: error: type: string description: Human-readable description of what went wrong. example: Watch not found StructuredErrorResponse: type: object description: >- Structured error payload, used for rate-limit and API-version failures. The flatter `SimpleErrorResponse` shape is used elsewhere, so parse defensively. required: - error example: error: type: rate_limit_error message: >- Rate limit exceeded for this endpoint. Please write to gtm@crustdata.co. metadata: [] properties: error: type: object required: - type - message properties: type: type: string description: Machine-readable error type identifier. example: rate_limit_error message: type: string description: Human-readable description of what went wrong. example: >- Rate limit exceeded for this endpoint. Please write to gtm@crustdata.co. metadata: type: array description: Extra context, empty on most errors. items: type: object additionalProperties: true example: [] securitySchemes: bearerAuth: type: http scheme: bearer description: API key passed as a Bearer token in the Authorization header. ```` ## Related topics - [Company Entity Watcher](/watcher-docs/company/entity.md) - [Person Entity Watcher](/watcher-docs/person/entity.md) - [Update an entity watch](/api-reference/watch-apis/edit-the-watched-list-pause-or-reconfigure-an-entity-watch.md) - [List entity watches](/api-reference/watch-apis/list-your-entity-watches.md) - [Get an entity watch](/api-reference/watch-apis/get-one-entity-watch.md)