How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nexla Private Query API

The Private Query API from Nexla — 1 operation(s) for private query.

Nexla Private Query API is one of 72 APIs that Nexla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Private Query. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 1 operation across 1 path, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version v0.2.3.3-combined.

Requests are made against the base URL https://dataops.nexla.io/nexla-api.

1 operations 1 paths 17 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0.2.3.3-combined
Base URL
https://dataops.nexla.io/nexla-api
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Private Query 1
POST
/private_query
Private Query
private_query_private_query_post 1 param body → 200422

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PrivateQueryRequest (14 properties), LLMConfig (6 properties), UserContext (6 properties), ValidationError (5 properties). Each schema is shown below with its type and property counts.

RerankingConfig
object
4 properties 2 required
LLMConfig
object
6 properties 2 required
EmbeddingConfig
object
4 properties 2 required
FilterCondition
object
A single filter predicate on a metadata key.
3 properties 2 required
NexsetFilters
object
Filters applied to a specific nexset during retrieval.
3 properties
UserContext
object
6 properties 1 required
PromptOverrides
object
2 properties
ValidationError
object
5 properties 3 required
LLMCredentialParameters
object
5 properties
HTTPValidationError
object
1 property
RetrievalParams
object
2 properties
NexsetSpec
object
Specification for a nexset to include in a query, with optional per-nexset filters.
2 properties 1 required
PrivateQueryRequest
object
14 properties 2 required
TokenType
string
FilterOperator
string
Supported operators for nexset metadata filtering.
LLMModelParams
object
3 properties
StreamFormat
string
Supported streaming response formats.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nexla-private-query-api-openapi.yml Raw ↑

Other APIs Nexla publishes across the network.

Nexla Access Control API
Nexla Approval Requests API
Nexla Async Tasks API
Nexla Audit Logs API
Nexla Bulk Evaluation API
Nexla Bulk Query API
Nexla Clear Dataset Cache API
Nexla Clear Token Cache API
Nexla Code API
Nexla Code Containers API
Nexla Credential Mappings API
Nexla Credentials API
Where this information came from

This is an independent, third-party profile of Nexla Private Query API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.