# How it works

To access the InEvent API, you'll need an access token. How you get this token depends on if your app is for your own usage or for the public's usage.

Generate an **Access Token** if you're using the API to access data in your own InEvent workspace.\
Use OAuth if you're building a publicly-available app that accesses other people's InEvent data (in construction).

To access endpoints that require authentication you must send the `tokenID` **query parameter** in your API call, like the example below:

```sh
curl -X GET "https://api.inevent.com/?action=api.describe&tokenID=YOUR_TOKEN_HERE"
```

Every time you see a `tokenID` parameter, it means the endpoint requires authentication and that you must use your encrypted **Access Token** as value for that parameter. Also, every token has a *scope* and we have a couple of different *scopes* you can use, and for a given *scope*, you may have different *permission levels* for that **Access Token**.


---

# 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://developers.inevent.com/authentication/how-it-works.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.