# POST messages/gps

<mark style="color:green;">`POST`</mark> `/messages/gps`

Updates a persona's GPS coordinates&#x20;

This is important if social media messages from the persona should come for a specific location

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `Bearer <token>`   |

**Request Body**

```
{
"persona":"3-850",
"lon":-0.096969,
"lat":51.501658,
"location":"Lambeth, London, GB",
"team_id":123456, // team_id of the Session team
"type":"team",
"ts": 1738686056
}
```

| Name       | Type   | Description                                                                                                                                    |
| ---------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| `persona`  | string | persona\_id of the persona to update                                                                                                           |
| `lng`      | number | longitude                                                                                                                                      |
| `lat`      | number | latitude                                                                                                                                       |
| `location` | string | any text will work here - there's no match of the string location to the action lon,lat. This allows fictional location "Merril Bay, Goldland" |
| `type`     | string | must be "team"                                                                                                                                 |

**Asset object**

<table><thead><tr><th width="222">Name</th><th width="172">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>type</code></td><td>string</td><td>image I video I audio I document</td></tr><tr><td><code>assetUrl</code></td><td>string</td><td>must be URL to the hosted asset</td></tr><tr><td><code>alt</code></td><td>string</td><td>description of asset</td></tr></tbody></table>

**Response**

{% tabs %}
{% tab title="200" %}

```json
{
  "message_id": "7b5a92a4-04a0-4b32-848c-1201df844cd1"
}
```

{% endtab %}

{% tab title="400" %}

```json
{
  "error": "Invalid request"
}
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpdocs.conducttr.com/feature-documentation/api/endpoint-reference/messaging/post-messages-gps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.