/api/v1/object/data/{objectSlug}/signalsGet badge counts for a set of records.
Get badge counts for a set of records.
Send up to 500 record slugs in slugs. Returns one entry per record the
credential can see; slugs it cannot see, and slugs that match no record,
are left out. Each entry holds:
open_tasks— open tasks linked to the record.overdue—truewhen one of those tasks is past its due date.mentions— unread comment mentions of the credential owner.unread_incoming— unread incoming messages in chats linked to the record, ornullwhen the credential owner may not read chats.
Returns an empty list unless GET /object/features reports
record_signals: true. Counts can be up to 60 seconds old.
Scope: read.<object slug>, for example read.contacts.
Errors:
400— no active object has that slug.403— the credential lacksread.<object slug>.422—slugsis missing, empty, holds more than 500 entries, or holds a value that is not a string.
Request:
{ "slugs": ["9f2c4b7a1e03", "4d7b1e9a2c65"] }
Response 200:
{
"status": 200,
"message": "Record signals retrieved successfully",
"data": [
{
"record_slug": "9f2c4b7a1e03",
"unread_incoming": 3,
"open_tasks": 2,
"overdue": true,
"mentions": 0
},
{
"record_slug": "4d7b1e9a2c65",
"unread_incoming": 0,
"open_tasks": 0,
"overdue": false,
"mentions": 1
}
]
}
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/jsonrequiredCapped at the bulk ceiling: the response is one entry per slug and the counts behind it are three grouped queries, so an unbounded list would turn one request into a table scan per signal source.
Responses
Successful response
{
"message": "string",
"data": [
"string"
]
}Bad request
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Unauthorized
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Internal server error
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Powered by heyo-docs