Shared
ModelsExpand Collapse
ChatHandle object { id, handle, joined_at, 5 more }
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
line_type: optional "iMessage" or "RCS"The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
LinkPartResponse object { reactions, type, value } A rich link preview part
A rich link preview part
Reactions on this message part
Reactions on this message part
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
line_type: optional "iMessage" or "RCS"The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question.
Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question. Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
MediaPartResponse object { id, filename, mime_type, 4 more } A media attachment part
A media attachment part
Reactions on this message part
Reactions on this message part
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
line_type: optional "iMessage" or "RCS"The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question.
Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question. Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
Reaction object { handle, is_me, type, 2 more }
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
line_type: optional "iMessage" or "RCS"The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question.
Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question. Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
TextPartResponse object { reactions, type, value } A text message part
A text message part
Reactions on this message part
Reactions on this message part
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
Messaging service type. Where this names the transport a message used,
it is per-message: a chat’s own service can differ from a message in
it, and a conversation can fall back from RCS to SMS.
line_type: optional "iMessage" or "RCS"The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
The kind of line: iMessage for an iMessage-capable line, RCS for an
RCS-only line, which sends RCS and SMS but never iMessage. Same values as
the type parameter on GET /v3/available_number. A property of the line
itself, so unlike service it does not change with the conversation:
an iMessage-capable line can still carry an RCS or SMS conversation.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question.
Custom reactions have type “custom” with the actual emoji in the custom_emoji field.
Type of reaction. Standard reactions are love, like, dislike, laugh, emphasize, question. Custom reactions have type “custom” with the actual emoji in the custom_emoji field.