sinch-api-messages-send-location

Send a location message with coordinates via the Sinch Conversation API.

6|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-location-sinch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-api-messages-send-location
Source: https://github.com/sinch/sinch-plugins/tree/main/plugins/sinch-antigravity-plugin/skills/sinch-api-messages-send-location
Command: npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-location-sinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending location pins through messaging channels like RCS and WhatsApp requires constructing the correct location_message payload and authenticating against the Sinch Conversation API, which is tedious to do manually. ## Core Features & Use Cases - Location Message Delivery: Send latitude, longitude, and an optional label to any recipient phone number in E.164 format. - Dual Execution Path: Uses the Sinch MCP tool when available, otherwise falls back to a direct authenticated REST API call. - Use Case: A support agent needs to share a store location with a customer on WhatsApp; they provide the phone number and coordinates and the message is sent immediately with a delivery confirmation. ## Quick Start Ask the assistant to send a location message to +14155551234 at latitude 37.7749 and longitude -122.4194 with the label "Downtown Store".

Frequently Asked Questions about sinch-api-messages-send-location

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a location message via the Sinch Conversation API?

Provide the recipient phone number in E.164 format plus latitude and longitude, optionally with a label and channel. The skill calls the Sinch MCP send-location-message tool or posts a location_message payload to the messages:send endpoint.

Which channels support location messages on Sinch?

RCS and WhatsApp typically support location messages through the Sinch Conversation API. Channels without location support may return an error when the message is sent.

What credentials are needed for the Sinch Conversation API?

You need CONVERSATION_PROJECT_ID, CONVERSATION_KEY_ID, CONVERSATION_KEY_SECRET, CONVERSATION_REGION, and CONVERSATION_APP_ID environment variables. These come from a Sinch Build account with a Conversation API app configured.

Why does sending a location message fail on some channels?

Failures occur when the channel does not support location_message types, coordinates fall outside valid ranges (-90 to 90 latitude, -180 to 180 longitude), or Sinch credentials are missing or invalid.

What happens if the Sinch MCP server is not available?

The skill falls back to a direct REST call, posting to https://{region}.conversation.api.sinch.com/v1/projects/{projectId}/messages:send with OAuth2 authentication using the configured environment variables.