"description":"Send a message to some technology URI or endpoint.",
"operations":[
{
"httpMethod":"PUT",
"summary":"Send a message to some technology URI or endpoint.",
"nickname":"sendMessage",
"responseClass":"void",
"parameters":[
{
"name":"to",
"description":"The endpoint resource or technology specific URI to send the message to. Valid resources are sip, pjsip, and xmpp.",
"paramType":"query",
"required":true,
"allowMultiple":false,
"dataType":"string"
},
{
"name":"from",
"description":"The endpoint resource or technology specific identity to send this message from. Valid resources are sip, pjsip, and xmpp.",
"paramType":"query",
"required":true,
"allowMultiple":false,
"dataType":"string"
},
{
"name":"body",
"description":"The body of the message",
"paramType":"query",
"required":false,
"allowMultiple":false,
"dataType":"string"
},
{
"name":"variables",
"descriptioni":"The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip and sip resource types will add the key/value pairs as SIP headers,",
"description":"Send a message to some endpoint in a technology.",
"operations":[
{
"httpMethod":"PUT",
"summary":"Send a message to some endpoint in a technology.",
"nickname":"sendMessageToEndpoint",
"responseClass":"void",
"parameters":[
{
"name":"tech",
"description":"Technology of the endpoint",
"paramType":"path",
"dataType":"string"
},
{
"name":"resource",
"description":"ID of the endpoint",
"paramType":"path",
"dataType":"string"
},
{
"name":"from",
"description":"The endpoint resource or technology specific identity to send this message from. Valid resources are sip, pjsip, and xmpp.",
"paramType":"query",
"required":true,
"allowMultiple":false,
"dataType":"string"
},
{
"name":"body",
"description":"The body of the message",
"paramType":"query",
"required":false,
"allowMultiple":false,
"dataType":"string"
},
{
"name":"variables",
"descriptioni":"The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip and sip resource types will add the key/value pairs as SIP headers,",