> 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/oms/demo-data-service.md).

# Demo Data Service

All services related to Demo Data are listed in this page.

### `POST` Load Data

This service is used to load demo data into OMS. When you run this service, it will execute a Django command to load fixture data to OMS.

**Path:** `/api/v1/oms/demo/load-data/`

**Example Request**

To run this service, a `POST` request should be sent to the `/api/v1/oms/demo/load-data/` endpoint. No payload is required. In the headers, set the `Authorization` header to include the token for authentication.

Here's an example of how to make the request in python:

```python
import requests
import json
url = "https://{domain_url}/api/v1/oms/demo/load-data/"
token = "11111XXXXXXXXXXXXXXXXX201XXXXX9332d"

headers = {
    'Content-Type': 'application/json',
    'Authorization': f'Token {token}'
}

response = requests.request('POST', url, headers=headers)
print(response.json())
```

**Example Response (200 OK)**

This service returns a successful response with a status code of `200 OK`. The response body does not contain any objects or messages.

**Example Response (401 Unauthorized)**

If the authorization token is missing or incorrect in the request headers, the service will return a response with status code of `401 Unauthorized`. The response body does not contain any objects or messages.


---

# 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/oms/demo-data-service.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.
