> For the complete documentation index, see [llms.txt](https://tgtaps.gitbook.io/tgtaps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tgtaps.gitbook.io/tgtaps-docs/features/placeholders.md).

# Placeholders

Placeholders are text fields in double curly braces in a format: `{{some_text}}`. These are dynamic system values like points, energy, user level, etc.

When the application is launched, the app inserts the values into placeholders and dynamically updates it. For example, when the user [clicks the points button](/tgtaps-docs/blocks/clicker-game/click-button.md), points amount in the placeholder are increased.

Text with placeholders look like this:

<figure><img src="/files/rONAbYfQsPJEGHgHjJ3p" alt=""><figcaption></figcaption></figure>

The full list of placeholders you can see below the text field:

<figure><img src="/files/SKDAjPYHr79fwklEYAKN" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/e17J0dYJoYneCvYRVOwp" alt=""><figcaption></figcaption></figure>

There are the following placeholders:

* System-wide: like points, level name, energy. They are visible in the placeholders list.
* Placeholders from your API (see [custom API properties](/tgtaps-docs/integrations/how-to-display-ui-fields-from-your-api.md)).
* Block-wide placeholders: they are present only in some specific blocks (for example, [buy page dialog](/tgtaps-docs/blocks/system-blocks/buy-page-dialog.md)) and visible in text description:

<figure><img src="/files/Xp8to3DtIMtWb2LfACeC" alt=""><figcaption></figcaption></figure>

***

Something unclear in docs or you know how to improve article? [Message us in community!](https://docs.tgtaps.com/tgtaps-docs/readme/community)\
We will answer you and then promise to improve the article within 3 days.


---

# 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 dynamically by asking a question.

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

```
GET https://tgtaps.gitbook.io/tgtaps-docs/features/placeholders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.