Skip to main content
POST
Create or update a tap prompt fragment

Authorizations

x-api-key
string
header
required

Optional API key for authentication (enabled via application.yaml)

Body

application/json
key
string
required

Data-source key that triggers injection (e.g. a provider or API name)

aliases
string[]

Alternate names that also trigger this fragment

content
string

Fragment text appended to the tap code-generation system prompt when the key/alias matches

enabled
boolean
default:true
createdAt
string
updatedAt
string
status
enum<string>

Absent or active for fragments a person wrote or accepted; suggested for fragments the recovery agent wrote from an incident's learn note (stored with enabled false). Accept one by POSTing it with enabled true and status active; agents may not.

Available options:
active,
suggested
origin
enum<string>

Where a suggested fragment came from

Available options:
incident
incidentId
string

The incident whose learn note produced the fragment

Response

Saved

status
string
Example:

"ok"