canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-marketing-campaigns-contacts-api

# Sendgrid Twilio SendGrid Marketing Campaigns Contacts API

The Twilio SendGrid Marketing Campaigns Contacts API allows you to manage all of your marketing contacts programmatically. You can also import and export contacts using this API. The Contacts API allows you to associate contacts with lists and segments; however, to manage the lists and segments themselves, see the [Lists API](https://docs.sendgrid.com/api-reference/lists/) and [Segments API](https. The API exposes 15 endpoints secured with bearer authentication.

## For AI agents

Programmatically get sample contacts, add or update a contact. Covers 15 operations with bearer authentication.

## Scope

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

## Capabilities

- Get Sample Contacts
- Add or Update a Contact
- Delete Contacts
- Query and filter Twilio SendGrid Marketing Campaigns Contacts API records by parameters
- Monitor Twilio SendGrid Marketing Campaigns Contacts API operational status and events

## Use cases

### Marketing Operations

Use the Twilio SendGrid Marketing Campaigns Contacts API to perform marketing operations programmatically. The API provides 15 endpoints covering core functionality including get sample contacts, add or update a contact, delete contacts.

Example prompt: Call GET /v3/marketing/contacts to get sample contacts

### Automated Contacts Management

Automate contacts operations by combining multiple Twilio SendGrid Marketing Campaigns Contacts API endpoints. Agents can add or update a contact and then delete contacts in a single workflow.

Example prompt: Call PUT /v3/marketing/contacts to add or update a contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Marketing Campaigns Contacts 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 'get sample contacts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v3/marketing/contacts | Get Sample Contacts |
| PUT | /v3/marketing/contacts | Add or Update a Contact |
| DELETE | /v3/marketing/contacts | Delete Contacts |
| GET | /v3/marketing/contacts/{id} | Get a Contact by ID |
| POST | /v3/marketing/contacts/batch | Get Batched Contacts by IDs |
| DELETE | /v3/marketing/contacts/{contact_id}/identifiers | Delete a Contact Identifier |
| GET | /v3/marketing/contacts/count | Get Total Contact Count |
| POST | /v3/marketing/contacts/exports | Export Contacts |

## Key resources

- **Contacts** — Twilio SendGrid Marketing Campaigns Contacts API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Marketing Campaigns Contacts API by hand means learning its bearer API key auth, pointing at the api.sendgrid.com host, and handling batch imports, exports, and retries yourself. Through Jentic you install once, import the Marketing Contacts API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the contact id in the URL path (/v3/marketing/contacts/{id}), so a rule can pin your agent to reading one contact and nothing else. You choose the operations it may call, so bulk upserts with PUT /v3/marketing/contacts or deletes are not included unless you add them.
- **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 'get a contact by id' or 'export contacts', and Jentic returns the matching Twilio SendGrid Marketing Contacts API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Twilio SendGrid Marketing Campaigns Contacts API use?

The Twilio SendGrid Marketing Campaigns Contacts 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 get sample contacts with the Twilio SendGrid Marketing Campaigns Contacts API?

Yes. Use the GET /v3/marketing/contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Marketing Campaigns Contacts 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 get sample contacts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get sample contacts'. Jentic returns the matching Twilio SendGrid Marketing Campaigns Contacts API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Marketing Campaigns Contacts API have?

The Twilio SendGrid Marketing Campaigns Contacts API exposes 15 endpoints covering contacts operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials your agent may use. Because this API puts the contact id in the URL path (GET /v3/marketing/contacts/{id}), you can pin the agent to reading a single contact and nothing else. Bulk upserts through PUT /v3/marketing/contacts and any delete operations stay off-limits unless you explicitly add them.