> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/integrations-and-api.md).

# API access

{% hint style="info" %}
If you are looking for **information on our existing integrations/optional couplings**, please visit [this article](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/untitled)!
{% endhint %}

## What is an API?

API stands for Application Programming Interface. With the use of an API a connection between two applications can be established, so that they can 'talk to each other'. In other words, an API is a messenger that delivers your request to the provider that you’re requesting it from and then delivers the re~~s~~ponse back to you. APIs are an accessible way to extract and share data within and across organizations. 

## What can I do with an API?

A common reason to use an API within Let's Get Digital is to connect your Let's Get Digital Admin Panel with registration software (for which there is not yet an [existing integration](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/untitled) within LGD). This way user data can be synched with Let's Get Digital, without the necessity for you to import any data manually. 

## How do I build an API with Let's Get Digital? 

**Please have a look at our** [**API documentation**](https://docs.letsgetdigital.com/)**.** Here you should find all information that you would need to build an API with Let's Get Digital. If this looks unfamiliar and strange to you, please pass this info on to your tech or development department! They will know what to do! 

For webhook information, click here: [Webhooks](https://knowledge-base.letsgetdigital.com/faq/faq-about-the-application-app/integrations-and-api/webhooks)

{% hint style="info" %}
You can add a new API token in the Admin Panel under **Settings - API tokens**
{% endhint %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/integrations-and-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.