> 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/personal_info.md).

# User personal info

The billing identity stored for an account, replaced wholesale on each update.

Personal info is the billing identity stored for an account: the legal name, registration numbers, and registered address that invoices are issued against.

{% hint style="warning" %}
This operation **replaces** the stored personal info rather than merging into it. A field omitted from the request is cleared, so send every field you intend to keep.
{% endhint %}

Which fields apply depends on the account's legal type. `iec` and `legal_name` apply to `legal_entity` only. The registered address fields, `okpo_code`, `state_reg_num`, and `tin` apply to `legal_entity` or `sole_trader`.

The operation needs [plugin](/docs/navixy-api/user-api/resources/commons/plugin.md) 45 to be available to the user.

## API actions

API base path: `/user/personal_info`.

***

## Update personal info

> Replace the user's personal and address information.\
> \
> \*\*Requires the platform plugin with id 45.\*\* Without it the call fails with error code 222, plugin not found.\
> \
> \*\*This is a full replacement, not a merge.\*\* Fields omitted from the request are cleared.\
> \
> \`phone\` is required and must not be empty.

```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/personal_info/update":{"post":{"tags":["Users"],"summary":"Update personal info","description":"Replace the user's personal and address information.\n\n**Requires the platform plugin with id 45.** Without it the call fails with error code 222, plugin not found.\n\n**This is a full replacement, not a merge.** Fields omitted from the request are cleared.\n\n`phone` is required and must not be empty.","operationId":"userPersonalInfoUpdate","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","properties":{"legal_type":{"type":"string","description":"Legal type of the user.","enum":["legal_entity","sole_trader","individual"]},"first_name":{"type":"string","description":"Contact person first name."},"middle_name":{"type":"string","description":"Contact person middle name."},"last_name":{"type":"string","description":"Contact person last name."},"phone":{"type":"string","description":"Contact phone, up to 15 digits. Required and must not be empty.","maxLength":15},"post_country":{"type":"string","description":"Optional. Country part of the user's post address."},"post_index":{"type":"string","description":"Optional. Index part of the user's post address."},"post_region":{"type":"string","description":"Optional. Region part of the user's post address."},"post_city":{"type":"string","description":"Optional. City part of the user's post address."},"post_street_address":{"type":"string","description":"Optional. Street part of the user's post address."},"iec":{"type":"string","description":"Industrial Enterprises Classifier, also known as KPP. Used in Russia. For `legal_entity` only."},"legal_name":{"type":"string","description":"User legal name. For `legal_entity` only."},"okpo_code":{"type":"string","description":"Optional. All-Russian Classifier of Enterprises and Organizations, 8 or 10 characters.","maxLength":10},"state_reg_num":{"type":"string","description":"Optional. State registration number, up to 15 characters. For example EIN in the USA or OGRN in Russia.","maxLength":15},"tin":{"type":"string","description":"Taxpayer identification number."},"registered_country":{"type":"string","description":"Country part of the user's registered address."},"registered_index":{"type":"string","description":"Index part of the user's registered address."},"registered_region":{"type":"string","description":"Region part of the user's registered address."},"registered_city":{"type":"string","description":"City part of the user's registered address."},"registered_street_address":{"type":"string","description":"Street part of the user's registered address."}},"required":["legal_type","first_name","last_name","phone"]}}}},"responses":{"200":{"description":"Personal info updated","$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"}}}}}}
```

#### Errors

These errors come in addition to the [general error codes](/docs/navixy-api/general/errors.md#error-codes):

* 222 - Plugin not found, when plugin 45 is not available to the user.


---

# 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/personal_info.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.