> For the complete documentation index, see [llms.txt](https://piramal-swasthya.gitbook.io/uba/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piramal-swasthya.gitbook.io/uba/toasters/provider-toaster/developer-guide/backend-guide/strapi-provider.md).

# Strapi Provider

The UBI Strapi Provider is a content management system (CMS)

The UBI Strapi Provider is a content management system (CMS) that manages benefit programs and their related information. It provides an admin interface to create and manage benefits, and an API to access this information.

### Project Specifications

* **Framework**: Strapi v5.12.6
* **Language**: TypeScript enabled
* **Database**: PostgreSQL
* **Node Version**: 18.x
* **Package Manager**: npm >=6.0.0

### Core Features

#### 1. Content Management

* Admin interface for benefit management
* Custom collections support
* TypeScript-based development
* PostgreSQL data persistence

#### 2. Content Types

**Benefit**

* Basic program information
* Eligibility rules
* Application forms
* Program timelines

**Components**

* Address information
* Contact details
* Document requirements
* Benefit details

#### 3. API Features

* REST API endpoints
* API documentation
* User authentication
* Data filtering and population support (`?populate=*`)

### System Components

1. **Admin Panel**
   * Web interface for content management
   * User management
   * API token generation
   * Custom collection management
2. **Database**
   * PostgreSQL database
   * Stores all content
   * Handles relationships
   * No SSL by default

### Security

* JWT authentication
* Role-based access
* API token management
* Input validation

### Additional Resources

* [Official Strapi Docs](https://docs.strapi.io/cms/quick-start)

<br>


---

# 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://piramal-swasthya.gitbook.io/uba/toasters/provider-toaster/developer-guide/backend-guide/strapi-provider.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.