> ## Documentation Index
> Fetch the complete documentation index at: https://finance.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Setting

> Creates a new setting for a specific category with dynamic key-value pairs. This endpoint allows authenticated users to create configuration settings organized by category. Each setting consists of a key and value pair that can be used to store application configuration.



## OpenAPI

````yaml https://spec.speakeasy.com/aries/aries/aries-trading-platform-api-with-code-samples post /v1/config/{category}/settings
openapi: 3.0.3
info:
  title: Aries Trading Platform API
  description: >-
    Complete API documentation for the Aries trading platform including user
    management, authentication, account management, order management, market
    data, and analytics
  contact:
    name: Aries Financial
    email: dev@aries.com
  version: 1.0.0
servers:
  - url: https://api.tradearies.dev
    description: Production server
security: []
tags:
  - name: Accounts
    description: Account management endpoints for positions, orders, and balances
  - name: Analytics
    description: >-
      Analytics endpoints for market data analysis including top gainers,
      losers, volume leaders, sector analysis, analyst ratings, market breadth,
      and net inflow
  - name: Authentication
    description: User authentication endpoints
  - name: Calendars
    description: Calendar endpoints for economic events and historical data
  - name: Market Data
    description: >-
      Market data endpoints for symbol search, real-time data access, and equity
      details
  - name: Orders
    description: >-
      Order management endpoints for placing, updating, canceling, and
      previewing orders
  - name: Users
    description: User management endpoints
  - name: Health
    description: Service health endpoints
paths:
  /v1/config/{category}/settings:
    post:
      tags:
        - Settings
      summary: Create Setting
      description: >-
        Creates a new setting for a specific category with dynamic key-value
        pairs. This endpoint allows authenticated users to create configuration
        settings organized by category. Each setting consists of a key and value
        pair that can be used to store application configuration.
      operationId: createSetting
      parameters:
        - name: category
          in: path
          description: >-
            Category of the setting (e.g., 'display', 'trading',
            'notifications')
          required: true
          schema:
            type: string
          example: feature-flags
      requestBody:
        description: Global settings data as key-value pairs
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
            example:
              new_ui_enabled: true
              beta_features: false
              api_rate_limit: 100
        required: true
      responses:
        '201':
          description: Setting created successfully
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: Bad request - Invalid request body or setting already exists
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  codes:
                    type: array
                    items:
                      type: object
                      properties:
                        code:
                          type: string
                        description:
                          type: string
                      required:
                        - code
                        - description
                required:
                  - error
              example:
                error: Setting already exists
                codes:
                  - code: SETTING_ALREADY_EXISTS
                    description: Setting already exists
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: Unauthorized
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
              example:
                error: Internal server error
      security:
        - BearerAuth: []
      x-codeSamples:
        - lang: java
          label: Java (SDK)
          source: |-
            package hello.world;

            import java.lang.Exception;
            import java.util.Map;
            import org.openapis.openapi.AriesJava;
            import org.openapis.openapi.models.errors.*;
            import org.openapis.openapi.models.operations.CreateSettingResponse;

            public class Application {

                public static void main(String[] args) throws BadRequestException, UnauthorizedException, InternalServerError, Exception {

                    AriesJava sdk = AriesJava.builder()
                            .bearerAuth(System.getenv().getOrDefault("BEARER_AUTH", ""))
                        .build();

                    CreateSettingResponse res = sdk.settings().create()
                            .category("feature-flags")
                            .body(Map.ofEntries(
                                Map.entry("new_ui_enabled", true),
                                Map.entry("beta_features", false),
                                Map.entry("api_rate_limit", 100L)))
                            .call();

                    if (res.object().isPresent()) {
                        // handle response
                    }
                }
            }
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````