canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-link-branding-api

# Sendgrid Twilio SendGrid Link Branding API

The Twilio SendGrid Link Branding API allows you to configure your domain settings so that all of the click-tracked links, opens, and images in your emails are served from your domain rather than `sendgrid.net`. Spam filters and recipient servers look at the links within emails to determine whether the email appear trustworthy. They use the reputation of the root domain to determine whether the li. The API exposes 10 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a branded link, retrieve all branded links. Covers 10 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Create a branded link
- Retrieve all branded links
- Update a branded link
- Delete a branded link
- Validate a branded link
- Associate a branded link with a subuser

## Use cases

### Communications Operations

Use the Twilio SendGrid Link Branding API to perform communications operations programmatically. The API provides 10 endpoints covering core functionality including create a branded link, retrieve all branded links, retrieve a branded link.

Example prompt: Call POST /v3/whitelabel/links to create a branded link

### Automated Link Branding Management

Automate link branding operations by combining multiple Twilio SendGrid Link Branding API endpoints. Agents can retrieve all branded links and then retrieve a branded link in a single workflow.

Example prompt: Call GET /v3/whitelabel/links to retrieve all branded links, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Link Branding API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create a branded link', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/whitelabel/links | Create a branded link |
| GET | /v3/whitelabel/links | Retrieve all branded links |
| GET | /v3/whitelabel/links/{id} | Retrieve a branded link |
| PATCH | /v3/whitelabel/links/{id} | Update a branded link |
| DELETE | /v3/whitelabel/links/{id} | Delete a branded link |
| POST | /v3/whitelabel/links/{id}/validate | Validate a branded link |
| POST | /v3/whitelabel/links/{link_id}/subuser | Associate a branded link with a subuser |
| GET | /v3/whitelabel/links/default | Retrieve the default branded link |

## Key resources

- **Link Branding** — Twilio SendGrid Link Branding API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Link Branding API by hand means learning its bearer API key auth, picking the right global api.sendgrid.com or EU api.eu.sendgrid.com host, and handling paging and retries yourself. Through Jentic you install once, import the Link Branding API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the branded link id in the URL path (/v3/whitelabel/links/{id}), so a rule can pin your agent to one branded link: it can read and validate that link and nothing else. You choose the operations it may call, so deleting a link with DELETE /v3/whitelabel/links/{id} is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a branded link' or 'validate a link', and Jentic returns the matching Twilio SendGrid Link Branding API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

### What authentication does the Twilio SendGrid Link Branding API use?

The Twilio SendGrid Link Branding API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a branded link with the Twilio SendGrid Link Branding API?

Yes. Use the POST /v3/whitelabel/links endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Link Branding API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a branded link through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a branded link'. Jentic returns the matching Twilio SendGrid Link Branding API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Link Branding API have?

The Twilio SendGrid Link Branding API exposes 10 endpoints covering link branding operations.

### Can I limit what my agent is allowed to do with the SendGrid Link Branding API?

Yes. Jentic One runs in your own self-hosted instance, so your rules decide which SendGrid Link Branding operations and credentials your agent may use. Because the branded link id sits in the URL path (/v3/whitelabel/links/{id}), you can pin an agent to a single link and grant only read and validate access, so it can call GET /v3/whitelabel/links/{id} and POST /v3/whitelabel/links/{id}/validate and nothing more. Destructive calls such as DELETE /v3/whitelabel/links/{id} are excluded unless you explicitly add them to the agent's allowed operations.