> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/data-sources/delete-a-data-source.md).

# Delete a data source

Deletes a data source.

This is a hard delete: the record is removed. To take a seller out of use without removing it, set `is_active` to `false` with an update instead.

```json
{"openapi":"3.1.0","info":{"title":"Admin API","version":"1.0.0"},"tags":[{"name":"Data Sources","description":"Administrative endpoints for **data sources** — the sellers / suppliers behind the catalog. A data source carries the commercial and legal identity of a seller (a display `name`, a unique `supplier_code`, and contact details) and binds that seller to the price list and stock list it sells under. On a marketplace, each seller is a data source; a single-seller store typically has one.\n\n## Core Capabilities\n\n**1. Listing & Filtering**\n* Retrieve a paginated list of data sources.\n* Filter by `supplier_code` (case-insensitive exact match).\n* Order results with the `sort` parameter, as described under **Filtering & Ordering**.\n\n**2. Full CRUD**\n* Create a data source with its identity, contact details, and price / stock list bindings.\n* Retrieve a single data source.\n* Fully or partially update a data source.\n* Delete a data source. `DELETE` is a **hard delete** — the record is removed.\n\n> **Deactivating a data source has a side effect.** Setting `is_active` to `false` on an update removes every basket item on the storefront that references this data source. Deactivation is not the same as deletion: the record itself is kept and can be reactivated later.\n\n## Data Source Fields\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `pk` | integer | The unique identifier of the data source. Read-only; supplying it in a request body has no effect. |\n| `name` | string | The seller's display name. Required on create and full update. Up to 64 characters and unique across all data sources. |\n| `slug` | string | A URL-safe identifier. Optional and unique when given; up to 64 characters. |\n| `title` | string | The seller's full / legal name. Optional; up to 255 characters. |\n| `supplier_code` | string | The seller's unique business code. Required on create and full update. Up to 50 characters and unique across all data sources. |\n| `address` | string | Postal address. Optional. |\n| `email` | string | Contact e-mail address. Optional; must be a valid e-mail when given. |\n| `phone_number` | string | Contact phone number. Optional; up to 128 characters. |\n| `fax_number` | string | Fax number. Optional; up to 128 characters. |\n| `kep_address` | string | Registered electronic-mail (KEP) address. Optional; must be a valid e-mail when given. |\n| `mersis_number` | string | Central Registry (MERSIS) number. Optional; up to 16 characters. |\n| `trade_association` | string | Trade association / chamber the seller belongs to. Optional; up to 255 characters. |\n| `extras` | object | Free-form JSON for extra, integration-specific data. Optional; defaults to an empty object. |\n| `price_list` | integer | The identifier of the price list supplying this seller's prices. Optional; may be `null`. |\n| `stock_list` | integer | The identifier of the stock list supplying this seller's stock. Optional; may be `null`. |\n| `is_active` | boolean | Whether the data source is active. Defaults to `true` on create. See the deactivation side effect above. |\n\n## Filtering & Ordering\n\nThe list endpoint accepts a single filter, `supplier_code`, matched case-insensitively against the whole value. Query parameters that are not listed are ignored rather than rejected. Results can be ordered with the `sort` parameter on the data source's fields; prefix a field with a hyphen for descending order and separate several fields with commas.\n\n## Dynamic Settings & Environment Variables\n\nNo dynamic settings (`dj_dynamic_settings`) and no environment variables are read by these endpoints. Their behavior does not change with the management-panel or deployment configuration."}],"servers":[{"description":"Omnitron Remote Proxy (external access — recommended)","url":"https://{omnitron_url}/api/v1/remote/{channel_id}","variables":{"omnitron_url":{"default":"sandbox.akinon.com","description":"Omnitron server URL (e.g., {omnitron.akinon.com})"},"channel_id":{"default":"1","description":"The channel identifier the remote request is routed through"}}},{"description":"Commerce API Server (internal / direct access only)","url":"https://{commerce_url}/api/v1","variables":{"commerce_url":{"default":"sandbox.akinon.com","description":"Internal commerce server URL, reachable only from within the Omnitron network"}}}],"security":[{"tokenAuth":[]}],"components":{"securitySchemes":{"tokenAuth":{"type":"apiKey","in":"header","name":"Authorization","description":"Token credential sent in the Authorization header, in the form: `Token <your-token>`. Requires a staff (admin) account."}},"responses":{"Unauthorized":{"description":"Authentication credentials were not provided or are invalid.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"Forbidden":{"description":"The authenticated user does not have administrator privileges.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"DataSourceNotFound":{"description":"No data source exists with the given identifier.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"schemas":{"Error":{"type":"object","description":"An error response.","properties":{"detail":{"type":"string","description":"A human-readable description of the error."}},"additionalProperties":true}}},"paths":{"/data_sources/{id}/":{"delete":{"tags":["Data Sources"],"operationId":"deleteDataSource","summary":"Delete a data source","description":"Deletes a data source.\n\nThis is a hard delete: the record is removed. To take a seller out of use without removing it, set `is_active` to `false` with an update instead.","responses":{"204":{"description":"The data source was deleted successfully. No response body."},"401":{"$ref":"#/components/responses/Unauthorized"},"403":{"$ref":"#/components/responses/Forbidden"},"404":{"$ref":"#/components/responses/DataSourceNotFound"}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apidocs.akinon.com/commerce-openapis/admin/data-sources/delete-a-data-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
