Read an onboarding thread's messages
GET /voice/campaigns/onboarding/threads/{thread_id}
GET
/voice/campaigns/onboarding/threads/{thread_id}
Every message in the thread, oldest first.
Voice puts the organisation in the PATH here. It is not in this one: the only correct value is the one on the key.
Authorizations
Parameters
Path Parameters
thread_id
required
Thread id.
string
Thread id.
Header Parameters
Responses
200
Successful Response
object
data
required
A LIST result from voice, normalised so items is always present.
Voice is inconsistent about whether a list comes back bare or under a named
key (collections, files, routes, chats, …). Both are preserved:
the original key is kept for anyone reading voice’s docs, and items
always holds the same rows so a client can page one way.
object
items
Array
key
additional properties
any
pagination
Any of:
object
has_next
required
Whether there are more pages
boolean
limit
required
Items per page
integer
notes
Any of:
Array<string>
null
page
required
Current page number (1-indexed)
integer
total
required
Total number of items
integer
null
422
Validation Error
object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string