API Reference
The QSC REST API lets you manage your search app programmatically. All endpoints share the same base URL.
Schema and feeding use the admin and feeding tokens; the Chat API (via the Agent Server) uses the agent token. All three are documented in Authentication.
Base URL
https://qsc.quasiris.de
Authentication
Pass your API token via the X-QSC-Token header on every request:
X-QSC-Token: <your-token>
Three tokens share the X-QSC-Token header — use the one that matches the endpoint:
| Token | Used for |
|---|---|
| Admin token | Schema updates (/api/v1/searchapp/*) |
| Feeding token | Data operations and scheduling (/api/v1/data/*, /api/v1/job/*) |
| Agent token | Agent Chat (/api/v1/agent/chat/*) — agent-server AUTH_TOKEN |
Admin and feeding tokens are managed under Security in the QSC Admin UI. See Authentication for details.
Quickstart with Postman
The fastest way to get started — import the collection and an environment, fill in your credentials, then run through the numbered folders in order.
| Environment | Download |
|---|---|
| Production | qsc-prod.postman_environment.json |
| Development | qsc-dev.postman_environment.json |
In Postman: File → Import the collection and the environment file, then select the environment and set:
| Variable | Used for |
|---|---|
tenant, code | Search app (folders 1–3) |
token, feedingToken | Admin and feeding tokens |
chatTenant, chatCode, chatToken | Agent config and agent-server token (folder 4) |
APIs
| API | Description |
|---|---|
| Search App Schema | Define the field schema of your search app |
| Feeding | Push documents into the index |
| Search | Execute searches, suggestions, and navigation |
| Chat | Send chat messages to a QSC Agent, streamed or non-streamed |