> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/developer-tools/sendgrid-integration-for-email-communications.md).

# SendGrid Integration for Email Communications

PeakCommerce supports **SendGrid** for sending transactional email — order confirmations, notifications, and other system messages — through your own email account, so messages come from your domain and reputation rather than a shared sender.

## What it is

SendGrid is a transactional email provider. Connecting it routes PeakCommerce's outgoing email through your SendGrid account, giving you control over sender identity, authentication, and deliverability.

## What you can do with it

* **Send all outgoing email through your own account** — once connected, every outgoing email from PeakCommerce is sent through your SendGrid account.
* **Own your deliverability** — email comes from your SendGrid sender identity, so domain authentication, reputation, and deliverability stay under your control.

## How to connect

Enable the SendGrid integration for your tenant and provide your **SendGrid API key** in your integration settings. Once it's activated and the key is in place, all outgoing email routes through SendGrid. Your implementation team can help enable and verify it during onboarding.

## Who and when

Set up by an admin during onboarding, or whenever you want transactional email to come from your own domain rather than a default sender.

## Gotchas

Both activation and a valid API key are required — email won't route through SendGrid until both are in place. Keep the API key current; a revoked or rotated key stops delivery until you update it.

See also: Marketing & CDP integrations.


---

# 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://docs.peakcommerce.com/integrations/developer-tools/sendgrid-integration-for-email-communications.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.