Update an event type
Updates an existing event type. Only the fields sent are changed. Sending cadence_amount or cadence_unit (null included) requires data capture rate to be enabled for your account (feature_data_capture_rate in GET /feature_flags); otherwise returns 422 “cadence_amount and cadence_unit require feature_data_capture_rate” and nothing is saved. Requests that leave out both fields are not gated. PUT behaves the same. Requires the read:project and write:event_type token scopes.
Authorizations
Path Parameters
The project's friendly ID (e.g. prj_aBcD1234eFgH5678).
The event type's friendly ID (e.g. et_aBcD1234eFgH5678).
Body
Response
The updated event type.
The event type's friendly ID (e.g. et_aBcD1234eFgH5678).
"et_aBcD1234eFgH5678"
True when expected_locations is two.
How often an event of this type is expected, as a count of cadence_unit. An event type carries both cadence fields or neither; both null means no cadence is declared, which the app shows as Irregular.
x >= 115
The unit cadence_amount counts. second, minute and hour measure elapsed time; day and above are calendar periods advanced in the account's time zone, so 1 day and 24 hour are different declarations and a daily stream stays on local midnight across a clock change. From month up, a reading counts toward the period that contains it rather than the nearest period boundary, so a monthly reading taken on the 28th still counts for that month.
second, minute, hour, day, week, month, year, null "minute"
Link that opens this event type in the Mangrove app.
"https://app.gomangrove.com/nexus/prj_aBcD1234eFgH5678/data-inputs/event-types/et_aBcD1234eFgH5678"