# Glossary and helper

## Models definition and architecture

### CAMPAIGN (Use Case)

You can create campaigns of different types (ab, toggle, perso) and adding options to it thanks to the Remote Control API :

* Configure goals
* Configure flags
* Configure targeting

You can find the payload architecture of campaigns [here](/server-side/command-line-interface/ressource-schema.md).

### PROJECT

Campaigns are linked to a project, you can manage them thanks to the Remote Control API.\
You can find the payload architecture of project [here](https://github.com/flagship-io/Gitbook/blob/main/remote-control-api/broken-reference/README.md) .

### TARGETING KEY

You can find the payload architecture of targeting key [here](https://github.com/flagship-io/Gitbook/blob/main/remote-control-api/broken-reference/README.md).

### FLAG

You can find the payload architecture of flag [here](https://github.com/flagship-io/Gitbook/blob/main/remote-control-api/broken-reference/README.md).

### GOAL (KPI)

You can find the payload architecture of goals [here](/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-goal.md).

## Platform concepts

### CLIENT\_ID

API parameter (body). You can find your client\_id when you generate an access).\
Save it on your side then, it will not be accessible on the platform anymore.

### CLIENT\_SECRET

API parameter (body). You can find your client\_secret when you generate an access).\
Save it on your side then, it will not be accessible on the platform anymore.

### ACCOUNT\_ID

API parameter (query). ID of your account. You can find your account\_id in the Settings > Account section.

## API helpers

#### Pagination

For listing routes, you can paginate your results. To do that use the **\_page** url parameter.\
If you want to specify the max number of items per page, you can use the **\_max\_per\_page** url parameter.

```
?_page=1&_max_per_page=5
```


---

# 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.abtasty.com/server-side/remote-control-api/glossary-and-global-api-helpers.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.