Set key metrics
A user can have several lines of the same metric in the same month (they add up):array of row objects
required
The key-metric lines to book, described below. Up to 1,000 per call.
boolean
default:"false"
If a row’s
metric_id already exists (c.f. rows parameters below), overwrite it instead of throwing an error.rows accepts:
string
required
The user the value belongs to.
string
required
Name of the key metric. The first time you post a new one, it’s automatically added to the project’s key metrics.
number
required
The value to book.
"YYYY-MM"
The calendar month the value belongs to. Required unless you set
month_start and month_end instead."YYYY-MM"
Bill over a multi-month period (e.g. quarterly) instead of a single
month. amount is split evenly over the period. Set either month, or both month_start and month_end, never both forms on the same row.string
An id for the key-metric row over which uniqueness is checked, typically from your own tracking system.
API values are their own key-metric source, alongside CSV uploads. Sources add up: if you post a value for a user-month that also has a CSV upload, Weflayr assumes it is the sum. We recommend using one source only to avoid double counting.
Get key metrics
list[string]
Specify the names of the users whose key metrics should be fetched. Not setting it means “all users”.
integer
default:"100"
Numbers of rows to fetch. Max
1000.string
The route is paginated: pass the previous page’s
next_cursor to fetch the next page. PS: has_more from the output says whether another page exists.Delete key metrics
list[string]
required
Delete all these users’ API-booked key metrics.
"YYYY-MM"
Narrow the delete to this inclusive month range. Omit both to delete every API-booked value of the named users.