> ## Documentation Index > Fetch the complete documentation index at: https://docs.withsplendor.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a query endpoint > Creates a named, versioned SQL query with typed parameters (the durable counterpart to an ad-hoc SQL search). The SQL uses `:name` placeholders, each declared as a typed parameter; values are bound safely at execute time. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/endpoints openapi: 3.1.0 info: description: >- Splendor is a search and retrieval API for your operational data. Ingest datasets — logs, documents, and structured records — and query them through one consistent interface that spans full-text, SQL, and semantic (vector) search. Every request authenticates with a bearer token and selects a workspace with the `X-Splendor-Tenant-Id` header. Read and query operations are available to any member; operations that create, change, or delete data require an admin role. All search modes return one shared envelope, and every result carries provenance back to the exact source object it came from. title: Splendor API version: 1.0.0 servers: - description: Production url: https://api.withsplendor.com security: - bearerAuth: [] tags: - description: Resolve the authenticated user and the tenants they can access. name: Identity - description: >- Build on Splendor as a platform: authenticate with a platform API key to provision an isolated tenant per end-customer and manage your platform keys. name: Platform - description: >- List datasets, inspect inferred schemas and readiness, and manage dataset lifecycle including deletion and schema rebuilds. name: Datasets & schema - description: >- Run full-text, SQL, and semantic search over your datasets, stream results, and resolve object media. name: Search & query - description: Save queries and materialize result sets for repeatable analysis. name: Views - description: >- Define named, versioned, parameterized SQL queries and manage their versions. name: Query Endpoints - description: Create and manage asynchronous exports of search results. name: Exports - description: >- Configure data sources, upload data through hosted multipart uploads, stream logs, and track ingest runs. name: Sources & ingest - description: >- Connect third-party systems by managing connector instances in the selected tenant. name: Connectors - description: Define and test detection rules that run against incoming data. name: Detections - description: Inspect discovered fields and promote them to fast, aggregatable fields. name: Fields - description: >- Operational visibility and recovery: audit logs, usage, dead-letter queue, reindex jobs, and data-deletion jobs. name: Operations paths: /v1/endpoints: post: tags: - Query Endpoints summary: Create a query endpoint description: >- Creates a named, versioned SQL query with typed parameters (the durable counterpart to an ad-hoc SQL search). The SQL uses `:name` placeholders, each declared as a typed parameter; values are bound safely at execute time. operationId: createQueryEndpoint parameters: - $ref: '#/components/parameters/SplendorTenantId' requestBody: content: application/json: schema: $ref: '#/components/schemas/QueryEndpointCreateRequest' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/QueryEndpointResponse' description: Successful Response '400': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The request is invalid. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '409': content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The request conflicts with the current state of the resource. '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error components: parameters: SplendorTenantId: description: Selects the tenant (workspace) the request acts within. in: header name: x-splendor-tenant-id required: true schema: type: string schemas: QueryEndpointCreateRequest: description: 'Create a Query Endpoint (#684): a named SQL template + typed parameters.' properties: description: anyOf: - maxLength: 2000 type: string - type: 'null' title: Description name: maxLength: 255 minLength: 1 title: Name type: string parameters: items: $ref: '#/components/schemas/QueryParameter' title: Parameters type: array sql: minLength: 1 title: Sql type: string required: - name - sql title: QueryEndpointCreateRequest type: object QueryEndpointResponse: example: created_at: '2026-01-15T09:30:00Z' description: Orders in a region, newest first. endpoint_id: qe_01H8Z3 latest_version: 2 name: orders_by_region updated_at: '2026-01-15T09:30:00Z' properties: created_at: format: date-time title: Created At type: string description: anyOf: - type: string - type: 'null' title: Description endpoint_id: title: Endpoint Id type: string latest_version: title: Latest Version type: integer name: title: Name type: string updated_at: format: date-time title: Updated At type: string required: - endpoint_id - name - latest_version - created_at - updated_at title: QueryEndpointResponse type: object ApiError: description: >- Error envelope returned by every Splendor API endpoint. ``detail`` is either a plain message string (most errors) or a structured ``{code, message}`` object (validation and capacity errors that carry a stable machine-readable code). examples: - detail: Dataset not found - detail: code: semantic_search_capacity_exhausted message: Semantic search capacity is temporarily exhausted; retry shortly. properties: detail: anyOf: - type: string - $ref: '#/components/schemas/ErrorBody' title: Detail required: - detail title: ApiError type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object QueryParameter: description: >- One typed parameter of a Query Endpoint. A required parameter must be supplied at execute time and carries no default; an optional parameter must carry a ``default`` that is valid for its ``type``. properties: default: anyOf: - type: string - type: integer - type: number - type: boolean - type: 'null' title: Default name: title: Name type: string required: default: true title: Required type: boolean type: enum: - string - int - float - bool title: Type type: string required: - name - type title: QueryParameter type: object ErrorBody: description: Structured error detail returned by validation and capacity errors. examples: - code: semantic_query_text_required message: Semantic vector search requires non-empty text. properties: code: title: Code type: string message: title: Message type: string required: - code - message title: ErrorBody type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object responses: Unauthorized: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The bearer token is missing, malformed, or expired. Forbidden: content: application/json: schema: $ref: '#/components/schemas/ApiError' description: The token lacks access to the tenant or the role required. securitySchemes: bearerAuth: bearerFormat: JWT description: API token issued from the Splendor console. scheme: bearer type: http ````