# Generating a secure ingest token

Apica Ascent uses an ingest token to secure the ingestion of log data from your data sources into your Apica Ascent deployment. You can generate a secure ingest token using the Apica Ascent UI and the command-line tool, [apicactl](https://github.com/ApicaSystem/apicactl).

### Obtaining an ingest token using UI

You can obtain a secure ingest token from the Account tab in the Settings page on the Apica Ascent UI. 

To begin, click on the username on the navbar, click "**Settings**", and click on the "Account" tab if you are not brought there by default. Your secure ingest token will be displayed under the **Ingest Token** field. Click the **Copy** icon next to the token to copy it to your clipboard.

![Ingest Token](/files/BXPAnNT0zE0Gn7m2Vs3d)

### Generating using apicactl

To generate a secure ingest token, do the following.

1. [Install](https://github.com/ApicaSystem/apicactl?#quickstart) and [configure](https://github.com/ApicaSystem/apicactl/blob/main/docs/config/apicactl_config.md) `apicactl`, if you haven't already.
2. Run the following command to generate a secure ingest token:

   ```bash
   apicactl get httpingestkey
   ```
3. Copy the ingest key generated by running the command above and save it in a secure location.

You can now use this ingest token while configuring Apica Ascent to ingest data from your data sources, especially while using log forwarders like Fluent Bit or Logstash.


---

# 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.apica.io/integrations/overview/generating-a-secure-ingest-token.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.