Warp search
Last updated
Was this helpful?
Last updated
Was this helpful?
From client application perspective, warp search consists of two major steps: initiate a search, using http request, which returns the search identifier, and then subscribe to warp search results, using the provided search id. Details are provided below.
Initiate a warp search.
Warp search is initiated, using the corresponding endpoint (/warps/search). Please refer to for details.
Subscription to search results.
Search results are returned as RabbitMQ events (Please refer to for details about connection to RabbitMQ of TEOS Api).
After receiving the search Id in the step 1, the client needs to subscribe to events from the queue named "warps-{searchId}" ({searchId} must be replaced by the actual identifier of the search, retrieved in step 1). TEOS Api guarantees, that the queue exists by the time of returning the response in step 1. The queue exists for 5 minutes.
There are two types of messages, that can arrive from the queue:
Contains the details of the warp. Example of the message:
Contains the summary of warp search. Please be aware that due to async nature of the warp search, this message does not necessarily arrive after all the result have arrived. The FoundWarpCount property shows, how many WarpFound messages must arrive within this search.