Trackers

Create a tracker, in draft

Creates a tracker in draft: it measures nothing until started. Starting it launches its first survey immediately, unless it carries a chosen next_survey_at still in the future, in which case the grid starts on that date. That first survey runs on every frequency, on_demand included, where it is also the last one until POST /trackers/{id}/survey asks for another. Manager or above.

post/trackers

Request

  • Base URL: https://api.epovest.com/v1
  • URL: https://api.epovest.com/v1/trackers
  • Auth: HTTP bearer

Request body

titlestring required

Display name.

promptsstring[] required

The questions asked to the engines at every survey, phrased as a customer would ask them.

enginesEngine[] required
frequency'monthly' | 'weekly' | 'daily' | 'on_demand' required

The pace of the surveys. on_demand puts the tracker on no schedule: starting it runs one survey, and every survey after that comes from POST /trackers/{id}/survey.

resolution'hd' | 'full_hd' | '4k' | '8k' required

Repetitions of every question per engine and survey: hd=1, full_hd=3, 4k=6, 8k=9.

analystsAnalystType[]
custom_promptstring

The instruction of the custom_prompt analyst; it comes with it.

discoveryboolean

Suggests new keywords spotted in the answers. It works from keywords, so send keywords[] alongside, and check discovery in the answer.

notify_on_surveyboolean
next_survey_atstring

When the first survey runs, ISO 8601 with a date AND a time (2026-08-01T09:00), strictly in the future, read as UTC without an offset. Omitted, the first survey runs at start. Sent on a PAUSED tracker it is kept and read back like anywhere else, and it is what makes the next start wait instead of surveying right away. It goes with a frequency that has a pace: sent alongside on_demand it answers 422, and POST /trackers/{id}/survey is the move it was reaching for.

project_idstring

The UUID of a project of the account, or default for none. Omitted, the tracker files under Default.

Response

The tracker, in draft.

Changes

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