> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/resources/commons/user/session.md).

# Session

Extend the life of the current user session.

A user session obtained from [`user/auth`](/docs/navixy-api/user-api/resources/commons/user.md#post-user-auth) expires on an absolute deadline, **30 days after it was issued by default**, and using the session does not push that deadline back. This operation replaces the deadline with a fresh full lifetime starting now, which is how a long-running client stays signed in without asking for credentials again. The period is a per-installation setting: see [how long a session lasts](/docs/navixy-api/user-api/authentication.md#how-long-a-session-lasts).

It works only with a standard user session. Calling it with an API key returns error 4, "User or API key not found or session ended", even though the key itself is valid, because an [API key](/docs/navixy-api/user-api/resources/commons/api-keys.md) never expires and has nothing to renew.

## API actions

API base path: `/user/session`.

Operations that list no errors of their own return only the [general error codes](/docs/navixy-api/general/errors.md#error-codes).

***

## Renew session

> Extend the lifetime of the current session.\
> \
> A session expires on an absolute deadline set when it was created, \*\*30 days later by default\*\*, and using the session does not push that deadline back. This operation replaces the deadline with a fresh full lifetime starting now, so a session with 2 days left and one with 29 days left both end up with the same 30 days. The period is a per-installation setting, so treat 30 days as the default rather than a constant.\
> \
> An API key has no expiry and needs no renewal.\
> \
> \*\*Requires a session hash. An API key is rejected\*\* with error code 4, "User or API key not found or session ended", which is misleading: the key is valid, but this operation accepts standard sessions only.\
> \
> Also accepts GET with the same parameters as query-string values.

```json
{"openapi":"3.1.0","info":{"title":"Navixy Platform API","version":"1.0.0"},"tags":[{"name":"Users","description":"Operations for authenticating a user, managing their sessions, reading and updating their settings and personal information, reading audit records, and registering custom applications. All resources under the /user/ path."}],"servers":[{"url":"https://api.eu.navixy.com/v2","description":"Navixy production server on European platform"},{"url":"https://api.us.navixy.com/v2","description":"Navixy production server on American platform"},{"url":"https://api.me.navixy.com/v2","description":"Navixy production server on Middle East platform"}],"security":[{"api_key":[]}],"components":{"securitySchemes":{"api_key":{"type":"apiKey","description":"Either a user session hash or an API key, with the \"NVX \" prefix, for example \"NVX 22eac1c27af4be7b9d04da2ce1af111b\". Obtain a session hash from the userAuth operation, or create an API key from the API keys operations. A small number of operations accept a session hash only and reject an API key with error code 4; each says so in its description.","name":"Authorization","in":"header"}},"responses":{"OK":{"description":"Successful response","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean","description":"`true` if request finished successfully.","readOnly":true}}}}}},"ResponseError":{"description":"Error response object","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean","description":"Always false."},"status":{"type":"object","description":"Error status. Present only when an error occurred.","properties":{"code":{"type":"integer","description":"An error code in this API, not an HTTP code."},"description":{"type":"string","description":"An error description."}}},"errors":{"type":"array","description":"Per-parameter detail, returned with validation failures such as error code 7. A parameter name here may be an internal field name rather than the documented parameter name.","items":{"type":"object","properties":{"parameter":{"type":"string","description":"Name of the parameter that failed validation."},"error":{"type":"string","description":"What was wrong with it."}}}}}}}}}}},"paths":{"/user/session/renew":{"post":{"tags":["Users"],"summary":"Renew session","description":"Extend the lifetime of the current session.\n\nA session expires on an absolute deadline set when it was created, **30 days later by default**, and using the session does not push that deadline back. This operation replaces the deadline with a fresh full lifetime starting now, so a session with 2 days left and one with 29 days left both end up with the same 30 days. The period is a per-installation setting, so treat 30 days as the default rather than a constant.\n\nAn API key has no expiry and needs no renewal.\n\n**Requires a session hash. An API key is rejected** with error code 4, \"User or API key not found or session ended\", which is misleading: the key is valid, but this operation accepts standard sessions only.\n\nAlso accepts GET with the same parameters as query-string values.","operationId":"userSessionRenew","responses":{"200":{"description":"Session renewed","$ref":"#/components/responses/OK"},"400":{"description":"Bad request. The response body carries the API-level error code in `status.code`. Validation failures also include an `errors` array naming each offending parameter.","$ref":"#/components/responses/ResponseError"},"default":{"$ref":"#/components/responses/ResponseError"}}}}}}
```

## More in this section

#### Delivery session

| Endpoint                                                                                                                                  | Method | What it does            |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------ | ----------------------- |
| [`/user/session/delivery/create`](/docs/navixy-api/user-api/resources/commons/user/session/delivery.md#post-user-session-delivery-create) | POST   | Create delivery session |
| [`/user/session/delivery/read`](/docs/navixy-api/user-api/resources/commons/user/session/delivery.md#post-user-session-delivery-read)     | POST   | Read delivery session   |

#### Push token

| Endpoint                                                                                                                                        | Method | What it does      |
| ----------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ----------------- |
| [`/user/session/push_token/bind`](/docs/navixy-api/user-api/resources/commons/user/session/push_token.md#post-user-session-push_token-bind)     | POST   | Bind push token   |
| [`/user/session/push_token/delete`](/docs/navixy-api/user-api/resources/commons/user/session/push_token.md#post-user-session-push_token-delete) | POST   | Delete push token |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/navixy-api/user-api/resources/commons/user/session.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.