> ## Documentation Index > Fetch the complete documentation index at: https://docs.fiddler.ai/llms.txt > Use this file to discover all available pages before exploring further. # Create a new configuration > Create a configuration for an organization, project, or model. Each setting can be created only once per scope; if it already exists, this endpoint returns `409 Conflict`. A setting can exist before you first create it: on deployments where stored values take effect, Fiddler copies any retention value set as an environment variable into an organization-level configuration at startup. To change an existing value, find its `id` with the list endpoint and use the update endpoint. `description`, `is_secret`, `is_system`, and `group_name` are filled in automatically. **Retention settings delete data.** For `PROD_EVENTS_TTL_DAYS` set on a `MODEL`, the new retention period is applied to that model's existing production events, and events older than the period are permanently deleted by background processes over the following hours. `PROD_EVENTS_TTL_DAYS` set on an `ORGANIZATION` or `PROJECT` applies only to models created afterward. The configuration is saved before the retention period is applied, so a successful response, or a `GET` that shows the value, confirms only that the configuration was saved, not that the retention period has been applied to stored data. If this request returns an error, the configuration may still have been saved: check with the list endpoint before retrying, and use the update endpoint if it exists. ## OpenAPI ````yaml POST /v3/configurations openapi: 3.0.3 info: title: Fiddler API - 2.0 description: APIs to interact with Fiddler termsOfService: https://fiddler.ai/about/terms contact: email: support@fiddler.ai license: name: Proprietary url: '2.0' version: '2.0' servers: [] security: - BearerAuth: [] tags: - name: access-key description: CRUD operations for API keys - name: agent-v3 description: CRUD for the Agent Registry (Stage 1, manual entries) - name: aggregation-invalidation-request-v3 description: Endpoints related to retrieving aggregation invalidation requests - name: alert-rules-v3 description: CRUD for Alert Rules, Summary, and Stats APIs - name: application-v3 - name: auth description: Authentication strategies and login flows - name: baseline-v3 description: CRUD for baseline - name: catalog-v3 description: >- Entity catalog provides paginated, searchable discovery of entity names (attribute keys, agent names, span types, span names, score names, evaluator config names) and their distinct values. Powered by ClickHouse materialized views — no worker or PostgreSQL dependency. - name: chart-annotation-v3 description: Endpoints related to retrieving chart annotations - name: chart-v3 description: CRUD for chart - name: queries-v3 description: v3 queries API - name: configuration-v3 description: > Read and change runtime configurations (Config Manager) for your organization, its projects, and its models. **Private preview.** These endpoints accept requests on every deployment. Whether a saved value takes effect depends on two deployment settings that are off by default: one makes Fiddler read stored values, and the other runs the configuration worker, which applies retention changes to stored data. Contact your Fiddler Customer Success Manager before using these endpoints. This reference documents the data retention (TTL) settings: `PROD_EVENTS_TTL_DAYS`, `GENAI_TRACES_TTL_DAYS`, and `GENAI_METRICS_TTL_DAYS`. The API accepts other registered settings too; contact your Fiddler Customer Success Manager before changing any of them. **Retention settings permanently delete data** once it is older than the configured period. When existing data is affected depends on the setting; see each setting's description. - name: cost-evaluators-v3 description: > Paginated roll-up of per-evaluator LLM cost and token usage, aggregated hourly. Available only on deployments with evaluator cost reporting enabled. - name: custom-metrics-v3 - name: dimensionality-reduction-v3 - name: environment-v3 description: Endpoints related to environment management - name: evals - name: datasets - name: evaluation-v3 - name: evaluator-v3 - name: rule-evaluators-v3 - name: experiment-v3 - name: explainability-v3 - name: llm_rca-v3 - name: file-upload description: Endpoints related to file uploading. - name: fql-expressions-v3 description: > Endpoints for listing FQL (Fiddler Query Language) functions available for GenAI custom metrics. Used by the frontend for autocomplete and signature hints in the FQL editor. - name: genai-alert-rules-v3 description: CRUD API for GenAI Alert Rules - name: genai-custom-metrics-v3 description: API for GenAI Custom Metrics - name: genai-filters-v3 description: API for GenAI Filters - name: genai-metrics-v3 description: >- Endpoints for pre-aggregated GenAI metrics. All metric data is pre-aggregated hourly by a Celery-based metric collector; no real-time aggregation is performed at request time. - name: guardrails-api description: Endpoints related to retrieving Guardrails specific data - name: ingestion-v3 - name: intercom-api description: Endpoints related to intercom APIs - name: jobs-v3 - name: llm-gateway-v3 - name: auth-login - name: auth-logout - name: mcp-client-setup-v3 description: Endpoints for retrieving MCP client setup instructions. - name: metrics-v3 description: Metrics endpoints - name: model-v3 - name: dashboard-v3 - name: model-deployment-v3 - name: monitoring-summary-v3 - name: histograms-v3 - name: organization-roles-v3 description: Update user org role - name: organization-settings-v3 description: Update organization settings such as timezone, email configuration, etc. - name: pagerduty-api description: CRUD for Pagerduty services. - name: project-v3 - name: project-roles-v3 description: Project role assignment management - name: scores-v3 description: Unified CRUD for scores and annotations - name: searchable-text-key-v3 description: >- Manage the global searchable text keys table that controls which OTel attribute keys are routed to the full-text-searchable `ValueContent` column in the unified attributes table. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: segments-v3 - name: semantic-mapping-v3 description: >- Manage the global semantic name mappings table that maps raw OTel attribute keys to canonical semantic concepts. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: server-info-v3 description: Endpoints related to retrieving server information - name: service-account description: > Service accounts and their API keys. A human Org Admin manages the service accounts of their own organization: create, read, update, and enable/disable (there is no delete — an account is disabled instead), and issue, rename, enable/disable, and revoke each account's API keys (a key's expiry is fixed at creation and changed only by rotating the key). An API key is an `fks_` secret that inherits the account's grants and cannot manage service accounts; an active, unexpired key must be disabled before it can be revoked, and it authenticates only while both it and its account are active. Scopes here are capability scopes (what the account may do), not OAuth scopes. - name: sessions-v3 description: v3 session APIs - name: span-v3 - name: team-roles-v3 - name: team-v3 - name: traces-v3 description: v3 trace api for monitoring - name: fetch-sessions-v3 description: v3 fetch sessions api for monitoring - name: user-access-key description: > CRUD operations for user API keys. All endpoints are user-scoped — each user can only operate on their own API keys. No one including Org admins have access to other users' API keys. - name: users-v3 - name: version-compatibility-v3 - name: webhooks externalDocs: url: https://docs.fiddler.ai description: Find out more about Fiddler paths: /v3/configurations: post: tags: - configuration-v3 summary: Create a new configuration description: > Create a configuration for an organization, project, or model. Each setting can be created only once per scope; if it already exists, this endpoint returns `409 Conflict`. A setting can exist before you first create it: on deployments where stored values take effect, Fiddler copies any retention value set as an environment variable into an organization-level configuration at startup. To change an existing value, find its `id` with the list endpoint and use the update endpoint. `description`, `is_secret`, `is_system`, and `group_name` are filled in automatically. **Retention settings delete data.** For `PROD_EVENTS_TTL_DAYS` set on a `MODEL`, the new retention period is applied to that model's existing production events, and events older than the period are permanently deleted by background processes over the following hours. `PROD_EVENTS_TTL_DAYS` set on an `ORGANIZATION` or `PROJECT` applies only to models created afterward. The configuration is saved before the retention period is applied, so a successful response, or a `GET` that shows the value, confirms only that the configuration was saved, not that the retention period has been applied to stored data. If this request returns an error, the configuration may still have been saved: check with the list endpoint before retrying, and use the update endpoint if it exists. operationId: addConfigurationV3 requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/AddConfigurationRequestBody' responses: '201': description: Configuration created successfully content: application/json: schema: allOf: - $ref: '#/components/schemas/ApiResponse' - type: object properties: data: $ref: '#/components/schemas/ConfigurationResponse' '400': $ref: '#/components/responses/400' '401': $ref: '#/components/responses/401' '403': $ref: '#/components/responses/403' '404': $ref: '#/components/responses/404' '409': $ref: '#/components/responses/409' '500': $ref: '#/components/responses/500' components: schemas: AddConfigurationRequestBody: type: object required: - name - source_name - source_id - value properties: name: $ref: '#/components/schemas/ConfigurationName' source_name: $ref: '#/components/schemas/ConfigurationSource' source_id: $ref: '#/components/schemas/ConfigurationSourceId' value: $ref: '#/components/schemas/ConfigurationValue' ApiResponse: type: object description: | Response object for standard API responses. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version. kind: type: string default: NORMAL enum: - NORMAL description: | Type of response, indicating a normal response. ConfigurationResponse: allOf: - type: object properties: id: type: string format: uuid description: Configuration UUID name: $ref: '#/components/schemas/ConfigurationName' source_name: $ref: '#/components/schemas/ConfigurationSource' source_id: $ref: '#/components/schemas/ConfigurationSourceId' value: $ref: '#/components/schemas/ConfigurationValue' description: type: string nullable: true description: Human-readable description of the configuration is_secret: type: boolean description: Whether the configuration value contains sensitive data is_system: type: boolean description: Whether this is a system configuration group_name: nullable: true allOf: - $ref: '#/components/schemas/ConfigurationGroup' description: Configuration group identifier organization: $ref: '#/components/schemas/OrganizationCompact' created_by: nullable: true allOf: - $ref: '#/components/schemas/UserCompact' updated_by: nullable: true allOf: - $ref: '#/components/schemas/UserCompact' required: - id - name - source_name - source_id - value - is_secret - is_system - organization - $ref: '#/components/schemas/CreateUpdateTimestamp' ConfigurationName: type: string description: > Name of the setting. The API accepts every registered setting. This reference documents the data retention settings below; contact your Fiddler Customer Success Manager before changing any other setting. - `PROD_EVENTS_TTL_DAYS`: retention period, in days, for ML model production events. Minimum 7. Can be set on an `ORGANIZATION`, `PROJECT`, or `MODEL`; the most specific scope wins. - `GENAI_TRACES_TTL_DAYS`: retention period, in days, for raw GenAI trace and span data. Minimum 7, unless your deployment sets a different minimum. `ORGANIZATION` scope only. - `GENAI_METRICS_TTL_DAYS`: retention period, in days, for pre-aggregated GenAI metrics. Minimum 60. `ORGANIZATION` scope only. ConfigurationSource: type: string description: Scope the configuration applies to. enum: - ORGANIZATION - PROJECT - MODEL - APPLICATION ConfigurationSourceId: type: string format: uuid description: >- UUID of the organization, project, model, or application the configuration applies to, matching `source_name`. For `ORGANIZATION`, this is your organization's UUID, not its name or numeric ID. ConfigurationValue: description: > Configuration value. The format depends on the configuration type (determined by the `name` field). The value must be one of: - **Boolean**: `true` or `false` (for BoolConfigValue) - **Integer**: `123` (for IntConfigValue) - **Float**: `123.45` (for FloatConfigValue) - **String**: `"string"` (for StringConfigValue) The actual type is determined by the configuration name and validated against the config registry. oneOf: - type: boolean - type: number - type: string ConfigurationGroup: type: string description: Group the setting belongs to, if any. Filled in automatically. OrganizationCompact: type: object title: OrganizationCompact description: > Compact version of an organization which can be included in the response of relevant APIs. required: - id - name properties: id: type: string format: uuid description: | Unique identifier of the organization. name: type: string description: | Name of the organization. UserCompact: type: object title: UserCompactV3 description: > Compact version of a user which can be included in the response of relevant APIs. required: - id - email properties: id: type: string format: uuid readOnly: true description: | Unique identifier for the user. full_name: type: string readOnly: true description: | Full name of the user. email: type: string format: email description: | Email address of the user. CreateUpdateTimestamp: type: object required: - created_at - updated_at properties: created_at: type: string format: date-time readOnly: true description: | Date and time when the object was created. updated_at: type: string format: date-time readOnly: true description: | Date and time when the object was last updated. ErrorResponse: type: object description: | Response object for errors returned by the API. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version of the response. kind: type: string default: ERROR enum: - ERROR description: | Type of response, usually indicating an error. error: type: object properties: code: type: integer format: int32 description: > Represents the code for this error, typically an HTTP response code. default: 400 enum: - 400 - 401 - 403 - 404 - 409 - 410 - 422 - 429 - 500 - 501 - 503 message: type: string description: > A human-readable message providing more details about the error. If there are multiple errors, it will be the message for the first error. example: Resource Not Found errors: type: array description: > Container for additional information regarding the error, especially for multiple errors. items: type: object properties: reason: type: string description: > Unique identifier for this error, different from the error code. example: ResourceNotFoundException message: type: string description: > A human-readable message providing more details about the error. If there is only one error, this field will match error.message. example: Resource Not Found help: type: string description: > Link to support or documentation providing more information on the error. responses: '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Conflict content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer ````