bigdata_edit_monitor

​

Overview

​

When to Use

• Activating: Turning a monitor on after previewing it, with email delivery if the user asked for it
• Rescheduling: Replacing the frequency or cron schedule
• Refining: Narrowing what the monitor keeps with intent_refinement or extraction_instructions
• Changing scope: Replacing the search queries, the entities, or the structured output schema

​

How It Works

1. Find the monitor id with bigdata_get_monitor if the user has not supplied it
2. Call bigdata_edit_monitor with the id and at least one change
3. Read the returned monitor detail to confirm the result

​

Parameters

{
  "id": "b0253b18-0dd8-4a01-a9a4-f209bce91a26",
  "status": "active",
  "delivery": {"type": "email"}
}

​

Important Notes

• id is required, plus at least one other field. A call with nothing to change returns an error
• An explicit null only clears structured_output, extraction_instructions, entities, or delivery
• intent_refinement cannot be combined with structured_output or with an entities change. Change the entities first, then send the refinement in a second call
• If every field you send already matches what is stored, nothing is updated and the current monitor is returned
• Schema edits and refinements are tried only once, because each one is a model call. A rejection returns the reason, and nothing from that call is saved
• If email delivery is requested for an owner with no email address, the whole update is rejected. Retry without delivery
• An unknown monitor id returns a not-found error

​

Data Returned

​

Practical Tips

​

Only add email when asked

​

Entities, then refinement

​

Preview after a change