Send Location Message
Send a location (latitude, longitude, optional label) to a recipient via the Sinch Conversation API. Supported on RCS, WhatsApp, and other channels that support location sharing.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--to / -t: Recipient phone number (E.164) - required
--lat / -y: Latitude (decimal) - required
--lon / -x: Longitude (decimal) - required
--label / -l: Optional label for the location (e.g. "Store downtown")
--channel / -c: Channel (RCS, WHATSAPP) - optional
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
If $ARGUMENTS empty: ask for recipient, latitude, longitude, and optional label. Otherwise parse.
Validate: --to (E.164), --lat (valid number -90 to 90), --lon (valid number -180 to 180). Optional: --label, --channel.
Try MCP tool mcp__sinch__send-location-message if available with recipient, lat, lon, label, channel. On success display result and exit.
If MCP not available: get CONVERSATION_* env vars. If missing, report "Sinch API is not configured."
Build message.location_message with latitude, longitude, and optional title (label). Recipient via channel_identities.
POST https://{region}.conversation.api.sinch.com/v1/projects/{projectId}/messages:send with OAuth2, body: app_id, recipient, message.
On success: "✅ Location message sent!" with message ID. Handle errors clearly.
Handle all errors gracefully.
Examples
/sinch-api-messages-send-location --to=+14155551234 --lat=37.7749 --lon=-122.4194
/sinch-api-messages-send-location -t +14155551234 -y 55.61 -x 13.00 --label="Sinch HQ"
API Reference
Notes
- Not all channels support location; RCS and WhatsApp typically do. Unsupported channels may return an error.
1---2name: sinch-api-messages-send-location3description: Send a location message via Sinch Conversation API4---56# Send Location Message78Send a location (latitude, longitude, optional label) to a recipient via the Sinch Conversation API. Supported on RCS, WhatsApp, and other channels that support location sharing.910**IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.**1112## Input1314- `--to` / `-t`: Recipient phone number (E.164) - required15- `--lat` / `-y`: Latitude (decimal) - required16- `--lon` / `-x`: Longitude (decimal) - required17- `--label` / `-l`: Optional label for the location (e.g. "Store downtown")18- `--channel` / `-c`: Channel (RCS, WHATSAPP) - optional1920Arguments: $ARGUMENTS2122## Instructions2324**Execute these steps directly - do not write code or scripts:**25260. If $ARGUMENTS empty: ask for recipient, latitude, longitude, and optional label. Otherwise parse.27281. Validate: --to (E.164), --lat (valid number -90 to 90), --lon (valid number -180 to 180). Optional: --label, --channel.29302. Try MCP tool `mcp__sinch__send-location-message` if available with recipient, lat, lon, label, channel. On success display result and exit.31323. If MCP not available: get CONVERSATION_* env vars. If missing, report "Sinch API is not configured."33344. Build message.location_message with latitude, longitude, and optional title (label). Recipient via channel_identities.35365. POST https://{region}.conversation.api.sinch.com/v1/projects/{projectId}/messages:send with OAuth2, body: app_id, recipient, message.37386. On success: "✅ Location message sent!" with message ID. Handle errors clearly.39407. Handle all errors gracefully.4142## Examples4344```45/sinch-api-messages-send-location --to=+14155551234 --lat=37.7749 --lon=-122.419446/sinch-api-messages-send-location -t +14155551234 -y 55.61 -x 13.00 --label="Sinch HQ"47```4849## API Reference5051- **MCP Tool**: `mcp__sinch__send-location-message`52- **API Endpoint**: POST /v1/projects/{projectId}/messages:send53- **Message type**: location_message (latitude, longitude, title)54- **Documentation**: https://developers.sinch.com/docs/conversation/message-types5556## Notes5758- Not all channels support location; RCS and WhatsApp typically do. Unsupported channels may return an error.