Configuration
Per-tenant configuration for persona, model strategy, feature flags, RAG, agentic mode, rate limits, and data retention.
Tenant configuration is stored as structured JSON across several config blocks. All config is updated via PATCH /dashboard/account/config.
PATCH https://api.liyaengine.ai/dashboard/account/config
Authorization: Bearer <dashboard_jwt>
Content-Type: application/json
{
"personaConfig": { ... },
"featureConfig": { ... },
"modelConfig": { ... }
}You can update one or more blocks in a single request. Omitted blocks are left unchanged.
Config blocks
| Block | What it controls |
|---|---|
| personaConfig | AI name, tone, formality, disclaimers, language |
| modelConfig | Model strategy, per-intent overrides, cost limits |
| featureConfig | Feature flags — RAG, agentic mode, streaming, employer features |
RAG chunking, embedding model, and retrieval behaviour are not part of this endpoint — they're set per knowledge collection via PATCH /dashboard/collections/:id. See RAG Configuration.
Data retention periods (session, message, audit log, etc.) are platform defaults today, not per-tenant settable — the only writable field in this area is piiProtection (a top-level boolean, not a dataRetentionConfig block). See Data Retention.
Reading current config
GET /dashboard/account
Authorization: Bearer <dashboard_jwt>The response includes config.personaConfig, config.featureConfig, config.modelConfig, and config.piiProtection (a derived boolean — see Data Retention).