/v1/definitions/{key}/rows/{rowId}/offersAdd an offer to a deal
Two asks on one path, and the body says which: send {offer: …} and the ONE offer the desk wrote is created and presented in the same transaction; send a riskProfile or a score (0-100, one or the other, never both) and the tier ladder is generated from it. Either way the answer is the offers rows this call created, so a client reads one shape. An authored offer needs a positive funded amount, and a workspace that deleted its presented status has deleted the authored path with it. Deals page only.
Access class: def:read.
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Request body
application/jsonrequiredResponses
the action's answer
{
"data": [
{
"archived_at": "string",
"assignees": {},
"cells": {},
"createdBy": "string",
"display": {},
"externalId": "",
"groupId": "",
"id": "",
"position": 1,
"source": "string"
}
]
}a refusal: {"error": "<what a person needs to read>"}. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.
{
"error": "string"
}