> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Source

> Delete a single source by its slug.

Deletes the source identified by `slug`. The identifier is the pipeline **slug**, not the source ID — the same value used by [Get Source](/platform-api/sources/details) and [Update Source](/platform-api/sources/update).

A successful call returns `204 No Content` with an empty body.

## Example

```bash theme={null}
curl --request DELETE \
  --url https://api.nekt.ai/api/v1/sources/facebook-ads/ \
  --header "x-api-key: YOUR_API_KEY"
```

<Warning>
  There is no undelete endpoint — deleting a source cannot be reversed through the Platform API. Double-check the slug before sending the request.
</Warning>

## Authentication

This endpoint requires an [API key](/platform-api/introduction#create-an-api-key) in the `x-api-key` header. MCP tokens cannot delete resources and are rejected with `403 Forbidden`.

## Related

* [Bulk Delete Sources](/platform-api/sources/bulk-delete) — remove several sources in a single request.
* [List Sources](/platform-api/sources/list) — find the slug you want to delete.


## OpenAPI

````yaml DELETE /api/v1/sources/{slug}/
openapi: 3.0.3
info:
  title: Nekt API
  version: v1
  description: Nekt API Documentation
  contact:
    email: support@nekt.ai
servers:
  - url: https://api.nekt.ai
security: []
paths:
  /api/v1/sources/{slug}/:
    delete:
      tags:
        - v1
      description: >-
        Opt-in visibility of soft-deleted rows on the ``list`` action, for
        admins/owners only.


        Views combine ``include_deleted_requested()`` with their own
        ``get_manager()`` to start the

        list queryset from ``all_objects`` when the caller passes
        ``?include_deleted=true``. The opt-in

        is intentionally scoped to ``list`` — update/trigger/destroy keep using
        the default (deleted-

        excluding) manager, so they can never operate on a soft-deleted
        resource.


        Only Owners/Admins may see deleted items; a non-admin caller (including
        token principals with

        ``role=None``, e.g. scoped MCP tokens) asking for them gets a 403.
      operationId: v1_sources_destroy
      parameters:
        - in: path
          name: slug
          schema:
            type: string
          required: true
      responses:
        '204':
          description: No response body
      security:
        - ApiKeyAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: 'API Key authentication. Format: ''x-api-key: api_key'''

````