Skip to main content
POST
Dispatch object to router

Endpoint

Route: /dispatch/router
Authentication: Bearer JWT
Runs router assignment logic for a given object: evaluates triggers, availability, distribution model, and assigns an owner when rules match.

Request body

Responses

200 — Assignment succeeded
When the router has a HubSpot integration and sync fails after a successful Routera assignment, the response is still 200 with success: true plus: 200 — Other outcomes (no assignment; response has message only, no error flag) 400 — Invalid JSON or missing required fields
500 — Processing error
This endpoint can also be invoked asynchronously via SQS with the same router_id and object_id fields in the message body.

Authorizations

Authorization
string
header
required

Bearer JWT with valid account context.

Body

application/json
router_id
string
required

Router to run

object_id
string
required

Object to assign

Response

Dispatch completed

Assignment succeeded, or a non-error outcome (HTTP 200). When success is true, the object was assigned.

message
string
success
boolean

Present and true when the object was assigned

user
string

Email of the user assigned as owner

field_name
string

Display name of the owner field that was updated

owner_assigned_at
string

Assignment timestamp (RFC 2822 UTC)

hubspot_sync_failed
boolean

True when Routera assigned the owner but HubSpot sync failed

hubspot_error
string

HubSpot sync error detail (when hubspot_sync_failed is true)

error
boolean

True only on HTTP 400/500 error responses