> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/use-cqube/ingesting-the-data/steps-to-ingest-data-files/api-to-upload-starter-pack-data-files-for-nvsk-programs.md).

# API to upload starter pack data files for NVSK programs

This focuses on ingestion of programs like UDISE, PGI, NISHTHA, DIKSHA, NAS, PM-POSHAN. The jwt token has to be passed in the API headers.

**Note:** There could be some common errors in the files which could lead to unsuccessful data ingestion into cQube. Look at these errors here and resolve them before ingesting data into cQube.

The already existing files will need to be ingested into cQube via the following process:

This API accepts the data in a zip file format and adds it to the emission folder in the respective cloud storage / SDC.

<br>

&#x20;**National Programs API:**

### Step 1: &#x20;

Open the specified request & add the details

**API Endpoint:** \<domain\_name>/api/ingestion/national\_programs

**HTTP Method:** GET&#x20;

<figure><img src="https://lh4.googleusercontent.com/FxBb2naDMzrSwyVBQqO-icyzVjsZXAOUwAJS4_iZQUAEOG8d4eaASjtmHjXsDydBgFc6MzzXzWZjIu6kr20Sb7rakoanaIN609omZPk28cIgDFl43xQxaWpWZ7JbcGD0VCvuF2Qb9e22DQucpueddRY" alt=""><figcaption></figcaption></figure>

### Step 2:&#x20;

Send the query parameters with reference to the YAML file. The query parameters for the above api is attached in  Link for yaml:  [ ](https://github.com/Sunbird-cQube/spec-ms/blob/dev/spec.yaml)[<img src="https://lh6.googleusercontent.com/vz1PVdRSVzygs-DlegHLT1KDUWzJ5y6WDQD3V5CE-Szl9udxKtyL3yuPSqPy3tpkwN2UbYDE43uFQV-qzU1yjCeV6ESNlJD5xkmTSZds-4yEy3NWIt10Fs-D3UfRV6IZg-mNQD-HBg78jlreb_eY_q8" alt="" data-size="line">](https://github.com/Sunbird-cQube/spec-ms/blob/dev/spec.yaml)[spec-ms/spec.yaml at dev · Sunbird-cQube/spec-ms](https://github.com/Sunbird-cQube/spec-ms/blob/dev/spec.yaml)

Provide the valid input details for the parameters shown below.

<figure><img src="https://lh5.googleusercontent.com/dYFL3X-Vkq1W9HHJv2XInIso2b5nofh7yaHVDzWjJkHUKbwgIe8EIBtpJP1uzkaDHe0mT9ceX2m3yiCWn7r6CWbdA4lIBMwUpXM2AVcq26GOJWdExaXPsHb5UsBSeEvzHgvjPFKp4NEfcbzNebzSBxA" alt=""><figcaption></figcaption></figure>

### Step 3:&#x20;

Click on the send button for the request and if the request is successful the user should see a response message which contains the status of the file.

<figure><img src="https://lh4.googleusercontent.com/ZYvquzK3X_OlYqpX6LucWKlOywN07ulIUh7qvxGUAzi2H9KAZiPXkgCv7PIgEMCHr_tiPLMKY1UmBRse3ug75SCkKKlJJ3IgSXDxc6XmXPYvG1SMcyoB1Uvu9kAAvf0QNaqwgUJxUlzwcQ4qLyG7lGU" alt=""><figcaption></figcaption></figure>


---

# 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://cqube.sunbird.org/use-cqube/ingesting-the-data/steps-to-ingest-data-files/api-to-upload-starter-pack-data-files-for-nvsk-programs.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.