Sales Engine
API documentation
ProjectsOperation projects.results.update

Projects results update

Update a result, usually its current value.

PATCH/api/v1/projects/{id}/results/{resultId}
Scope write: Create and edit lists, research, sequences, campaigns, memory, signals and learning; queue jobs.

Parameters

Path

NameInDescription
idrequiredpathThe record's id.
resultIdrequiredpathThe record's id.

Body

A JSON object. Fields not listed are ignored.

NameInDescription
metricbodyWhat is measured, such as Qualified meetings a month.
unitbodyUnit, such as meetings or %.
baselinebody, integerWhere it started.
targetbody, integerThe goal.
currentbody, integerWhere it is now.
positionbody, integerOrder.
client_visiblebody, booleanShow it on the portal (default yes).

Example

curl
curl -X PATCH "https://crm.ashwanth.dev/api/v1/projects/{id}/results/{resultId}" \
  -H "Authorization: Bearer $SALES_ENGINE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "metric": "",
  "unit": "",
  "baseline": 0,
  "target": 0,
  "current": 0,
  "position": 0,
  "client_visible": false
}'
CLI
sales-engine projects results update <id> <resultId>

The JSON above lists every documented field with a typed placeholder; send only the ones you mean.

Response

A 200 with the result under data, on creation too. Errors come back as an error object with a stable code; see Errors.

Shape
{
  "data": { ... }
}

Run it below to see the live shape for your workspace.

Try it

Runs against this server, as the workspace behind the key.
Kept in this page while you browse the docs, gone on reload, never stored. Signed in to the app? Leave it blank and the call runs as you.
Path
required
The record's id.
required
The record's id.
Every documented field is listed above; leave out the ones you do not need.
Request
PATCH /api/v1/projects/%7Bid%7D/results/%7BresultId%7D
Fill the path first.

Also in Projects