Skip to main content
PATCH
/
api
/
signals
/
search
/
{id}
Re-filter a completed signal search
curl --request PATCH \
  --url https://app.puffle.ai/api/signals/search/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "filterPrompt": "<string>"
}
'
{
  "success": true,
  "status": "running"
}

​
Overview

Update the filter_prompt on a completed search and enqueue a re-filter Trigger.dev task. All existing results are reset to relevant=false; the filter task flips matching ones back to true. search.status flips to running until the task finishes. Only completed searches can be re-filtered.
This operation shares the URL path /api/signals/search/{id} with other verbs. See the sibling page for related operations on the same resource.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
id
string<uuid>
required

Signal search UUID.

Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$

Body

application/json
​
filterPrompt
string
required

New LLM relevance filter instruction, 1-1000 chars. Replaces the previous filter and re-evaluates all existing results.

Required string length: 1 - 1000

Response

Filter re-run enqueued. Poll GET /api/signals/search/{id} for completion.

​
success
enum<boolean>
required
Available options:
true
​
status
enum<string>
required
Available options:
running