> ## Documentation Index > Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Index an event signal > Index an event signal into the specified collection. The JSON request body describes the signal's attributes. ## OpenAPI ````yaml /api-reference/5.9/fusion-api-query.json post /signals/{collection} openapi: 3.0.1 info: title: Fusion Query API description: >- A Lucidworks Fusion microservice for machine-learning-enhanced ranking and retrieval. contact: name: Lucidworks url: www.lucidworks.com email: support@lucidworks.com license: name: License of API url: https://lucidworks.com/legal/developer-license-agreement/ version: '5.9' servers: - url: https://{FUSION HOST}/api description: Fusion variables: FUSION HOST: default: FUSION_HOST description: Your environment host. - url: https://{FUSION HOST}/api/apps/{APP_NAME} description: Fusion app variables: FUSION HOST: default: FUSION_HOST description: Your environment host. APP_NAME: default: APP_NAME description: The name of your Fusion app. security: - Basic auth: [] - API key: [] tags: - name: Custom Rule Type API description: Endpoints to define and manage custom rule type definitions. - name: Experiments API description: >- Use the Experiments API to compare different configuration variants and determine which ones are most successful. - name: Query Pipelines API description: >- Use these endpoints to view and manage your query pipelines. You can also send queries using this API, though the Query Profiles API is recommended instead. - name: Query Profiles API description: >- The Query Profiles API provides static endpoints that you can consistently point to when querying your collections. Query profiles allow you to change the query pipelines or collections behind them without changing the endpoint you use for your search queries. See the Query Profiles CRUD API for endpoints that create and modify query profiles. - name: Query Profiles CRUD API description: >- Use these endpoints to create and modify query profiles. Query profiles allow you to change the query pipelines or collections behind them without changing the endpoint you use for your search queries. See the Query Profiles API for the query endpoints. - name: Query Rewrite API description: >- The Query Rewrite API manages documents used for query rewriting to improve relevancy using AI-generated data. Primarily for internal use. - name: Query Stage API description: >- Use these endpoints to view the available query pipeline stages and their configuration parameters. - name: Query Stage Plugins API description: >- Use these endpoints to view, install, and manage custom query stages developed with the Query Stage SDK. - name: Signal Indexing API description: Endpoints to index signals. - name: Experience Manager API description: API only for internal use by the Experience Manager Springboard system - name: Query Pipeline Template API description: Used internally to generate query pipelines from a template. externalDocs: description: Lucidworks Documentation. url: https://doc.lucidworks.com/ paths: /signals/{collection}: post: tags: - Signal Indexing API summary: Index an event signal description: >- Index an event signal into the specified collection. The JSON request body describes the signal's attributes. operationId: createSignals parameters: - name: collection description: The data collection to which this signal belongs. in: path required: true schema: type: string - name: pipelineId description: >- An index pipeline to use for processing signals. Note that the index pipeline must end with a Solr Indexer stage, and in this stage the `enforce_schema` property must be set to 'true'. in: query required: false schema: type: string - name: commit description: >- Whether to commit signals to the collection immediately after indexing each one. The setting is not recommended in production and performance testing because it negatively impacts performance. Instead, consider letting the defaults of the Solr collection dictate the commit frequency. in: query required: false schema: type: boolean - name: async description: >- Whether to execute the request asynchronously. If true, an `autoCommit` is issued and failures are not reported. in: query required: false schema: type: boolean default: true requestBody: content: application/json: schema: type: array items: $ref: '#/components/schemas/Event' example: - params: query: Televisiones Panasonic 50 pulgadas filterQueries: - cat00000 - abcat0100000 - abcat0101000 - abcat0101001 docId: '2125233' type: click timestamp: '2011-09-01T23:44:52.53Z' - params: query: Sharp filterQueries: - cat00000 - abcat0100000 - abcat0101000 - abcat0101001 docId: '2009324' type: click timestamp: '2011-09-05T12:25:37.42Z' required: true responses: '200': description: OK content: '*/*': schema: type: object example: responseHeader: status: 0 QTime: 1 params: indent: 'true' q: 'docId: 2125233' wt: json response: numFound: 1198 start: 0 docs: - id: 7aee7b1f-5cde-4957-b73c-c15881f559ec filters_s: abcat0100000 $ abcat0101000 $ abcat0101001 $ cat00000 query_orig_s: Televisiones Panasonic 50 pulgadas params.user_s: 000000df17cd56a5df4a94074e133c9d4739fae3 docId: '2125233' params.query_time__s: '2011-09-01T23:43:59.75Z' query_t: televisiones panasonic 50 pulgadas query_s: televisiones panasonic 50 pulgadas filters_orig_ss: - abcat0100000 - abcat0101000 - abcat0101001 - cat00000 flag_s: EVENT type_s: click attr_params.filterQueries_: - cat00000 - abcat0100000 - abcat0101000 - abcat0101001 timestamp_dt: '2011-09-01T23:44:52.53Z' _version_: 1478892846857584600 - id: 6789a209-f5b5-457e-9df6-8033b8f7f317 filters_s: abcat0100000 $ abcat0101000 $ abcat0101001 $ cat00000 query_orig_s: Sharp params.user_s: 000001928162247ffaf63185cd8b2a244c78e7c6 docId: '2009324' params.query_time__s: '2011-09-05T12:25:01.18Z' query_t: sharp query_s: sharp filters_orig_ss: - abcat0100000 - abcat0101000 - abcat0101001 - cat00000 flag_s: EVENT type_s: click attr_params.filterQueries_: - cat00000 - abcat0100000 - abcat0101000 - abcat0101001 timestamp_dt: '2011-09-05T12:25:37.42Z' _version_: 1478892846859681800 components: schemas: Event: type: object properties: id: type: string epoch: type: integer format: int64 timestamp: type: string type: type: string params: type: object securitySchemes: Basic auth: type: http scheme: basic API key: name: x-api-key type: apiKey in: header ````