# Setting Account IDs

## Overview

Every account in Trustform can have an external unique identifier (UUID). This identifier is essential for retrieving data via the API and needs to be set manually. It helps maintain consistent data and smooth integration across systems.

## Add Account ID Information <a href="#steps-to-set-an-object-uid" id="steps-to-set-an-object-uid"></a>

To assign a UUID to an account, follow these steps:

{% stepper %}
{% step %}

#### Find the UUID field

Go to the **Accounts** section and select the account you want to update. Look under the account title for the message Account ID is not set, then click the **Edit** button.

<figure><img src="/files/YcNJ70BL7rY5WyEEWFgd" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Enter the unique identifier (UUID)

Add a UUID that is unique across all accounts. You can use letters, numbers, or special characters. Click the **checkmark** next to the UUID field to confirm the changes.

<figure><img src="/files/dwCN3gxuo8ubJtc7RlnK" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### **Notes**

* A UUID is required for API access – without it, you cannot retrieve object data
* Every UUID must be unique – the platform will not allow duplicates
* You can update the UUID later if needed

## Setting Object UUIDs – Best Practice <a href="#setting-object-uids-best-practice" id="setting-object-uids-best-practice"></a>

{% hint style="info" %}
When creating or referencing objects in Trustform, it is important to use **consistent and meaningful UUIDs (unique identifiers)** to ensure data integrity and easy traceability across your systems.
{% endhint %}

**Best Practices for UUID Creation**

A consistent approach to UUIDs ensures accuracy and simplifies integration. **Here is how to keep them clean and predictable:**

* Use stable values that do not change (for example, internal database ID or official registration number)
* Keep UUIDs globally unique across your organisation or data scope
* Avoid using personal data such as names or emails for privacy reasons
* Stick to a simple format, for example acct-12345 or profile\_US\_001
* Ensure they are predictable but not easily guessable when exposed externally

**Why It Matters**

Consistent and meaningful UUIDs allow you to:

* Reference objects reliably across API calls
* Prevent duplication errors
* Integrate with external systems more efficiently


---

# 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://docs.trustform.io/guide/onboarding-and-reviewing/editor/setting-account-ids.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.