# Remote Access & APIs

1. [**API Keys**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis/api-keys.md)- An API key in groundcover provides secure, programmatic access to the API on behalf of a [service account](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis/service-accounts.md). It inherits that account’s permissions and should be stored safely. This is also the key you need when working groundcover’s terraform provider. See:
   1. groundcover's [APIs documentation](https://docs.groundcover.com/use-groundcover/remote-access-and-apis/api-examples).
   2. groundcover's Terraform provider: <https://github.com/groundcover-com/terraform-provider-groundcover>.
2. [**Ingestion Keys**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis/ingestion-keys.md)- Ingestion Keys let sensors, integrations and browsers send observability data to your groundcover backend. These keys are the counterpart of API Keys, which are optimized for reading data or automating dashboards and monitors.
3. [**Datasources (ds) API Key**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis/querying-you-data-using-an-api.md)- A key used to connect to groundcover as a datasource, querying Clickhouse and VictoriaMetrics directly.
4. [**Grafana Service Account Token**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis/build-alerts-and-dashboards-with-grafana-terraform-provider.md)- Used to remotely configure create Grafana Alerts & Dashboards via Terraform.

\\


---

# 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.groundcover.com/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/remote-access-and-apis.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.
