> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/daton/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/sendgrid-api-keys.md).

# How to create API Keys for SendGrid

Follow the below instructions for create your Sendgrid API Keys

* Login to Sendgrid at <https://app.sendgrid.com> with your credentials.
* Expand **Settings** on the menu on the left and click on **API Keys.** You would see the list of API Keys already created for this account.

![Navigate to Sendgrid API Keys page](/files/-LqjGvKGDCBLDuopNp2-)

* Create a new API Key and name it as Daton or by any other name which identifies the purpose of this API Key.
* Select **Restricted Access** for this API Key and further select **Read Access** for each individual API. Please note that Daton would require only read access to extract the data from Sendgrid.

![Provide read access to Sendgrid APIs](/files/-LqjGvKJxVLdBY3YAiJU)

* Copy the API Key and save it someplace safe as it will not be displayed again. You are required to provide this API key while integrating Sendgrid on Daton.

&#x20;


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/sendgrid-api-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.