Skip to content
vocapable.Docs

Record an agreed callback

POST
/v1/mobile/workspace/callbacks
curl --request POST \
  --url https://api.vocapable.com/v1/mobile/workspace/callbacks \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "organization_id": "example", "contact_id": "example", "opportunity_id": "example", "title": "example", "due_at": "2026-04-15T12:00:00Z", "owner_user_id": "example" }'

A callback is a promise of kind callback with a future agreed time. Its open state is what the contact policy reads (callback_scheduled) to prevent a premature retry, and the push worker wakes its owner as the time arrives.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Header Parameters

Section titled “Header Parameters”
Idempotency-Key
Any of:
string

Unique key for this request. A retry after a lost response or a reconnect replays the original result instead of saving the note or task twice.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
MobileWorkspaceCallbackCreate

An agreed callback: a promise with a responsible person and a future time.

object
organization_id
required
Organization Id
string
contact_id
Any of:
string
opportunity_id
Any of:
string
title
required
Title
string
>= 1 characters <= 300 characters
due_at
required
Due At
string format: date-time
owner_user_id
Any of:
string
Examplegenerated
{
  "organization_id": "example",
  "contact_id": "example",
  "opportunity_id": "example",
  "title": "example",
  "due_at": "2026-04-15T12:00:00Z",
  "owner_user_id": "example"
}

Responses

Section titled “Responses”

201

Section titled “201”

Successful Response

Media typeapplication/json
WorkspaceTask
object
id
required
Id
string
kind
required
Kind
string
Allowed values: follow_up callback delivery review case_response meeting_prep
title
required
Title
string
organization_id
required
Any of:
string
contact_id
required
Any of:
string
opportunity_id
required
Any of:
string
subject_type
required
Any of:
string
Allowed values: handoff case meeting approval call quote
subject_id
required
Any of:
string
owner
required
Any of:
WorkspacePersonRef

A teammate named on a record: the id the server holds and the name to show.

object
user_id
required
User Id
string
name
required
Name
string
due_at
required
Any of:
string format: date-time
status
required
Status
string
Allowed values: open done cancelled
completed_at
required
Any of:
string format: date-time
completed_by_user_id
required
Any of:
string
completion_note
required
Any of:
string
revision
required
Revision
integer
created_at
required
Created At
string format: date-time
updated_at
required
Updated At
string format: date-time
Example
{
  "kind": "follow_up",
  "subject_type": "handoff",
  "status": "open"
}

422

Section titled “422”

Validation Error

Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
input
Input
ctx
Context
object
Examplegenerated
{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example",
      "input": "example",
      "ctx": {}
    }
  ]
}