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

Lucidworks Signals API

Capture and retrieve user behavior signals

Lucidworks Signals API is one of 12 APIs that Lucidworks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.lucidworks.ai.

8 operations 4 paths 2 schemas 4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.lucidworks.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lucidworks Signals API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Signals 8

Capture and retrieve user behavior signals

GET
/signals/click
Get click signals
getClickSignals 3 params → 200
POST
/signals/click
Record click signal
recordClickSignal body → 201
GET
/signals/query
Get query signals
getQuerySignals → 200
POST
/signals/query
Record query signal
recordQuerySignal body → 201
GET
/signals/cartadd
Get cart-add signals
getCartAddSignals → 200
POST
/signals/cartadd
Record cart-add signal
recordCartAddSignal body → 201
GET
/signals/purchase-complete
Get purchase-complete signals
getPurchaseCompleteSignals → 200
POST
/signals/purchase-complete
Record purchase-complete signal
recordPurchaseSignal body → 201

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Signal (5 properties), SignalList (2 properties). Each schema is shown below with its type and property counts.

SignalList
object
2 properties
Signal
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lucidworks-signals-api-openapi.yml Raw ↑

Other APIs Lucidworks publishes across the network.

Lucidworks Fusion REST API
Lucidworks Chunking API
Lucidworks Classification API
Lucidworks Deployments API
Lucidworks Embeddings API
Lucidworks Models API
Lucidworks Predictions API
Lucidworks QueryRewrites API
Lucidworks Results API
Lucidworks Rules API
Lucidworks Tokenization API
Where this information came from

This is an independent, third-party profile of Lucidworks Signals 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.