configuration
Store User Configuration
Store (upsert) a named configuration for the authenticated user.
Request Parameters
- name (str): Name of the configuration. If a configuration with the same name already exists for this user, it is updated in place.
- config (dict): JSON-serializable configuration data to store (e.g. a KG schema, LLM settings, or ingestion parameters).
Response
Returns null on success (HTTP 200).
POST
Store User Configuration
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Name of the configuration to store. If a configuration with this name already exists for the user it is updated in place. Always provide a value: omitting it results in a server error.
Example:
"default_llm_settings"
The configuration data to store as a JSON object (e.g. a KG schema, LLM settings, or ingestion parameters). Always provide a value: omitting it results in a server error.
Example:
Response
Successful Response
Previous
Get User ConfigurationGet a stored configuration by its UUID.
## Path Parameters
- **config_id** (UUID): The "id" of a configuration previously returned by
GET /api/v1/configuration/get_user_configuration/.
## Response
Returns the stored configuration data as a JSON object. Returns an empty object {}
with HTTP 200 (not 404) when no configuration with that id exists.
Next
Store User Configuration