Recipes

Report a false-positive or false-negative against a protection recipe

Files a false-negative ('fn') or false-positive ('fp') report against an existing detection_recipes id. The customer is recorded as the 'created' identity on the recipe_review_actions chain; the candidate lands in pending state and awaits review. Requires customer-session auth (JWT cookie / bearer) OR an API key. Idempotency-Key header is REQUIRED — the body hash is folded into the reservation so a customer can re-submit with corrected details without 422'ing.

post/recipes/{recipeId}/report

Request

  • Base URL: https://api.mnemom.ai/v1
  • URL: https://api.mnemom.ai/v1/recipes/{recipeId}/report
  • Auth: one of:
    • HTTP bearer
    • API key in header X-Mnemom-Api-Key

Path parameters

recipeIdstring required

The detection_recipes id the report is filed against (the recipe that misfired or failed to fire).

Headers

Idempotency-Keystring required

Client-supplied UUID (or comparable) for de-duplication. Same key + same body within 24h replays the prior response; same key + different body returns 422.

Request body

type'fn' | 'fp' required

'fn' (false negative — recipe should have fired) or 'fp' (false positive — recipe fired on legitimate behaviour).

summarystring required

Customer's description of what happened.

evidencestring

Optional raw payload / log excerpt the admin reviewer can inspect.

agent_idstring

Optional. Customer's agent id, when the report concerns a specific agent.

checkpoint_idstring

Optional. Related integrity_checkpoints id (helps the reviewer correlate).

Response

Candidate created; awaiting review.

oktrue required
candidate_idstring required
type'fn' | 'fp' required
related_recipe_idstring required

Changes

No recorded changes to this operation across all 1 revision of this API.