1 minute readDocsAgent-ready
The API reference now shows the real body for recording a usage signal
Recording a usage signal takes eventType, agentId, customerId, properties and metadata at the top level, and the reference and dashboard docs now say so.
The API reference described recording a usage signal with a nested signal object, which the API has never read, so a request built from it was refused with eventType is required. The reference now documents the body the API accepts: eventType (required), plus optional agentId, customerId, properties and metadata. It also documents the response, which returns the stored signal.
Saving a block now returns the same fields as reading it.
For help, write to support@last-price.ai.