Set revenue
A customer can have several lines in the same month (in case of multiple billings):array of row objects
required
The revenue lines to book, described below. Up to 1,000 per call.
boolean
default:"false"
If a row’s
revenue_id already exists (c.f. rows parameters below), overwrite it instead of throwing an error.rows accepts:
string
required
The same
customer_name you stamp on your LLM calls when propagating metadata, so revenue and AI cost land on the same customer.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 revenue row over which uniqueness is checked, typically from a billing management system.
API values are their own revenue source, alongside Stripe and CSV. Sources add up: if you post revenue for a customer-month that also has a CSV upload or a Stripe sync, Weflayr assumes it is the sum. We recommend using one source only to avoid double counting.
Get revenue
list[string]
Specify the names of the customers from which revenue should be fetched. Not setting it means “all customers”.
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 revenue
list[string]
required
Delete all these customers’ API-booked revenue.
"YYYY-MM"
Narrow the delete to this inclusive month range. Omit both to delete every API-booked value of the named customers.