---
title: "Twilio SendGrid"
description: "Send transactional email and manage the supported SendGrid mail, contact, marketing, suppression, sender and account API families. Uses a customer restricted API key and the US API origin. Email acceptance is not deliver"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Twilio SendGrid

<p>Send transactional email and manage the supported SendGrid mail, contact, marketing, suppression, sender and account API families. Uses a customer restricted API key and the US API origin. Email acceptance is not delivery; verified senders, scopes, plans and regional residency still apply. Unsupported binary, form and schema contracts remain explicit exclusions; EU-region accounts require a separate reviewed configuration.</p>

<details data-command-index><summary>What you can do (380)</summary>
<h2>What you can do</h2>
<p>Available commands: 380 (177 read, 203 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-listaccount">Get all accounts</a> — <code>sendgrid.account_provisioning.listaccount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-createaccount">Create an account</a> — <code>sendgrid.account_provisioning.createaccount</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-deleteaccount">Delete an account</a> — <code>sendgrid.account_provisioning.deleteaccount</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-listaccountoffering">Get account offerings</a> — <code>sendgrid.account_provisioning.listaccountoffering</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-updateaccountoffering">Update account offerings</a> — <code>sendgrid.account_provisioning.updateaccountoffering</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-getaccountstate">Get an account&#39;s state</a> — <code>sendgrid.account_provisioning.getaccountstate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-updateaccountstate">Update an account&#39;s state</a> — <code>sendgrid.account_provisioning.updateaccountstate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-account_provisioning-listoffering">Get all available offerings</a> — <code>sendgrid.account_provisioning.listoffering</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-alerts-createalert">Create a new Alert</a> — <code>sendgrid.alerts.createalert</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-alerts-listalert">Retrieve all alerts</a> — <code>sendgrid.alerts.listalert</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-alerts-getalert">Retrieve a specific alert</a> — <code>sendgrid.alerts.getalert</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-alerts-deletealert">Delete an alert</a> — <code>sendgrid.alerts.deletealert</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-alerts-updatealert">Update an alert</a> — <code>sendgrid.alerts.updatealert</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-createapikey">Create API keys</a> — <code>sendgrid.api_keys.createapikey</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-listapikey">Retrieve all API Keys belonging to the authenticated user</a> — <code>sendgrid.api_keys.listapikey</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-getapikey">Retrieve an existing API Key</a> — <code>sendgrid.api_keys.getapikey</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-updateapikeyname">Update API key name</a> — <code>sendgrid.api_keys.updateapikeyname</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-updateapikey">Update API key name and scopes</a> — <code>sendgrid.api_keys.updateapikey</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-api_keys-deleteapikey">Delete API keys</a> — <code>sendgrid.api_keys.deleteapikey</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-emaildnsrecord">Email DNS records to a co-worker</a> — <code>sendgrid.domain_authentication.emaildnsrecord</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-listauthenticateddomain">List all authenticated domains</a> — <code>sendgrid.domain_authentication.listauthenticateddomain</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-authenticatedomain">Authenticate a domain</a> — <code>sendgrid.domain_authentication.authenticatedomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-getauthenticateddomain">Retrieve an authenticated domain</a> — <code>sendgrid.domain_authentication.getauthenticateddomain</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-updateauthenticateddomain">Update an authenticated domain</a> — <code>sendgrid.domain_authentication.updateauthenticateddomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-deleteauthenticateddomain">Delete an authenticated domain.</a> — <code>sendgrid.domain_authentication.deleteauthenticateddomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-associatesubuserwithdomain">Associate an authenticated domain with a given user.</a> — <code>sendgrid.domain_authentication.associatesubuserwithdomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-disassociatesubuserfromdomain">Disassociate an authenticated domain from a given user for users with up to five associated domains.</a> — <code>sendgrid.domain_authentication.disassociatesubuserfromdomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-associatesubuserwithdomainmultiple">Associate an authenticated domain with a given user, for up to five domains.</a> — <code>sendgrid.domain_authentication.associatesubuserwithdomainmultiple</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-addiptoauthenticateddomain">Add an IP to an authenticated domain</a> — <code>sendgrid.domain_authentication.addiptoauthenticateddomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-deleteipfromauthenticateddomain">Remove an IP from an authenticated domain.</a> — <code>sendgrid.domain_authentication.deleteipfromauthenticateddomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-validateauthenticateddomain">Validate a domain authentication.</a> — <code>sendgrid.domain_authentication.validateauthenticateddomain</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-listdefaultauthenticateddomain">Get the default authentication</a> — <code>sendgrid.domain_authentication.listdefaultauthenticateddomain</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-listauthenticateddomainwithuser">List the authenticated domain associated with the given user.</a> — <code>sendgrid.domain_authentication.listauthenticateddomainwithuser</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-disassociateauthenticateddomainfromuser">Disassociate an authenticated domain from a given user.</a> — <code>sendgrid.domain_authentication.disassociateauthenticateddomainfromuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-domain_authentication-listallauthenticateddomainwithuser">List all the authenticated domains associated with the given user.</a> — <code>sendgrid.domain_authentication.listallauthenticateddomainwithuser</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_activity-listmessage">Filter all messages</a> — <code>sendgrid.email_activity.listmessage</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_activity-getmessage">Filter messages by message ID</a> — <code>sendgrid.email_activity.getmessage</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_activity-requestcsv">Request CSV</a> — <code>sendgrid.email_activity.requestcsv</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_activity-downloadcsv">Download CSV</a> — <code>sendgrid.email_activity.downloadcsv</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_validation-validateemail">Validate an email</a> — <code>sendgrid.email_validation.validateemail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_validation-listemailjobforverification">Request a presigned URL and headers for Bulk Email Address Validation list upload.</a> — <code>sendgrid.email_validation.listemailjobforverification</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_validation-getvalidationsemailjobs">This request lists all of a user&#39;s Bulk Email Validation Jobs.</a> — <code>sendgrid.email_validation.getvalidationsemailjobs</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-email_validation-getemailjobforverification">This request returns a single Bulk Email Validation Job.</a> — <code>sendgrid.email_validation.getemailjobforverification</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-enforced_tls-listenforcedtlssetting">Retrieve current Enforced TLS settings.</a> — <code>sendgrid.enforced_tls.listenforcedtlssetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-enforced_tls-updateenforcedtlssetting">Update Enforced TLS settings</a> — <code>sendgrid.enforced_tls.updateenforcedtlssetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-integrations-getintegrationsbyuser">ListIntegration</a> — <code>sendgrid.integrations.getintegrationsbyuser</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-integrations-addintegration">CreateIntegration</a> — <code>sendgrid.integrations.addintegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-integrations-deleteintegration">DeleteBulkIntegration</a> — <code>sendgrid.integrations.deleteintegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-integrations-findintegrationbyid">GetIntegration</a> — <code>sendgrid.integrations.findintegrationbyid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-integrations-updateintegration">UpdateIntegration</a> — <code>sendgrid.integrations.updateintegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-listaccessactivity">Retrieve all recent access attempts</a> — <code>sendgrid.ip_access_management.listaccessactivity</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-addiptoallowlist">Add one or more IPs to the allow list</a> — <code>sendgrid.ip_access_management.addiptoallowlist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-listallowedip">Retrieve a list of currently allowed IPs</a> — <code>sendgrid.ip_access_management.listallowedip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-deleteallowedips">Remove one or more IPs from the allow list</a> — <code>sendgrid.ip_access_management.deleteallowedips</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-getallowedip">Retrieve a specific allowed IP</a> — <code>sendgrid.ip_access_management.getallowedip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_access_management-deleteallowedip">Remove a specific IP from the allowed list</a> — <code>sendgrid.ip_access_management.deleteallowedip</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-listip">Get a List of all IP Addresses on your Account</a> — <code>sendgrid.ip_address_management.listip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-getip">Get Details for an IP Address</a> — <code>sendgrid.ip_address_management.getip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-listippool">GET all IP Pools that have Associated IPs</a> — <code>sendgrid.ip_address_management.listippool</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-createippool">Create an IP Pool with a Name and IP Assignments</a> — <code>sendgrid.ip_address_management.createippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-getippool">Get Details for an IP Pool</a> — <code>sendgrid.ip_address_management.getippool</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-updateippool">Update an IP Pool Name</a> — <code>sendgrid.ip_address_management.updateippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-deleteippool">Delete IP Pool</a> — <code>sendgrid.ip_address_management.deleteippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-listipassignedtoippool">Get IPs Assigned to an IP Pool</a> — <code>sendgrid.ip_address_management.listipassignedtoippool</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-addipstoippool">Add a Batch of IPs to an IP Pool</a> — <code>sendgrid.ip_address_management.addipstoippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_address_management-deleteipsfromippool">Delete a Batch of IPs from an IP Pool</a> — <code>sendgrid.ip_address_management.deleteipsfromippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_provisioning-listaccountips">List Account IPs</a> — <code>sendgrid.ip_provisioning.listaccountips</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_provisioning-addaccountips">Add Account IPs</a> — <code>sendgrid.ip_provisioning.addaccountips</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_provisioning-removeaccountips">Remove Account IPs</a> — <code>sendgrid.ip_provisioning.removeaccountips</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_warmup-warmupip">Start warming up an IP address</a> — <code>sendgrid.ip_warmup.warmupip</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_warmup-listwarmupip">Retrieve all IPs currently in warmup</a> — <code>sendgrid.ip_warmup.listwarmupip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_warmup-getwarmupip">Retrieve the warmup status for a specific IP address</a> — <code>sendgrid.ip_warmup.getwarmupip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ip_warmup-stopipwarmup">Stop warming up an IP address</a> — <code>sendgrid.ip_warmup.stopipwarmup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-listip">Retrieve all IP addresses</a> — <code>sendgrid.ips.listip</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-createippool">Create an IP pool</a> — <code>sendgrid.ips.createippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-listippool">Retrieve all IP pools</a> — <code>sendgrid.ips.listippool</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-getippool">Retrieve all the IPs in a specified pool</a> — <code>sendgrid.ips.getippool</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-updateippool">Rename an IP pool</a> — <code>sendgrid.ips.updateippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-deleteippool">Delete an IP pool</a> — <code>sendgrid.ips.deleteippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-addiptoippool">Add an IP address to a pool</a> — <code>sendgrid.ips.addiptoippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-deleteipfromippool">Remove an IP address from a pool</a> — <code>sendgrid.ips.deleteipfromippool</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-ips-listremainingipcount">Get remaining IPs count</a> — <code>sendgrid.ips.listremainingipcount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-createbrandedlink">Create a branded link</a> — <code>sendgrid.link_branding.createbrandedlink</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-listbrandedlink">Retrieve all branded links</a> — <code>sendgrid.link_branding.listbrandedlink</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-getbrandedlink">Retrieve a branded link</a> — <code>sendgrid.link_branding.getbrandedlink</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-updatebrandedlink">Update a branded link</a> — <code>sendgrid.link_branding.updatebrandedlink</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-deletebrandedlink">Delete a branded link</a> — <code>sendgrid.link_branding.deletebrandedlink</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-validatebrandedlink">Validate a branded link</a> — <code>sendgrid.link_branding.validatebrandedlink</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-associatebrandedlinkwithsubuser">Associate a branded link with a subuser</a> — <code>sendgrid.link_branding.associatebrandedlinkwithsubuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-listdefaultbrandedlink">Retrieve the default branded link</a> — <code>sendgrid.link_branding.listdefaultbrandedlink</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-listsubuserbrandedlink">Retrieve a subuser&#39;s branded link</a> — <code>sendgrid.link_branding.listsubuserbrandedlink</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-link_branding-disassociatebrandedlinkfromsubuser">Disassociate a branded link from a subuser</a> — <code>sendgrid.link_branding.disassociatebrandedlinkfromsubuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-createcampaign">Create a Campaign</a> — <code>sendgrid.lmc_campaigns.createcampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-listcampaign">Retrieve all Campaigns</a> — <code>sendgrid.lmc_campaigns.listcampaign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-getcampaign">Retrieve a single campaign</a> — <code>sendgrid.lmc_campaigns.getcampaign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-deletecampaign">Delete a Campaign</a> — <code>sendgrid.lmc_campaigns.deletecampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-updatecampaign">Update a Campaign</a> — <code>sendgrid.lmc_campaigns.updatecampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-schedulecampaign">Schedule a Campaign</a> — <code>sendgrid.lmc_campaigns.schedulecampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-updatescheduledcampaign">Update a Scheduled Campaign</a> — <code>sendgrid.lmc_campaigns.updatescheduledcampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-getscheduledcampaign">View Scheduled Time of a Campaign</a> — <code>sendgrid.lmc_campaigns.getscheduledcampaign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-unschedulecampaign">Unschedule a Scheduled Campaign</a> — <code>sendgrid.lmc_campaigns.unschedulecampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-sendcampaign">Send a Campaign</a> — <code>sendgrid.lmc_campaigns.sendcampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_campaigns-sendtestcampaign">Send a Test Campaign</a> — <code>sendgrid.lmc_campaigns.sendtestcampaign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-createcustomfield">Create a Custom Field</a> — <code>sendgrid.lmc_contactdb.createcustomfield</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listcustomfield">Retrieve all custom fields</a> — <code>sendgrid.lmc_contactdb.listcustomfield</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getcustomfield">Retrieve a Custom Field</a> — <code>sendgrid.lmc_contactdb.getcustomfield</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deletecustomfield">Delete a Custom Field</a> — <code>sendgrid.lmc_contactdb.deletecustomfield</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-createcontactdblist">Create a List</a> — <code>sendgrid.lmc_contactdb.createcontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listcontactdblist">Retrieve all lists</a> — <code>sendgrid.lmc_contactdb.listcontactdblist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deletecontactdblists">Delete Multiple lists</a> — <code>sendgrid.lmc_contactdb.deletecontactdblists</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getcontactdblist">Retrieve a single list</a> — <code>sendgrid.lmc_contactdb.getcontactdblist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-updatecontactdblist">Update a List</a> — <code>sendgrid.lmc_contactdb.updatecontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deletecontactdblist">Delete a List</a> — <code>sendgrid.lmc_contactdb.deletecontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listrecipientsfromcontactdblist">Retrieve all recipients on a List</a> — <code>sendgrid.lmc_contactdb.listrecipientsfromcontactdblist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-addrecipientstocontactdblist">Add Multiple Recipients to a List</a> — <code>sendgrid.lmc_contactdb.addrecipientstocontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-addrecipienttocontactdblist">Add a Single Recipient to a List</a> — <code>sendgrid.lmc_contactdb.addrecipienttocontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deleterecipientfromcontactdblist">Delete a Single Recipient from a Single List</a> — <code>sendgrid.lmc_contactdb.deleterecipientfromcontactdblist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-addrecipient">Add recipients</a> — <code>sendgrid.lmc_contactdb.addrecipient</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-updaterecipient">Update Recipient</a> — <code>sendgrid.lmc_contactdb.updaterecipient</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deleterecipients">Delete Recipients</a> — <code>sendgrid.lmc_contactdb.deleterecipients</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listrecipient">Retrieve recipients</a> — <code>sendgrid.lmc_contactdb.listrecipient</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getrecipient">Retrieve a single recipient</a> — <code>sendgrid.lmc_contactdb.getrecipient</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deleterecipient">Delete a Recipient</a> — <code>sendgrid.lmc_contactdb.deleterecipient</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getrecipientlist">Retrieve the lists that a recipient is on</a> — <code>sendgrid.lmc_contactdb.getrecipientlist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getbillable">Retrieve the count of billable recipients</a> — <code>sendgrid.lmc_contactdb.getbillable</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listrecipientcount">Retrieve a Count of Recipients</a> — <code>sendgrid.lmc_contactdb.listrecipientcount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listsearchrecipient">Search recipients</a> — <code>sendgrid.lmc_contactdb.listsearchrecipient</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-searchrecipient">Search recipients</a> — <code>sendgrid.lmc_contactdb.searchrecipient</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listreservedfield">Retrieve reserved fields</a> — <code>sendgrid.lmc_contactdb.listreservedfield</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-createsegment">Create a Segment</a> — <code>sendgrid.lmc_contactdb.createsegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listsegment">Retrieve all segments</a> — <code>sendgrid.lmc_contactdb.listsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getsegment">Retrieve a segment</a> — <code>sendgrid.lmc_contactdb.getsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-updatesegment">Update a segment</a> — <code>sendgrid.lmc_contactdb.updatesegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-deletesegment">Delete a segment</a> — <code>sendgrid.lmc_contactdb.deletesegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listrecipientforsegment">Retrieve recipients on a segment</a> — <code>sendgrid.lmc_contactdb.listrecipientforsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-liststatus">Get Recipient Upload Status</a> — <code>sendgrid.lmc_contactdb.liststatus</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-exportrecipient">Export Recipients</a> — <code>sendgrid.lmc_contactdb.exportrecipient</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-listexportrecipient">Get All Existing Exports</a> — <code>sendgrid.lmc_contactdb.listexportrecipient</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_contactdb-getexportrecipient">Export Recipients Status</a> — <code>sendgrid.lmc_contactdb.getexportrecipient</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-createsender">Create a Sender Identity</a> — <code>sendgrid.lmc_senders.createsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-listsender">Get all Sender Identities</a> — <code>sendgrid.lmc_senders.listsender</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-getsender">View a Sender Identity</a> — <code>sendgrid.lmc_senders.getsender</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-updatesender">Update a Sender Identity</a> — <code>sendgrid.lmc_senders.updatesender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-deletesender">Delete a Sender Identity</a> — <code>sendgrid.lmc_senders.deletesender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-lmc_senders-resetsenderverification">Resend Sender Identity Verification</a> — <code>sendgrid.lmc_senders.resetsenderverification</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-logs-getmessagebyid">Get all details for the specified message ID.</a> — <code>sendgrid.logs.getmessagebyid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-logs-listmessagesbyfilter">Search all messages using the provided query filters.</a> — <code>sendgrid.logs.listmessagesbyfilter</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listmailsetting">Retrieve all mail settings</a> — <code>sendgrid.mail_settings.listmailsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updateaddresswhitelist">Update address whitelist mail settings</a> — <code>sendgrid.mail_settings.updateaddresswhitelist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listaddresswhitelist">Retrieve address whitelist mail settings</a> — <code>sendgrid.mail_settings.listaddresswhitelist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updatebouncepurge">Update Bounce Purge Mail Settings</a> — <code>sendgrid.mail_settings.updatebouncepurge</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listbouncepurge">Retrieve Bounce Purge Mail Settings</a> — <code>sendgrid.mail_settings.listbouncepurge</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updatefooter">Update footer mail settings</a> — <code>sendgrid.mail_settings.updatefooter</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listfooter">Retrieve footer mail settings</a> — <code>sendgrid.mail_settings.listfooter</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updateforwardbounce">Update forward bounce mail settings</a> — <code>sendgrid.mail_settings.updateforwardbounce</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listforwardbounce">Retrieve forward bounce mail settings</a> — <code>sendgrid.mail_settings.listforwardbounce</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updateforwardspam">Update forward spam mail settings</a> — <code>sendgrid.mail_settings.updateforwardspam</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listforwardspam">Retrieve forward spam mail settings</a> — <code>sendgrid.mail_settings.listforwardspam</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-updatetemplate">Update template mail settings</a> — <code>sendgrid.mail_settings.updatetemplate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail_settings-listtemplate">Retrieve legacy template mail settings</a> — <code>sendgrid.mail_settings.listtemplate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail-createmailbatch">Create a batch ID.</a> — <code>sendgrid.mail.createmailbatch</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail-getmailbatch">Validate a batch ID.</a> — <code>sendgrid.mail.getmailbatch</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mail-sendmail">Send Email with Twilio SendGrid.</a> — <code>sendgrid.mail.sendmail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-updatecontact">Add or Update a Contact</a> — <code>sendgrid.mc_contacts.updatecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-deletecontact">Delete Contacts</a> — <code>sendgrid.mc_contacts.deletecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-listcontact">Get Sample Contacts</a> — <code>sendgrid.mc_contacts.listcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-getcontact">Get a Contact by ID</a> — <code>sendgrid.mc_contacts.getcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-listbatchedcontact">Get Batched Contacts by IDs</a> — <code>sendgrid.mc_contacts.listbatchedcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-deletecontactidentifier">Delete a Contact Identifier</a> — <code>sendgrid.mc_contacts.deletecontactidentifier</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-listcontactcount">Get Total Contact Count</a> — <code>sendgrid.mc_contacts.listcontactcount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-exportcontact">Export Contacts</a> — <code>sendgrid.mc_contacts.exportcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-listexportcontact">Get All Existing Exports</a> — <code>sendgrid.mc_contacts.listexportcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-getexportcontact">Export Contacts Status</a> — <code>sendgrid.mc_contacts.getexportcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-importcontact">Import Contacts</a> — <code>sendgrid.mc_contacts.importcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-getimportcontact">Import Contacts Status</a> — <code>sendgrid.mc_contacts.getimportcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-searchcontact">Search Contacts</a> — <code>sendgrid.mc_contacts.searchcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-listcontactbyemail">Get Contacts by Emails</a> — <code>sendgrid.mc_contacts.listcontactbyemail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_contacts-getcontactbyidentifiers">Get Contacts by Identifiers</a> — <code>sendgrid.mc_contacts.getcontactbyidentifiers</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_custom_fields-createfielddefinition">Create Custom Field Definition</a> — <code>sendgrid.mc_custom_fields.createfielddefinition</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_custom_fields-listfielddefinition">Get All Field Definitions</a> — <code>sendgrid.mc_custom_fields.listfielddefinition</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_custom_fields-updatefielddefinition">Update Custom Field Definition</a> — <code>sendgrid.mc_custom_fields.updatefielddefinition</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_custom_fields-deletefielddefinition">Delete Custom Field Definition</a> — <code>sendgrid.mc_custom_fields.deletefielddefinition</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-createdesign">Create Design</a> — <code>sendgrid.mc_designs.createdesign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-listdesign">List Designs</a> — <code>sendgrid.mc_designs.listdesign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-duplicatedesign">Duplicate Design</a> — <code>sendgrid.mc_designs.duplicatedesign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-getdesign">Get Design</a> — <code>sendgrid.mc_designs.getdesign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-updatedesign">Update Design</a> — <code>sendgrid.mc_designs.updatedesign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-deletedesign">Delete Design</a> — <code>sendgrid.mc_designs.deletedesign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-listprebuiltdesign">List SendGrid Pre-built Designs</a> — <code>sendgrid.mc_designs.listprebuiltdesign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-duplicateprebuiltdesign">Duplicate SendGrid Pre-built Design</a> — <code>sendgrid.mc_designs.duplicateprebuiltdesign</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_designs-getprebuiltdesign">Get SendGrid Pre-built Design</a> — <code>sendgrid.mc_designs.getprebuiltdesign</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-createmarketinglist">Create List</a> — <code>sendgrid.mc_lists.createmarketinglist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-listmarketinglist">Get All Lists</a> — <code>sendgrid.mc_lists.listmarketinglist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-getmarketinglist">Get a List by ID</a> — <code>sendgrid.mc_lists.getmarketinglist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-updatemarketinglist">Update List</a> — <code>sendgrid.mc_lists.updatemarketinglist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-deletemarketinglist">Delete a list</a> — <code>sendgrid.mc_lists.deletemarketinglist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-deletecontact">Remove Contacts from a List</a> — <code>sendgrid.mc_lists.deletecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_lists-listcontactcount">Get List Contact Count</a> — <code>sendgrid.mc_lists.listcontactcount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-createsegment">Create Segment</a> — <code>sendgrid.mc_segments_2.0.createsegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-listsegment">Get List of Segments</a> — <code>sendgrid.mc_segments_2.0.listsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-updatesegment">Update Segment</a> — <code>sendgrid.mc_segments_2.0.updatesegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-getsegment">Get Segment by ID</a> — <code>sendgrid.mc_segments_2.0.getsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-deletesegment">Delete segment</a> — <code>sendgrid.mc_segments_2.0.deletesegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments_2-0-refreshsegment">Manually refresh a segment</a> — <code>sendgrid.mc_segments_2.0.refreshsegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments-listsegment">Get List of Segments</a> — <code>sendgrid.mc_segments.listsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments-getsegment">Get Segment by ID</a> — <code>sendgrid.mc_segments.getsegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_segments-deletesegment">Delete Segment</a> — <code>sendgrid.mc_segments.deletesegment</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-createsender">Create a Sender</a> — <code>sendgrid.mc_senders.createsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-listsender">Get a list of all Senders</a> — <code>sendgrid.mc_senders.listsender</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-getsender">Get a specific Sender</a> — <code>sendgrid.mc_senders.getsender</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-updatesender">Update a Sender</a> — <code>sendgrid.mc_senders.updatesender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-deletesender">Delete a Sender</a> — <code>sendgrid.mc_senders.deletesender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_senders-resetsenderverification">Resend a Sender verification</a> — <code>sendgrid.mc_senders.resetsenderverification</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-createsinglesend">Create Single Send</a> — <code>sendgrid.mc_singlesends.createsinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-listsinglesend">Get All Single Sends</a> — <code>sendgrid.mc_singlesends.listsinglesend</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-deletesinglesends">Bulk Delete Single Sends</a> — <code>sendgrid.mc_singlesends.deletesinglesends</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-duplicatesinglesend">Duplicate Single Send</a> — <code>sendgrid.mc_singlesends.duplicatesinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-updatesinglesend">Update Single Send</a> — <code>sendgrid.mc_singlesends.updatesinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-getsinglesend">Get Single Send by ID</a> — <code>sendgrid.mc_singlesends.getsinglesend</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-deletesinglesend">Delete Single Send by ID</a> — <code>sendgrid.mc_singlesends.deletesinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-schedulesinglesend">Schedule Single Send</a> — <code>sendgrid.mc_singlesends.schedulesinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-deletescheduledsinglesend">Delete Single Send Schedule</a> — <code>sendgrid.mc_singlesends.deletescheduledsinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-listcategory">Get All Categories</a> — <code>sendgrid.mc_singlesends.listcategory</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_singlesends-searchsinglesend">Get Single Sends Search</a> — <code>sendgrid.mc_singlesends.searchsinglesend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-listautomationstat">Get All Automation Stats</a> — <code>sendgrid.mc_stats.listautomationstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-getautomationstat">Get Automation Stats by ID</a> — <code>sendgrid.mc_stats.getautomationstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-listclicktrackingstat">Get Automation Click Tracking Stats by ID</a> — <code>sendgrid.mc_stats.listclicktrackingstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-exportautomationstat">Export Single Send Stats</a> — <code>sendgrid.mc_stats.exportautomationstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-listsinglesendstat">Get All Single Sends Stats</a> — <code>sendgrid.mc_stats.listsinglesendstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-getsinglesendstat">Get Single Send Stats by ID</a> — <code>sendgrid.mc_stats.getsinglesendstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-listsinglesendtrackingstat">Get Single Send Click Tracking Stats by ID</a> — <code>sendgrid.mc_stats.listsinglesendtrackingstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_stats-exportsinglesendstat">Export Single Send Stats</a> — <code>sendgrid.mc_stats.exportsinglesendstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-mc_test-sendtestmarketingemail">Send a Test Marketing Email</a> — <code>sendgrid.mc_test.sendtestmarketingemail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-partner-listpartnersetting">Returns a list of all partner settings.</a> — <code>sendgrid.partner.listpartnersetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-recipients_data_erasure-eraserecipientemaildata">Erase recipients&#39; email data</a> — <code>sendgrid.recipients_data_erasure.eraserecipientemaildata</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-reverse_dns-setupreversedns">Set up reverse DNS</a> — <code>sendgrid.reverse_dns.setupreversedns</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-reverse_dns-listreversedns">Retrieve all reverse DNS records</a> — <code>sendgrid.reverse_dns.listreversedns</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-reverse_dns-getreversedns">Retrieve a reverse DNS record</a> — <code>sendgrid.reverse_dns.getreversedns</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-reverse_dns-deletereversedns">Delete a reverse DNS record</a> — <code>sendgrid.reverse_dns.deletereversedns</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-reverse_dns-validatereversedns">Validate a reverse DNS record</a> — <code>sendgrid.reverse_dns.validatereversedns</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scheduled_sends-createscheduledsend">Cancel or pause a scheduled send</a> — <code>sendgrid.scheduled_sends.createscheduledsend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scheduled_sends-listscheduledsend">Retrieve all scheduled sends</a> — <code>sendgrid.scheduled_sends.listscheduledsend</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scheduled_sends-getscheduledsend">Retrieve scheduled send</a> — <code>sendgrid.scheduled_sends.getscheduledsend</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scheduled_sends-updatescheduledsend">Update a scheduled send</a> — <code>sendgrid.scheduled_sends.updatescheduledsend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scheduled_sends-deletescheduledsend">Delete a cancellation or pause from a scheduled send</a> — <code>sendgrid.scheduled_sends.deletescheduledsend</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-scopes-listscope">Retrieve a list of scopes for which this user has access.</a> — <code>sendgrid.scopes.listscope</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-seq-listengagementqualityscore">Get Engagement Quality Scores</a> — <code>sendgrid.seq.listengagementqualityscore</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-seq-listsubuserengagementqualityscore">Get Subusers&#39; Engagement Quality Scores</a> — <code>sendgrid.seq.listsubuserengagementqualityscore</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-createssocertificate">Create an SSO Certificate</a> — <code>sendgrid.sso.createssocertificate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-getssocertificate">Get an SSO Certificate</a> — <code>sendgrid.sso.getssocertificate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-updatessocertificate">Update SSO Certificate</a> — <code>sendgrid.sso.updatessocertificate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-deletessocertificate">Delete an SSO Certificate</a> — <code>sendgrid.sso.deletessocertificate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-createssointegration">Create an SSO Integration</a> — <code>sendgrid.sso.createssointegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-listssointegration">Get All SSO Integrations</a> — <code>sendgrid.sso.listssointegration</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-getssointegration">Get an SSO Integration</a> — <code>sendgrid.sso.getssointegration</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-updatessointegration">Update an SSO Integration</a> — <code>sendgrid.sso.updatessointegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-deletessointegration">Delete an SSO Integration</a> — <code>sendgrid.sso.deletessointegration</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-listssointegrationcertificate">Get All SSO Certificates by Integration</a> — <code>sendgrid.sso.listssointegrationcertificate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-sso-updatessoteammate">Edit an SSO Teammate</a> — <code>sendgrid.sso.updatessoteammate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listbrowserstat">Retrieve email statistics by browser.</a> — <code>sendgrid.stats.listbrowserstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listcategory">Retrieve all categories</a> — <code>sendgrid.stats.listcategory</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listcategorystat">Retrieve Email Statistics for Categories</a> — <code>sendgrid.stats.listcategorystat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listcategorystatsum">Retrieve sums of email stats for each category.</a> — <code>sendgrid.stats.listcategorystatsum</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listclientstat">Retrieve email statistics by client type.</a> — <code>sendgrid.stats.listclientstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-getclientstat">Retrieve stats by a specific client type.</a> — <code>sendgrid.stats.getclientstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listdevicestat">Retrieve email statistics by device type.</a> — <code>sendgrid.stats.listdevicestat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-listmailboxproviderstat">Retrieve email statistics by mailbox provider.</a> — <code>sendgrid.stats.listmailboxproviderstat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-stats-liststat">Retrieve global email statistics</a> — <code>sendgrid.stats.liststat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-listsubuser">List all Subusers</a> — <code>sendgrid.subusers.listsubuser</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-createsubuser">Create Subuser</a> — <code>sendgrid.subusers.createsubuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-updatesubuser">Enable/disable a subuser</a> — <code>sendgrid.subusers.updatesubuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-deletesubuser">Delete a subuser</a> — <code>sendgrid.subusers.deletesubuser</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-updatesubuserwebsiteaccess">Enable/Disable website access for a Subuser</a> — <code>sendgrid.subusers.updatesubuserwebsiteaccess</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-getsubusercredit">Get the Credits for a Subuser</a> — <code>sendgrid.subusers.getsubusercredit</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-updatesubusercredit">Update the Credits for a Subuser</a> — <code>sendgrid.subusers.updatesubusercredit</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-updatesubuserremainingcredit">Update the remaining credits for a Subuser</a> — <code>sendgrid.subusers.updatesubuserremainingcredit</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-updatesubuserip">Update IPs assigned to a subuser</a> — <code>sendgrid.subusers.updatesubuserip</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-listsubusermonthlystat">Retrieve the monthly email statistics for a single subuser</a> — <code>sendgrid.subusers.listsubusermonthlystat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-listreputation">Retrieve Subuser Reputations</a> — <code>sendgrid.subusers.listreputation</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-liststat">Retrieve email statistics for your subusers.</a> — <code>sendgrid.subusers.liststat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-listmonthlystat">Retrieve monthly stats for all subusers</a> — <code>sendgrid.subusers.listmonthlystat</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-subusers-liststatsum">Retrieve the totals for each email statistic metric for all subusers.</a> — <code>sendgrid.subusers.liststatsum</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-creatasmgroup">Create a new suppression group</a> — <code>sendgrid.suppressions.creatasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listasmgroup">Retrieve all suppression groups associated with the user.</a> — <code>sendgrid.suppressions.listasmgroup</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getasmgroup">Get information on a single suppression group.</a> — <code>sendgrid.suppressions.getasmgroup</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-updateasmgroup">Update a suppression group.</a> — <code>sendgrid.suppressions.updateasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deleteasmgroup">Delete a Suppression Group</a> — <code>sendgrid.suppressions.deleteasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-addsuppressiontoasmgroup">Add suppressions to a suppression group</a> — <code>sendgrid.suppressions.addsuppressiontoasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listsuppressionfromasmgroup">Retrieve all suppressions for a suppression group</a> — <code>sendgrid.suppressions.listsuppressionfromasmgroup</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletesuppressionfromasmgroup">Delete a suppression from a suppression group</a> — <code>sendgrid.suppressions.deletesuppressionfromasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-searchsuppressionfromasmgroup">Search for suppressions within a group</a> — <code>sendgrid.suppressions.searchsuppressionfromasmgroup</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listasmsuppression">Retrieve all suppressions</a> — <code>sendgrid.suppressions.listasmsuppression</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getasmsuppression">Retrieve all suppression groups for an email address</a> — <code>sendgrid.suppressions.getasmsuppression</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listsuppressionblock">Retrieve all blocks</a> — <code>sendgrid.suppressions.listsuppressionblock</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletesuppressionblocks">Delete blocks</a> — <code>sendgrid.suppressions.deletesuppressionblocks</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getsuppressionblock">Retrieve a specific block</a> — <code>sendgrid.suppressions.getsuppressionblock</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletesuppressionblock">Delete a specific block</a> — <code>sendgrid.suppressions.deletesuppressionblock</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listsuppressionbounces">Retrieve all bounces</a> — <code>sendgrid.suppressions.listsuppressionbounces</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletesuppressionbounces">Delete bounces</a> — <code>sendgrid.suppressions.deletesuppressionbounces</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getsuppressionbounces">Retrieve a Bounce</a> — <code>sendgrid.suppressions.getsuppressionbounces</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletesuppressionbounce">Delete a bounce</a> — <code>sendgrid.suppressions.deletesuppressionbounce</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listsuppressionbouncesclassifications">Retrieve bounce classification totals</a> — <code>sendgrid.suppressions.listsuppressionbouncesclassifications</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getsuppressionbouncesclassifications">Retrieve bounce classification over time by domain stats</a> — <code>sendgrid.suppressions.getsuppressionbouncesclassifications</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-createglobalsuppression">Add recipient addresses to the global suppression group.</a> — <code>sendgrid.suppressions.createglobalsuppression</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getglobalsuppression">Retrieve a Global Suppression</a> — <code>sendgrid.suppressions.getglobalsuppression</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deleteglobalsuppression">Delete a Global Suppression</a> — <code>sendgrid.suppressions.deleteglobalsuppression</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listinvalidemail">Retrieve all invalid emails</a> — <code>sendgrid.suppressions.listinvalidemail</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deleteinvalidemails">Delete invalid emails</a> — <code>sendgrid.suppressions.deleteinvalidemails</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getinvalidemail">Retrieve a specific invalid email</a> — <code>sendgrid.suppressions.getinvalidemail</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deleteinvalidemail">Delete a specific invalid email</a> — <code>sendgrid.suppressions.deleteinvalidemail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listspamreport">Retrieve all spam reports</a> — <code>sendgrid.suppressions.listspamreport</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletespamreports">Delete spam reports</a> — <code>sendgrid.suppressions.deletespamreports</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-getspamreport">Retrieve a specific spam report</a> — <code>sendgrid.suppressions.getspamreport</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-deletespamreport">Delete a specific spam report</a> — <code>sendgrid.suppressions.deletespamreport</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-suppressions-listglobalsuppression">Retrieve all global suppressions</a> — <code>sendgrid.suppressions.listglobalsuppression</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-inviteteammate">Invite teammate</a> — <code>sendgrid.teammates.inviteteammate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-listteammate">Retrieve all teammates</a> — <code>sendgrid.teammates.listteammate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-listsubuserbytemplate">Get Teammate Subuser Access</a> — <code>sendgrid.teammates.listsubuserbytemplate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-getteammate">Retrieve specific teammate</a> — <code>sendgrid.teammates.getteammate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-updateteammate">Update teammate&#39;s permissions</a> — <code>sendgrid.teammates.updateteammate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-deleteteammate">Delete teammate</a> — <code>sendgrid.teammates.deleteteammate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-listpendingteammate">Retrieve all pending teammates</a> — <code>sendgrid.teammates.listpendingteammate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-deletependingteammate">Delete pending teammate</a> — <code>sendgrid.teammates.deletependingteammate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-teammates-resendteammateinvite">Resend teammate invite</a> — <code>sendgrid.teammates.resendteammateinvite</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-createtemplate">Create a transactional template.</a> — <code>sendgrid.templates.createtemplate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-listtemplate">Retrieve paged transactional templates.</a> — <code>sendgrid.templates.listtemplate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-duplicatetemplate">Duplicate a transactional template.</a> — <code>sendgrid.templates.duplicatetemplate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-gettemplate">Retrieve a single transactional template.</a> — <code>sendgrid.templates.gettemplate</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-updatetemplate">Edit a transactional template.</a> — <code>sendgrid.templates.updatetemplate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-deletetemplate">Delete a template.</a> — <code>sendgrid.templates.deletetemplate</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-createtemplateversion">Create a new transactional template version.</a> — <code>sendgrid.templates.createtemplateversion</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-gettemplateversion">Retrieve a specific transactional template version.</a> — <code>sendgrid.templates.gettemplateversion</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-updatetemplateversion">Edit a transactional template version.</a> — <code>sendgrid.templates.updatetemplateversion</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-deletetemplateversion">Delete a transactional template version.</a> — <code>sendgrid.templates.deletetemplateversion</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-templates-activatetemplateversion">Activate a transactional template version.</a> — <code>sendgrid.templates.activatetemplateversion</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-listtrackingsetting">Retrieve Tracking Settings</a> — <code>sendgrid.tracking_settings.listtrackingsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-listclicktrackingsetting">Retrieve Click Track Settings</a> — <code>sendgrid.tracking_settings.listclicktrackingsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-updateclicktrackingsetting">Update Click Tracking Settings</a> — <code>sendgrid.tracking_settings.updateclicktrackingsetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-listgoogleanalyticstrackingsetting">Retrieve Google Analytics Settings</a> — <code>sendgrid.tracking_settings.listgoogleanalyticstrackingsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-updategoogleanalyticstrackingsetting">Update Google Analytics Settings</a> — <code>sendgrid.tracking_settings.updategoogleanalyticstrackingsetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-listopentrackingsetting">Get Open Tracking Settings</a> — <code>sendgrid.tracking_settings.listopentrackingsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-updateopentrackingsetting">Update Open Tracking Settings</a> — <code>sendgrid.tracking_settings.updateopentrackingsetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-listsubscriptiontrackingsetting">Retrieve Subscription Tracking Settings</a> — <code>sendgrid.tracking_settings.listsubscriptiontrackingsetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-tracking_settings-updatesubscriptiontrackingsetting">Update Subscription Tracking Settings</a> — <code>sendgrid.tracking_settings.updatesubscriptiontrackingsetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-listaccount">Get a user&#39;s account information.</a> — <code>sendgrid.user.listaccount</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-listcredit">Retrieve your credit balance</a> — <code>sendgrid.user.listcredit</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-listemail">Retrieve your account email address</a> — <code>sendgrid.user.listemail</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-updateemail">Update your account email address</a> — <code>sendgrid.user.updateemail</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-updatepassword">Update your password</a> — <code>sendgrid.user.updatepassword</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-listprofile">Get a user&#39;s profile</a> — <code>sendgrid.user.listprofile</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-updateprofile">Update a user&#39;s profile</a> — <code>sendgrid.user.updateprofile</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-listusername">Retrieve your username</a> — <code>sendgrid.user.listusername</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-user-updateusername">Update your username</a> — <code>sendgrid.user.updateusername</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-createverifiedsender">Create Verified Sender Request</a> — <code>sendgrid.verified_senders.createverifiedsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-listverifiedsender">Get All Verified Senders</a> — <code>sendgrid.verified_senders.listverifiedsender</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-updateverifiedsender">Edit Verified Sender</a> — <code>sendgrid.verified_senders.updateverifiedsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-deleteverifiedsender">Delete Verified Sender</a> — <code>sendgrid.verified_senders.deleteverifiedsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-listverifiedsenderdomain">Domain Warn List</a> — <code>sendgrid.verified_senders.listverifiedsenderdomain</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-resendverifiedsender">Resend Verified Sender Request</a> — <code>sendgrid.verified_senders.resendverifiedsender</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-listverifiedsenderstepscompleted">Completed Steps</a> — <code>sendgrid.verified_senders.listverifiedsenderstepscompleted</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-verified_senders-verifysendertoken">Verify Sender Request</a> — <code>sendgrid.verified_senders.verifysendertoken</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-createeventwebhook">Create a new Event Webhook</a> — <code>sendgrid.webhooks.createeventwebhook</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-listeventwebhook">Retrieve all of your Event Webhooks.</a> — <code>sendgrid.webhooks.listeventwebhook</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-getsignedeventwebhook">Get Signed Event Webhook&#39;s Public Key</a> — <code>sendgrid.webhooks.getsignedeventwebhook</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-updatesignedeventwebhook">Toggle signature verification for a single Event Webhook by ID</a> — <code>sendgrid.webhooks.updatesignedeventwebhook</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-testeventwebhook">Test an Event Webhook&#39;s settings</a> — <code>sendgrid.webhooks.testeventwebhook</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-geteventwebhook">Get the settings for a single Event Webhook.</a> — <code>sendgrid.webhooks.geteventwebhook</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-updateeventwebhook">Update a single Event Webhook by ID.</a> — <code>sendgrid.webhooks.updateeventwebhook</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-deleteeventwebhook">Delete a single Event Webhook by ID.</a> — <code>sendgrid.webhooks.deleteeventwebhook</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-listparsesetting">Retrieve all parse settings</a> — <code>sendgrid.webhooks.listparsesetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-createparsesetting">Create a parse setting</a> — <code>sendgrid.webhooks.createparsesetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-getparsesetting">Retrieve a specific parse setting</a> — <code>sendgrid.webhooks.getparsesetting</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-updateparsesetting">Update a parse setting</a> — <code>sendgrid.webhooks.updateparsesetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-deleteparsesetting">Delete a parse setting</a> — <code>sendgrid.webhooks.deleteparsesetting</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-listparsestatic">Retrieves Inbound Parse Webhook statistics.</a> — <code>sendgrid.webhooks.listparsestatic</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-createsecuritypolicy">Create a new webhook security policy</a> — <code>sendgrid.webhooks.createsecuritypolicy</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-listallsecuritypolicies">Retrieve all webhook security policies for your account</a> — <code>sendgrid.webhooks.listallsecuritypolicies</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-updatesecuritypolicy">Update an existing webhook security policy</a> — <code>sendgrid.webhooks.updatesecuritypolicy</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-getsecuritypolicy">Retrieve a specific webhook security policy</a> — <code>sendgrid.webhooks.getsecuritypolicy</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sendgrid#command-sendgrid-webhooks-deletesecuritypolicy">Delete a specific webhook security policy</a> — <code>sendgrid.webhooks.deletesecuritypolicy</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Twilio SendGrid, then enter the issued values in the connection form below.</p>
<ol>
<li>In SendGrid, open Settings → API Keys and create a Restricted Access key granting only the required endpoints. Verify sender identities or domains before enabling Mail Send. Paste the key into this connection’s SendGrid restricted API key field. This connection uses api.sendgrid.com for US-region accounts; do not use it for an EU-residency account. Start with a permitted read, then review mail recipients, marketing changes and plan limits before writes. A 202 Mail Send receipt confirms acceptance, not delivery. Save selected commands and create a separate scoped Tooluse.net API key for your AI client; keep the SendGrid key out of the MCP URL.</li>
</ol>
<p><a href="https://www.twilio.com/docs/sendgrid/ui/account-and-settings/api-keys">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>SendGrid restricted API key</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-sendgrid-account_provisioning-listaccount">
<summary><span>Get all accounts — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>listaccount</code></span></summary>
<p>Run <strong>Get all accounts</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.listaccount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>string</td>
<td>Optional</td>
<td>The last item successfully retrieved</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items to return</td>
<td><code>default: 10; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.listaccount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-createaccount">
<summary><span>Create an account — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>createaccount</code></span></summary>
<p>Run <strong>Create an account</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.createaccount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.T-Test-Account</code></td>
<td>string</td>
<td>Optional</td>
<td><strong>OPTIONAL</strong> Custom request header provided ONLY for a test account</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td>CreateAccountParams</td>
<td></td>
</tr>
<tr>
<td><code>body.profile</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/AccountProvisioningProfile&quot;</code></td>
</tr>
<tr>
<td><code>body.offerings</code></td>
<td>array</td>
<td>Required</td>
<td>List of offering names to assign to account.</td>
<td></td>
</tr>
<tr>
<td><code>body.offerings[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/AccountProvisioningOfferingV1&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.createaccount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "profile": {
      "first_name": "Sender",
      "last_name": "Wiz",
      "company_name": "Twilio SendGrid",
      "company_website": "https://sendgrid.com",
      "email": "test@test.com",
      "timezone": "Asia/Tokyo"
    },
    "offerings": [
      {
        "name": "org.ei.free.v1",
        "type": "package",
        "quantity": 1
      }
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-deleteaccount">
<summary><span>Delete an account — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>deleteaccount</code></span></summary>
<p>Run <strong>Delete an account</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.deleteaccount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.deleteaccount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg2a2bcd3ef4ab5c67d8efab91c01de2fa"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-listaccountoffering">
<summary><span>Get account offerings — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>listaccountoffering</code></span></summary>
<p>Run <strong>Get account offerings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.listaccountoffering">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.listaccountoffering">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg2a2bcd3ef4ab5c67d8efab91c01de2fa"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-updateaccountoffering">
<summary><span>Update account offerings — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>updateaccountofferin<wbr>g</code></span></summary>
<p>Run <strong>Update account offerings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.updateaccountoffering">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td>OfferingsToAdd</td>
<td></td>
</tr>
<tr>
<td><code>body.offerings</code></td>
<td>array</td>
<td>Required</td>
<td>List of offerings to assign to account.</td>
<td></td>
</tr>
<tr>
<td><code>body.offerings[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/AccountProvisioningOfferingV1&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.updateaccountoffering">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg2a2bcd3ef4ab5c67d8efab91c01de2fa"
  },
  "body": {
    "offerings": [
      {
        "name": "org.ei.free.v1",
        "type": "package",
        "quantity": 1
      }
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-getaccountstate">
<summary><span>Get an account's state — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>getaccountstate</code></span></summary>
<p>Run <strong>Get an account&#39;s state</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.getaccountstate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.getaccountstate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg2a2bcd3ef4ab5c67d8efab91c01de2fa"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-updateaccountstate">
<summary><span>Update an account's state — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>updateaccountstate</code></span></summary>
<p>Run <strong>Update an account&#39;s state</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.updateaccountstate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/AccountProvisioningStateWrite&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.updateaccountstate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg2a2bcd3ef4ab5c67d8efab91c01de2fa"
  },
  "body": {
    "state": "activated"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-account_provisioning-listoffering">
<summary><span>Get all available offerings — <code>sendgrid.<wbr>account_<wbr>provisioning.<wbr>listoffering</code></span></summary>
<p>Run <strong>Get all available offerings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.account_provisioning.listoffering">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.account_provisioning.listoffering">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-alerts-createalert">
<summary><span>Create a new Alert — <code>sendgrid.<wbr>alerts.<wbr>createalert</code></span></summary>
<p>Run <strong>Create a new Alert</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.alerts.createalert">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Type&quot;</code></td>
</tr>
<tr>
<td><code>body.type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body.email_to</code></td>
<td>string &#124; null</td>
<td>Required</td>
<td>The email address the alert will be sent to. Example: <a href="mailto:test@example.com">test@example.com</a></td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body.frequency</code></td>
<td>string</td>
<td>Optional</td>
<td>Required for stats_notification. How frequently the alert will be sent. Example: daily</td>
<td></td>
</tr>
<tr>
<td><code>body.percentage</code></td>
<td>integer</td>
<td>Optional</td>
<td>Required for usage_limit. When this usage threshold is reached, the alert will be sent. Example: 90</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.alerts.createalert">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-alerts-listalert">
<summary><span>Retrieve all alerts — <code>sendgrid.<wbr>alerts.<wbr>listalert</code></span></summary>
<p>Run <strong>Retrieve all alerts</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.alerts.listalert">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.alerts.listalert">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-alerts-getalert">
<summary><span>Retrieve a specific alert — <code>sendgrid.<wbr>alerts.<wbr>getalert</code></span></summary>
<p>Run <strong>Retrieve a specific alert</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.alerts.getalert">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.alert_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the alert you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.alerts.getalert">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "alert_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-alerts-deletealert">
<summary><span>Delete an alert — <code>sendgrid.<wbr>alerts.<wbr>deletealert</code></span></summary>
<p>Run <strong>Delete an alert</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.alerts.deletealert">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.alert_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the alert you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.alerts.deletealert">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "alert_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-alerts-updatealert">
<summary><span>Update an alert — <code>sendgrid.<wbr>alerts.<wbr>updatealert</code></span></summary>
<p>Run <strong>Update an alert</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.alerts.updatealert">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.alert_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the alert you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.email_to</code></td>
<td>string</td>
<td>Optional</td>
<td>The new email address you want your alert to be sent to. Example: <a href="mailto:test@example.com">test@example.com</a></td>
<td></td>
</tr>
<tr>
<td><code>body.frequency</code></td>
<td>string</td>
<td>Optional</td>
<td>The new frequency at which to send the stats_notification alert. Example: monthly</td>
<td></td>
</tr>
<tr>
<td><code>body.percentage</code></td>
<td>integer</td>
<td>Optional</td>
<td>The new percentage threshold at which the usage_limit alert will be sent. Example: 90</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.alerts.updatealert">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "alert_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-createapikey">
<summary><span>Create API keys — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>createapikey</code></span></summary>
<p>Run <strong>Create API keys</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.createapikey">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name you will use to describe this API Key.</td>
<td></td>
</tr>
<tr>
<td><code>body.scopes</code></td>
<td>array</td>
<td>Optional</td>
<td>The individual permissions that you are giving to this API Key.</td>
<td></td>
</tr>
<tr>
<td><code>body.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.createapikey">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-listapikey">
<summary><span>Retrieve all API Keys belonging to the authenticated user — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>listapikey</code></span></summary>
<p>Run <strong>Retrieve all API Keys belonging to the authenticated user</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.listapikey">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.listapikey">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-getapikey">
<summary><span>Retrieve an existing API Key — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>getapikey</code></span></summary>
<p>Run <strong>Retrieve an existing API Key</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.getapikey">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.api_key_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.getapikey">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "api_key_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-updateapikeyname">
<summary><span>Update API key name — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>updateapikeyname</code></span></summary>
<p>Run <strong>Update API key name</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.updateapikeyname">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.api_key_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The new name of the API Key.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.updateapikeyname">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "api_key_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-updateapikey">
<summary><span>Update API key name and scopes — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>updateapikey</code></span></summary>
<p>Run <strong>Update API key name and scopes</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.updateapikey">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.api_key_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.scopes</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.updateapikey">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "api_key_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-api_keys-deleteapikey">
<summary><span>Delete API keys — <code>sendgrid.<wbr>api_<wbr>keys.<wbr>deleteapikey</code></span></summary>
<p>Run <strong>Delete API keys</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.api_keys.deleteapikey">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.api_key_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.api_keys.deleteapikey">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "api_key_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-emaildnsrecord">
<summary><span>Email DNS records to a co-worker — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>emaildnsrecord</code></span></summary>
<p>Run <strong>Email DNS records to a co-worker</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.emaildnsrecord">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.link_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link.</td>
<td><code>minimum: 0</code></td>
</tr>
<tr>
<td><code>body.domain_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of your SendGrid domain record.</td>
<td><code>minimum: 0</code></td>
</tr>
<tr>
<td><code>body.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address to send the DNS information to.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body.message</code></td>
<td>string</td>
<td>Optional</td>
<td>A custom text block to include in the email body sent with the records.</td>
<td><code>default: &quot;Please set these DNS records in our hosting solution.&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.emaildnsrecord">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-listauthenticateddomain">
<summary><span>List all authenticated domains — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>listauthenticateddom<wbr>ain</code></span></summary>
<p>Run <strong>List all authenticated domains</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.listauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.exclude_subusers</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Exclude subuser domains from the result.</td>
<td></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td>The username associated with an authenticated domain.</td>
<td></td>
</tr>
<tr>
<td><code>query.domain</code></td>
<td>string</td>
<td>Optional</td>
<td>Search for authenticated domains.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.listauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-authenticatedomain">
<summary><span>Authenticate a domain — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>authenticatedomain</code></span></summary>
<p>Run <strong>Authenticate a domain</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.authenticatedomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.domain</code></td>
<td>string</td>
<td>Required</td>
<td>Domain being authenticated.</td>
<td></td>
</tr>
<tr>
<td><code>body.subdomain</code></td>
<td>string</td>
<td>Optional</td>
<td>The subdomain or custom return-path to use for this authenticated domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Optional</td>
<td>The username associated with this domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Optional</td>
<td>The IP addresses that will be included in the custom SPF record for this authenticated domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.custom_spf</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Specify whether to use a custom SPF or allow SendGrid to manage your SPF. This option is only available to authenticated domains set up for manual security.</td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Whether to use this authenticated domain as the fallback if no authenticated domains match the sender&#39;s domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.automatic_security</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Whether to allow SendGrid to manage your SPF records, DKIM keys, and DKIM key rotation.</td>
<td></td>
</tr>
<tr>
<td><code>body.custom_dkim_selector</code></td>
<td>string</td>
<td>Optional</td>
<td>Add a custom DKIM selector. Accepts three letters or numbers.</td>
<td></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>string</td>
<td>Optional</td>
<td>The region of the domain. Allowed values are <code>global</code> and <code>eu</code>. The default value is <code>global</code>.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.authenticatedomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-getauthenticateddomain">
<summary><span>Retrieve an authenticated domain — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>getauthenticateddoma<wbr>in</code></span></summary>
<p>Run <strong>Retrieve an authenticated domain</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.getauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.getauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-updateauthenticateddomain">
<summary><span>Update an authenticated domain — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>updateauthenticatedd<wbr>omain</code></span></summary>
<p>Run <strong>Update an authenticated domain</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.updateauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates whether this is the default authenticated domain.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body.custom_spf</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates whether to generate a custom SPF record for manual security.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.updateauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-deleteauthenticateddomain">
<summary><span>Delete an authenticated domain. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>deleteauthenticatedd<wbr>omain</code></span></summary>
<p>Run <strong>Delete an authenticated domain.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.deleteauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.deleteauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-associatesubuserwithdomain">
<summary><span>Associate an authenticated domain with a given user. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>associatesubuserwith<wbr>domain</code></span></summary>
<p>Run <strong>Associate an authenticated domain with a given user.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.associatesubuserwithdomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the authenticated domain to associate with the subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Required</td>
<td>Username to associate with the authenticated domain.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.associatesubuserwithdomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-disassociatesubuserfromdomain">
<summary><span>Disassociate an authenticated domain from a given user for users with up to five associated domains. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>disassociatesubuserf<wbr>romdomain</code></span></summary>
<p>Run <strong>Disassociate an authenticated domain from a given user for users with up to five associated domains.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.disassociatesubuserfromdomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td>Username for the subuser to find associated authenticated domain.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the authenticated domain to be disassociated with the subuser.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.disassociatesubuserfromdomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-associatesubuserwithdomainmultiple">
<summary><span>Associate an authenticated domain with a given user, for up to five domains. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>associatesubuserwith<wbr>domainmultiple</code></span></summary>
<p>Run <strong>Associate an authenticated domain with a given user, for up to five domains.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.associatesubuserwithdomainmultiple">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.domain_id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the authenticated domain to associate with the subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Required</td>
<td>Username to associate with the authenticated domain.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.associatesubuserwithdomainmultiple">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "domain_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-addiptoauthenticateddomain">
<summary><span>Add an IP to an authenticated domain — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>addiptoauthenticated<wbr>domain</code></span></summary>
<p>Run <strong>Add an IP to an authenticated domain</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.addiptoauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the domain to which you are adding an IP</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ip</code></td>
<td>string</td>
<td>Required</td>
<td>IP to associate with the domain. Used for manually specifying IPs for custom SPF.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.addiptoauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-deleteipfromauthenticateddomain">
<summary><span>Remove an IP from an authenticated domain. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>deleteipfromauthenti<wbr>cateddomain</code></span></summary>
<p>Run <strong>Remove an IP from an authenticated domain.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.deleteipfromauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the domain to delete the IP from.</td>
<td></td>
</tr>
<tr>
<td><code>path.ip</code></td>
<td>string</td>
<td>Required</td>
<td>IP to remove from the domain.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.deleteipfromauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1,
    "ip": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-validateauthenticateddomain">
<summary><span>Validate a domain authentication. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>validateauthenticate<wbr>ddomain</code></span></summary>
<p>Run <strong>Validate a domain authentication.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.validateauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>ID of the domain to validate.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.validateauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-listdefaultauthenticateddomain">
<summary><span>Get the default authentication — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>listdefaultauthentic<wbr>ateddomain</code></span></summary>
<p>Run <strong>Get the default authentication</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.listdefaultauthenticateddomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.domain</code></td>
<td>string</td>
<td>Optional</td>
<td>The domain to find a default authentication.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.listdefaultauthenticateddomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-listauthenticateddomainwithuser">
<summary><span>List the authenticated domain associated with the given user. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>listauthenticateddom<wbr>ainwithuser</code></span></summary>
<p>Run <strong>List the authenticated domain associated with the given user.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.listauthenticateddomainwithuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Required</td>
<td>Username for the subuser to find associated authenticated domain.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.listauthenticateddomainwithuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-disassociateauthenticateddomainfromuser">
<summary><span>Disassociate an authenticated domain from a given user. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>disassociateauthenti<wbr>cateddomainfromuser</code></span></summary>
<p>Run <strong>Disassociate an authenticated domain from a given user.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.disassociateauthenticateddomainfromuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td>Username for the subuser to find associated authenticated domain.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.disassociateauthenticateddomainfromuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-domain_authentication-listallauthenticateddomainwithuser">
<summary><span>List all the authenticated domains associated with the given user. — <code>sendgrid.<wbr>domain_<wbr>authentication.<wbr>listallauthenticated<wbr>domainwithuser</code></span></summary>
<p>Run <strong>List all the authenticated domains associated with the given user.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.domain_authentication.listallauthenticateddomainwithuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Required</td>
<td>Username for the subuser to find associated authenticated domains.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.domain_authentication.listallauthenticateddomainwithuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_activity-listmessage">
<summary><span>Filter all messages — <code>sendgrid.<wbr>email_<wbr>activity.<wbr>listmessage</code></span></summary>
<p>Run <strong>Filter all messages</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_activity.listmessage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.query</code></td>
<td>string</td>
<td>Required</td>
<td>Use the query syntax to filter your email activity. Combine up to 160 filter conditions per request.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>number</td>
<td>Optional</td>
<td>The number of messages returned. This parameter must be greater than 0 and less than or equal to 1000</td>
<td><code>default: 10; minimum: 1; maximum: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_activity.listmessage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "query": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_activity-getmessage">
<summary><span>Filter messages by message ID — <code>sendgrid.<wbr>email_<wbr>activity.<wbr>getmessage</code></span></summary>
<p>Run <strong>Filter messages by message ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_activity.getmessage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.msg_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the message you are requesting details for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_activity.getmessage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "msg_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_activity-requestcsv">
<summary><span>Request CSV — <code>sendgrid.<wbr>email_<wbr>activity.<wbr>requestcsv</code></span></summary>
<p>Run <strong>Request CSV</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_activity.requestcsv">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.query</code></td>
<td>string</td>
<td>Optional</td>
<td>Uses a SQL like syntax to indicate which messages to include in the CSV</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_activity.requestcsv">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_activity-downloadcsv">
<summary><span>Download CSV — <code>sendgrid.<wbr>email_<wbr>activity.<wbr>downloadcsv</code></span></summary>
<p>Run <strong>Download CSV</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_activity.downloadcsv">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.download_uuid</code></td>
<td>string</td>
<td>Required</td>
<td>UUID used to locate the download csv request entry in the DB.  This is the UUID provided in the email sent to the user when their csv file is ready to download</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_activity.downloadcsv">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "download_uuid": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_validation-validateemail">
<summary><span>Validate an email — <code>sendgrid.<wbr>email_<wbr>validation.<wbr>validateemail</code></span></summary>
<p>Run <strong>Validate an email</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_validation.validateemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address that you want to validate.</td>
<td></td>
</tr>
<tr>
<td><code>body.source</code></td>
<td>string</td>
<td>Optional</td>
<td>A one-word classifier for where this validation originated.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_validation.validateemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_validation-listemailjobforverification">
<summary><span>Request a presigned URL and headers for Bulk Email Address Validation list upload. — <code>sendgrid.<wbr>email_<wbr>validation.<wbr>listemailjobforverif<wbr>ication</code></span></summary>
<p>Run <strong>Request a presigned URL and headers for Bulk Email Address Validation list upload.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_validation.listemailjobforverification">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/FileType&quot;</code></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_validation.listemailjobforverification">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_validation-getvalidationsemailjobs">
<summary><span>This request lists all of a user's Bulk Email Validation Jobs. — <code>sendgrid.<wbr>email_<wbr>validation.<wbr>getvalidationsemailj<wbr>obs</code></span></summary>
<p>Run <strong>This request lists all of a user&#39;s Bulk Email Validation Jobs.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_validation.getvalidationsemailjobs">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_validation.getvalidationsemailjobs">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-email_validation-getemailjobforverification">
<summary><span>This request returns a single Bulk Email Validation Job. — <code>sendgrid.<wbr>email_<wbr>validation.<wbr>getemailjobforverifi<wbr>cation</code></span></summary>
<p>Run <strong>This request returns a single Bulk Email Validation Job.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.email_validation.getemailjobforverification">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Bulk Email Address Validation Job you wish to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.email_validation.getemailjobforverification">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-enforced_tls-listenforcedtlssetting">
<summary><span>Retrieve current Enforced TLS settings. — <code>sendgrid.<wbr>enforced_<wbr>tls.<wbr>listenforcedtlssetti<wbr>ng</code></span></summary>
<p>Run <strong>Retrieve current Enforced TLS settings.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.enforced_tls.listenforcedtlssetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.enforced_tls.listenforcedtlssetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-enforced_tls-updateenforcedtlssetting">
<summary><span>Update Enforced TLS settings — <code>sendgrid.<wbr>enforced_<wbr>tls.<wbr>updateenforcedtlsset<wbr>ting</code></span></summary>
<p>Run <strong>Update Enforced TLS settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.enforced_tls.updateenforcedtlssetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/EnforcedTlsRequestResponse&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.enforced_tls.updateenforcedtlssetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-integrations-getintegrationsbyuser">
<summary><span>ListIntegration — <code>sendgrid.<wbr>integrations.<wbr>getintegrationsbyuse<wbr>r</code></span></summary>
<p>Run <strong>ListIntegration</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.integrations.getintegrationsbyuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.integrations.getintegrationsbyuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-integrations-addintegration">
<summary><span>CreateIntegration — <code>sendgrid.<wbr>integrations.<wbr>addintegration</code></span></summary>
<p>Run <strong>CreateIntegration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.integrations.addintegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/IntegrationInput&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.integrations.addintegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "destination": "Segment",
    "filters": {
      "email_events": []
    },
    "properties": {
      "write_key": "1234-abc",
      "destination_region": "EU"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-integrations-deleteintegration">
<summary><span>DeleteBulkIntegration — <code>sendgrid.<wbr>integrations.<wbr>deleteintegration</code></span></summary>
<p>Run <strong>DeleteBulkIntegration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.integrations.deleteintegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Required</td>
<td>Comma-delimited Integration IDs for the Integrations to delete.</td>
<td></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/Id&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.integrations.deleteintegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "ids": []
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-integrations-findintegrationbyid">
<summary><span>GetIntegration — <code>sendgrid.<wbr>integrations.<wbr>findintegrationbyid</code></span></summary>
<p>Run <strong>GetIntegration</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.integrations.findintegrationbyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Integration you would like to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.integrations.findintegrationbyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-integrations-updateintegration">
<summary><span>UpdateIntegration — <code>sendgrid.<wbr>integrations.<wbr>updateintegration</code></span></summary>
<p>Run <strong>UpdateIntegration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.integrations.updateintegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Integration you would like to update.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/IntegrationPatch&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.integrations.updateintegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  },
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-listaccessactivity">
<summary><span>Retrieve all recent access attempts — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>listaccessactivity</code></span></summary>
<p>Run <strong>Retrieve all recent access attempts</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.listaccessactivity">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limits the number of IPs to return.</td>
<td><code>default: 20</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.listaccessactivity">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-addiptoallowlist">
<summary><span>Add one or more IPs to the allow list — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>addiptoallowlist</code></span></summary>
<p>Run <strong>Add one or more IPs to the allow list</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.addiptoallowlist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Required</td>
<td>An array containing the IP(s) you want to allow.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ips[].ip</code></td>
<td>string</td>
<td>Required</td>
<td>An IP address that you want to allow.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.addiptoallowlist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-listallowedip">
<summary><span>Retrieve a list of currently allowed IPs — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>listallowedip</code></span></summary>
<p>Run <strong>Retrieve a list of currently allowed IPs</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.listallowedip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.listallowedip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-deleteallowedips">
<summary><span>Remove one or more IPs from the allow list — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>deleteallowedips</code></span></summary>
<p>Run <strong>Remove one or more IPs from the allow list</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.deleteallowedips">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of the IDs of the IP address that you want to remove from your allow list.</td>
<td></td>
</tr>
<tr>
<td><code>body.ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.deleteallowedips">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-getallowedip">
<summary><span>Retrieve a specific allowed IP — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>getallowedip</code></span></summary>
<p>Run <strong>Retrieve a specific allowed IP</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.getallowedip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.rule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the allowed IP address that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.getallowedip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "rule_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_access_management-deleteallowedip">
<summary><span>Remove a specific IP from the allowed list — <code>sendgrid.<wbr>ip_<wbr>access_<wbr>management.<wbr>deleteallowedip</code></span></summary>
<p>Run <strong>Remove a specific IP from the allowed list</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_access_management.deleteallowedip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.rule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the allowed IP address that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_access_management.deleteallowedip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "rule_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-listip">
<summary><span>Get a List of all IP Addresses on your Account — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>listip</code></span></summary>
<p>Run <strong>Get a List of all IP Addresses on your Account</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.listip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies an IP address. The <code>ip</code> query parameter can be used to filter results by IP address.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies the number of results to be returned by the API. This parameter can be used in combination with the <code>before_key</code> or <code>after_key</code> parameters to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.after_key</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies which items to be returned by the API. When the <code>after_key</code> is specified, the API will return items beginning from the first item after the item specified. This parameter can be used in combination with <code>limit</code> to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.before_key</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies which items to be returned by the API. When the <code>before_key</code> is specified, the API will return items beginning from the first item before the item specified. This parameter can be used in combination with <code>limit</code> to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.is_leased</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates whether an IP address is leased from Twilio SendGrid. If <code>false</code>, the IP address is not a Twilio SendGrid IP; it is a customer&#39;s own IP that has been added to their Twilio SendGrid account.</td>
<td></td>
</tr>
<tr>
<td><code>query.is_enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if the IP address is billed and able to send email. This parameter applies to non-Twilio SendGrid APIs that been added to your Twilio SendGrid account. This parameter&#39;s value is <code>null</code> for Twilio SendGrid IP addresses.</td>
<td></td>
</tr>
<tr>
<td><code>query.is_parent_assigned</code></td>
<td>boolean</td>
<td>Optional</td>
<td>A parent must be assigned to an IP address before the parent can send mail from the IP and before the address can be assigned to an IP pool. Set this parameter value to true to allow the parent to send mail from the IP and make the IP eligible for IP pool assignment using the IP pool endpoints.</td>
<td></td>
</tr>
<tr>
<td><code>query.pool</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies the unique ID for an IP Pool. When included, only IP addresses belonging to the specified Pool will be returned.</td>
<td></td>
</tr>
<tr>
<td><code>query.start_added_at</code></td>
<td>integer</td>
<td>Optional</td>
<td>The <code>start_added_at</code> and <code>end_added_at</code> parameters are used to set a time window. IP addresses that were added to your account in the specified time window will be returned. The <code>start_added_at</code> parameter sets the beginning of the time window.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_added_at</code></td>
<td>integer</td>
<td>Optional</td>
<td>The <code>start_added_at</code> and <code>end_added_at</code> parameters are used to set a time window. IP addresses that were added to your account in the specified time window will be returned. The <code>end_added_at</code> parameter sets the end of the time window.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td>Allowed values are <code>all</code>, <code>eu</code>, and <code>us</code>. If you provide a specific region, results will include all pools that have at least one IP in the filtered region. If <code>all</code>, pools with at least one IP (regardless of region) will be returned. If the <code>region</code> filter is not provided, the query returns all pools, including empty ones.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region7&quot;</code></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Boolean indicating whether or not to return the IP Pool&#39;s region information in the response.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.listip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-getip">
<summary><span>Get Details for an IP Address — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>getip</code></span></summary>
<p>Run <strong>Get Details for an IP Address</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.getip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ip</code></td>
<td>string</td>
<td>Required</td>
<td>The <code>ip</code> path parameter specifies an IP address to make the request against.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Boolean indicating whether or not to return the IP Pool&#39;s region information in the response.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.getip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ip": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-listippool">
<summary><span>GET all IP Pools that have Associated IPs — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>listippool</code></span></summary>
<p>Run <strong>GET all IP Pools that have Associated IPs</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.listippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies the number of results to be returned by the API. This parameter can be used in combination with the <code>before_key</code> or <code>after_key</code> parameters to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.after_key</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies which items to be returned by the API. When the <code>after_key</code> is specified, the API will return items beginning from the first item after the item specified. This parameter can be used in combination with <code>limit</code> to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies an IP address. The <code>ip</code> query parameter can be used to filter results by IP address.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td>Allowed values are <code>all</code>, <code>eu</code>, and <code>us</code>. If you provide a specific region, results will include all pools that have at least one IP in the filtered region. If <code>all</code>, pools with at least one IP (regardless of region) will be returned. If the <code>region</code> filter is not provided, the query returns all pools, including empty ones.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region7&quot;</code></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Boolean indicating whether or not to return the IP Pool&#39;s region information in the response.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.listippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-createippool">
<summary><span>Create an IP Pool with a Name and IP Assignments — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>createippool</code></span></summary>
<p>Run <strong>Create an IP Pool with a Name and IP Assignments</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.createippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name to assign to the IP Pool. An IP Pool name cannot begin with a space or period.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of IP addresses to assign to the IP Pool. All assignments must succeed.</td>
<td><code>maxItems: 100</code></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.createippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-getippool">
<summary><span>Get Details for an IP Pool — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>getippool</code></span></summary>
<p>Run <strong>Get Details for an IP Pool</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.getippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Boolean indicating whether or not to return the IP Pool&#39;s region information in the response.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.getippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-updateippool">
<summary><span>Update an IP Pool Name — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>updateippool</code></span></summary>
<p>Run <strong>Update an IP Pool Name</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.updateippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name to assign to the IP Pool. An IP Pool name cannot begin with a space or period.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.updateippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-deleteippool">
<summary><span>Delete IP Pool — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>deleteippool</code></span></summary>
<p>Run <strong>Delete IP Pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.deleteippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.deleteippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-listipassignedtoippool">
<summary><span>Get IPs Assigned to an IP Pool — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>listipassignedtoippo<wbr>ol</code></span></summary>
<p>Run <strong>Get IPs Assigned to an IP Pool</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.listipassignedtoippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies the number of results to be returned by the API. This parameter can be used in combination with the <code>before_key</code> or <code>after_key</code> parameters to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.after_key</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies which items to be returned by the API. When the <code>after_key</code> is specified, the API will return items beginning from the first item after the item specified. This parameter can be used in combination with <code>limit</code> to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Boolean indicating whether or not to return the IP Pool&#39;s region information in the response.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.listipassignedtoippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-addipstoippool">
<summary><span>Add a Batch of IPs to an IP Pool — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>addipstoippool</code></span></summary>
<p>Run <strong>Add a Batch of IPs to an IP Pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.addipstoippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Required</td>
<td>An array of IP addresses to assign to the specified IP Pool. All assignments must succeed.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.addipstoippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_address_management-deleteipsfromippool">
<summary><span>Delete a Batch of IPs from an IP Pool — <code>sendgrid.<wbr>ip_<wbr>address_<wbr>management.<wbr>deleteipsfromippool</code></span></summary>
<p>Run <strong>Delete a Batch of IPs from an IP Pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_address_management.deleteipsfromippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.poolid</code></td>
<td>string</td>
<td>Required</td>
<td>Specifies the unique ID for an IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Required</td>
<td>An array of IP addresses to remove from the specified IP Pool.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_address_management.deleteipsfromippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "poolid": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_provisioning-listaccountips">
<summary><span>List Account IPs — <code>sendgrid.<wbr>ip_<wbr>provisioning.<wbr>listaccountips</code></span></summary>
<p>Run <strong>List Account IPs</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_provisioning.listaccountips">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of items to return</td>
<td><code>default: 10; minimum: 1; maximum: 5000</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>string</td>
<td>Optional</td>
<td>The last item successfully retrieved</td>
<td><code>format: &quot;ipv4&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_provisioning.listaccountips">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg1a2bcd3ef4ab5c67d8efab91c01de2fa"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_provisioning-addaccountips">
<summary><span>Add Account IPs — <code>sendgrid.<wbr>ip_<wbr>provisioning.<wbr>addaccountips</code></span></summary>
<p>Run <strong>Add Account IPs</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_provisioning.addaccountips">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td>Request to add IP addresses to an account. Maximum of 10 IPs per request, all from the same region.</td>
<td></td>
</tr>
<tr>
<td><code>body.count</code></td>
<td>integer</td>
<td>Required</td>
<td>Number of IPs to add (maximum 10 per request)</td>
<td><code>minimum: 1; maximum: 10</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region1&quot;</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_provisioning.addaccountips">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg1a2bcd3ef4ab5c67d8efab91c01de2fa"
  },
  "body": {
    "count": 2,
    "region": "us"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_provisioning-removeaccountips">
<summary><span>Remove Account IPs — <code>sendgrid.<wbr>ip_<wbr>provisioning.<wbr>removeaccountips</code></span></summary>
<p>Run <strong>Remove Account IPs</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_provisioning.removeaccountips">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.accountID</code></td>
<td>string</td>
<td>Required</td>
<td>Twilio SendGrid account ID</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td>RemoveAccountIPsRequest</td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Required</td>
<td>List of specific IP addresses to remove (maximum 10 per request)</td>
<td><code>minItems: 1; maxItems: 10</code></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;ipv4&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_provisioning.removeaccountips">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "accountID": "sg1a2bcd3ef4ab5c67d8efab91c01de2fa"
  },
  "body": {
    "ips": [
      "174.0.0.3",
      "192.0.0.1"
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_warmup-warmupip">
<summary><span>Start warming up an IP address — <code>sendgrid.<wbr>ip_<wbr>warmup.<wbr>warmupip</code></span></summary>
<p>Run <strong>Start warming up an IP address</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_warmup.warmupip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>The IP address that you want to begin warming up.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_warmup.warmupip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_warmup-listwarmupip">
<summary><span>Retrieve all IPs currently in warmup — <code>sendgrid.<wbr>ip_<wbr>warmup.<wbr>listwarmupip</code></span></summary>
<p>Run <strong>Retrieve all IPs currently in warmup</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_warmup.listwarmupip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_warmup.listwarmupip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_warmup-getwarmupip">
<summary><span>Retrieve the warmup status for a specific IP address — <code>sendgrid.<wbr>ip_<wbr>warmup.<wbr>getwarmupip</code></span></summary>
<p>Run <strong>Retrieve the warmup status for a specific IP address</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_warmup.getwarmupip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ip_address</code></td>
<td>string</td>
<td>Required</td>
<td>The IP address that you want to retrieve the warmup status for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_warmup.getwarmupip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ip_address": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ip_warmup-stopipwarmup">
<summary><span>Stop warming up an IP address — <code>sendgrid.<wbr>ip_<wbr>warmup.<wbr>stopipwarmup</code></span></summary>
<p>Run <strong>Stop warming up an IP address</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ip_warmup.stopipwarmup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ip_address</code></td>
<td>string</td>
<td>Required</td>
<td>The IP address that you want to retrieve the warmup status for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ip_warmup.stopipwarmup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ip_address": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-listip">
<summary><span>Retrieve all IP addresses — <code>sendgrid.<wbr>ips.<wbr>listip</code></span></summary>
<p>Run <strong>Retrieve all IP addresses</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.listip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>The IP address to get</td>
<td></td>
</tr>
<tr>
<td><code>query.exclude_whitelabels</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Should we exclude reverse DNS records (whitelabels)?</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td><code>default: 10; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.subuser</code></td>
<td>string</td>
<td>Optional</td>
<td>The subuser you are requesting for.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td>The direction to sort the results.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByDirection&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.listip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-createippool">
<summary><span>Create an IP pool — <code>sendgrid.<wbr>ips.<wbr>createippool</code></span></summary>
<p>Run <strong>Create an IP pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.createippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of your new IP pool.</td>
<td><code>maxLength: 64</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.createippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-listippool">
<summary><span>Retrieve all IP pools — <code>sendgrid.<wbr>ips.<wbr>listippool</code></span></summary>
<p>Run <strong>Retrieve all IP pools</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.listippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.listippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-getippool">
<summary><span>Retrieve all the IPs in a specified pool — <code>sendgrid.<wbr>ips.<wbr>getippool</code></span></summary>
<p>Run <strong>Retrieve all the IPs in a specified pool</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.getippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.pool_name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the IP pool that you want to retrieve the IP addresses for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.getippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "pool_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-updateippool">
<summary><span>Rename an IP pool — <code>sendgrid.<wbr>ips.<wbr>updateippool</code></span></summary>
<p>Run <strong>Rename an IP pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.updateippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.pool_name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the IP pool that you want to retrieve the IP addresses for.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The new name for your IP pool.</td>
<td><code>maxLength: 64</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.updateippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "pool_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-deleteippool">
<summary><span>Delete an IP pool — <code>sendgrid.<wbr>ips.<wbr>deleteippool</code></span></summary>
<p>Run <strong>Delete an IP pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.deleteippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.pool_name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the IP pool that you want to retrieve the IP addresses for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.deleteippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "pool_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-addiptoippool">
<summary><span>Add an IP address to a pool — <code>sendgrid.<wbr>ips.<wbr>addiptoippool</code></span></summary>
<p>Run <strong>Add an IP address to a pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.addiptoippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.pool_name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the IP pool you want to add the address to. If the name contains spaces, they must be URL encoded (e.g., &quot;Test Pool&quot; becomes &quot;Test%20Pool&quot;).</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>The IP address that you want to add to the named pool.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.addiptoippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "pool_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-deleteipfromippool">
<summary><span>Remove an IP address from a pool — <code>sendgrid.<wbr>ips.<wbr>deleteipfromippool</code></span></summary>
<p>Run <strong>Remove an IP address from a pool</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.deleteipfromippool">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.pool_name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the IP pool that you are removing the IP address from.</td>
<td></td>
</tr>
<tr>
<td><code>path.ip</code></td>
<td>string</td>
<td>Required</td>
<td>The IP address that you wish to remove.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.deleteipfromippool">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "pool_name": "example",
    "ip": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-ips-listremainingipcount">
<summary><span>Get remaining IPs count — <code>sendgrid.<wbr>ips.<wbr>listremainingipcount</code></span></summary>
<p>Run <strong>Get remaining IPs count</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.ips.listremainingipcount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.ips.listremainingipcount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-createbrandedlink">
<summary><span>Create a branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>createbrandedlink</code></span></summary>
<p>Run <strong>Create a branded link</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.createbrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.domain</code></td>
<td>string</td>
<td>Required</td>
<td>The root domain for the subdomain that you are creating the link branding for. This should match your FROM email address.</td>
<td></td>
</tr>
<tr>
<td><code>body.subdomain</code></td>
<td>string</td>
<td>Optional</td>
<td>The subdomain to create the link branding for. Must be different from the subdomain you used for authenticating your domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Default&quot;</code></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region&quot;</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;us&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.createbrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-listbrandedlink">
<summary><span>Retrieve all branded links — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>listbrandedlink</code></span></summary>
<p>Run <strong>Retrieve all branded links</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.listbrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limits the number of results returned per page.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.listbrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-getbrandedlink">
<summary><span>Retrieve a branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>getbrandedlink</code></span></summary>
<p>Run <strong>Retrieve a branded link</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.getbrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.getbrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-updatebrandedlink">
<summary><span>Update a branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>updatebrandedlink</code></span></summary>
<p>Run <strong>Update a branded link</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.updatebrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Default1&quot;</code></td>
</tr>
<tr>
<td><code>body.default</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.updatebrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-deletebrandedlink">
<summary><span>Delete a branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>deletebrandedlink</code></span></summary>
<p>Run <strong>Delete a branded link</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.deletebrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.deletebrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-validatebrandedlink">
<summary><span>Validate a branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>validatebrandedlink</code></span></summary>
<p>Run <strong>Validate a branded link</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.validatebrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link that you want to validate.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.validatebrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-associatebrandedlinkwithsubuser">
<summary><span>Associate a branded link with a subuser — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>associatebrandedlink<wbr>withsubuser</code></span></summary>
<p>Run <strong>Associate a branded link with a subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.associatebrandedlinkwithsubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.link_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the branded link you want to associate.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Optional</td>
<td>The username of the subuser account that you want to associate the branded link with.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.associatebrandedlinkwithsubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "link_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-listdefaultbrandedlink">
<summary><span>Retrieve the default branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>listdefaultbrandedli<wbr>nk</code></span></summary>
<p>Run <strong>Retrieve the default branded link</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.listdefaultbrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.domain</code></td>
<td>string</td>
<td>Optional</td>
<td>The domain to match against when finding the default branded link.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.listdefaultbrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-listsubuserbrandedlink">
<summary><span>Retrieve a subuser's branded link — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>listsubuserbrandedli<wbr>nk</code></span></summary>
<p>Run <strong>Retrieve a subuser&#39;s branded link</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.listsubuserbrandedlink">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the subuser to retrieve associated branded links for.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.listsubuserbrandedlink">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-link_branding-disassociatebrandedlinkfromsubuser">
<summary><span>Disassociate a branded link from a subuser — <code>sendgrid.<wbr>link_<wbr>branding.<wbr>disassociatebrandedl<wbr>inkfromsubuser</code></span></summary>
<p>Run <strong>Disassociate a branded link from a subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.link_branding.disassociatebrandedlinkfromsubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the subuser account that you want to disassociate a branded link from.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.link_branding.disassociatebrandedlinkfromsubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-createcampaign">
<summary><span>Create a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>createcampaign</code></span></summary>
<p>Run <strong>Create a Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.createcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/PostCampaignsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.createcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-listcampaign">
<summary><span>Retrieve all Campaigns — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>listcampaign</code></span></summary>
<p>Run <strong>Retrieve all Campaigns</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.listcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td><code>default: 10; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.listcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-getcampaign">
<summary><span>Retrieve a single campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>getcampaign</code></span></summary>
<p>Run <strong>Retrieve a single campaign</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.getcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the campaign you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.getcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-deletecampaign">
<summary><span>Delete a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>deletecampaign</code></span></summary>
<p>Run <strong>Delete a Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.deletecampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the campaign you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.deletecampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-updatecampaign">
<summary><span>Update a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>updatecampaign</code></span></summary>
<p>Run <strong>Update a Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.updatecampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the campaign you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Update a Campaign request</td>
<td></td>
</tr>
<tr>
<td><code>body.title</code></td>
<td>string</td>
<td>Required</td>
<td>The title of the campaign.</td>
<td></td>
</tr>
<tr>
<td><code>body.subject</code></td>
<td>string</td>
<td>Required</td>
<td>The subject line for your campaign.</td>
<td></td>
</tr>
<tr>
<td><code>body.categories</code></td>
<td>array</td>
<td>Required</td>
<td>The categories you want to tag on this campaign.</td>
<td></td>
</tr>
<tr>
<td><code>body.categories[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.html_content</code></td>
<td>string</td>
<td>Required</td>
<td>The HTML content of this campaign.</td>
<td></td>
</tr>
<tr>
<td><code>body.plain_content</code></td>
<td>string</td>
<td>Required</td>
<td>The plain content of this campaign.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.updatecampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-schedulecampaign">
<summary><span>Schedule a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>schedulecampaign</code></span></summary>
<p>Run <strong>Schedule a Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.schedulecampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Schedule a Campaign request</td>
<td></td>
</tr>
<tr>
<td><code>body.send_at</code></td>
<td>integer</td>
<td>Required</td>
<td>The unix timestamp for the date and time you would like your campaign to be sent out.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.schedulecampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-updatescheduledcampaign">
<summary><span>Update a Scheduled Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>updatescheduledcampa<wbr>ign</code></span></summary>
<p>Run <strong>Update a Scheduled Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.updatescheduledcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Update a Scheduled Campaign request</td>
<td></td>
</tr>
<tr>
<td><code>body.send_at</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.updatescheduledcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-getscheduledcampaign">
<summary><span>View Scheduled Time of a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>getscheduledcampaign</code></span></summary>
<p>Run <strong>View Scheduled Time of a Campaign</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.getscheduledcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.getscheduledcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-unschedulecampaign">
<summary><span>Unschedule a Scheduled Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>unschedulecampaign</code></span></summary>
<p>Run <strong>Unschedule a Scheduled Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.unschedulecampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.unschedulecampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-sendcampaign">
<summary><span>Send a Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>sendcampaign</code></span></summary>
<p>Run <strong>Send a Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.sendcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.sendcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_campaigns-sendtestcampaign">
<summary><span>Send a Test Campaign — <code>sendgrid.<wbr>lmc_<wbr>campaigns.<wbr>sendtestcampaign</code></span></summary>
<p>Run <strong>Send a Test Campaign</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_campaigns.sendtestcampaign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.campaign_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.to</code></td>
<td>string</td>
<td>Required</td>
<td>The email address that should receive the test campaign.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_campaigns.sendtestcampaign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "campaign_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-createcustomfield">
<summary><span>Create a Custom Field — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>createcustomfield</code></span></summary>
<p>Run <strong>Create a Custom Field</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.createcustomfield">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.type</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.createcustomfield">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listcustomfield">
<summary><span>Retrieve all custom fields — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listcustomfield</code></span></summary>
<p>Run <strong>Retrieve all custom fields</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listcustomfield">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listcustomfield">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getcustomfield">
<summary><span>Retrieve a Custom Field — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getcustomfield</code></span></summary>
<p>Run <strong>Retrieve a Custom Field</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getcustomfield">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_field_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the custom field that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getcustomfield">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_field_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deletecustomfield">
<summary><span>Delete a Custom Field — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deletecustomfield</code></span></summary>
<p>Run <strong>Delete a Custom Field</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deletecustomfield">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_field_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the custom field that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deletecustomfield">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_field_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-createcontactdblist">
<summary><span>Create a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>createcontactdblist</code></span></summary>
<p>Run <strong>Create a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.createcontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Create a List request</td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.createcontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listcontactdblist">
<summary><span>Retrieve all lists — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listcontactdblist</code></span></summary>
<p>Run <strong>Retrieve all lists</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listcontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listcontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deletecontactdblists">
<summary><span>Delete Multiple lists — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deletecontactdblists</code></span></summary>
<p>Run <strong>Delete Multiple lists</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deletecontactdblists">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deletecontactdblists">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getcontactdblist">
<summary><span>Retrieve a single list — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getcontactdblist</code></span></summary>
<p>Run <strong>Retrieve a single list</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getcontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getcontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-updatecontactdblist">
<summary><span>Update a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>updatecontactdblist</code></span></summary>
<p>Run <strong>Update a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.updatecontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Update a List request</td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The new name for your list.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.updatecontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deletecontactdblist">
<summary><span>Delete a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deletecontactdblist</code></span></summary>
<p>Run <strong>Delete a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deletecontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.delete_contacts</code></td>
<td>—</td>
<td>Optional</td>
<td>Adds the ability to delete all contacts on the list in addition to deleting the list.</td>
<td></td>
</tr>
<tr>
<td><code>query.delete_contacts</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/DeleteContacts&quot;</code></td>
</tr>
<tr>
<td><code>query.delete_contacts</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deletecontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listrecipientsfromcontactdblist">
<summary><span>Retrieve all recipients on a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listrecipientsfromco<wbr>ntactdblist</code></span></summary>
<p>Run <strong>Retrieve all recipients on a List</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listrecipientsfromcontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the list of recipients you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Page index of first recipient to return (must be a positive integer)</td>
<td></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of recipients to return at a time (must be a positive integer between 1 and 1000)</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listrecipientsfromcontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-addrecipientstocontactdblist">
<summary><span>Add Multiple Recipients to a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>addrecipientstoconta<wbr>ctdblist</code></span></summary>
<p>Run <strong>Add Multiple Recipients to a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.addrecipientstocontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the list of recipients you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.addrecipientstocontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-addrecipienttocontactdblist">
<summary><span>Add a Single Recipient to a List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>addrecipienttocontac<wbr>tdblist</code></span></summary>
<p>Run <strong>Add a Single Recipient to a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.addrecipienttocontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the list that you want to add the recipient to.</td>
<td></td>
</tr>
<tr>
<td><code>path.recipient_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the recipient you are adding to the list.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.addrecipienttocontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1,
    "recipient_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deleterecipientfromcontactdblist">
<summary><span>Delete a Single Recipient from a Single List — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deleterecipientfromc<wbr>ontactdblist</code></span></summary>
<p>Run <strong>Delete a Single Recipient from a Single List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deleterecipientfromcontactdblist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the list that you want to add the recipient to.</td>
<td></td>
</tr>
<tr>
<td><code>path.recipient_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the recipient you are adding to the list.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deleterecipientfromcontactdblist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "list_id": 1,
    "recipient_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-addrecipient">
<summary><span>Add recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>addrecipient</code></span></summary>
<p>Run <strong>Add recipients</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.addrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[].email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the recipient.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body[].first_name</code></td>
<td>string</td>
<td>Optional</td>
<td>The first name of the recipient.</td>
<td></td>
</tr>
<tr>
<td><code>body[].last_name</code></td>
<td>string</td>
<td>Optional</td>
<td>The last name of the recipient.</td>
<td></td>
</tr>
<tr>
<td><code>body[].age</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.addrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-updaterecipient">
<summary><span>Update Recipient — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>updaterecipient</code></span></summary>
<p>Run <strong>Update Recipient</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.updaterecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[].email</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body[].last_name</code></td>
<td>string</td>
<td>Optional</td>
<td>The last name of the recipient. This is one of the default custom fields.</td>
<td></td>
</tr>
<tr>
<td><code>body[].first_name</code></td>
<td>string</td>
<td>Optional</td>
<td>The first name of the recipient. This is one of the default custom fields.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.updaterecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deleterecipients">
<summary><span>Delete Recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deleterecipients</code></span></summary>
<p>Run <strong>Delete Recipients</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deleterecipients">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deleterecipients">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listrecipient">
<summary><span>Retrieve recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listrecipient</code></span></summary>
<p>Run <strong>Retrieve recipients</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Page index of first recipients to return (must be a positive integer)</td>
<td></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of recipients to return at a time (must be a positive integer between 1 and 1000)</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getrecipient">
<summary><span>Retrieve a single recipient — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getrecipient</code></span></summary>
<p>Run <strong>Retrieve a single recipient</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.recipient_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the recipient that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "recipient_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deleterecipient">
<summary><span>Delete a Recipient — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deleterecipient</code></span></summary>
<p>Run <strong>Delete a Recipient</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deleterecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.recipient_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the recipient that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deleterecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "recipient_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getrecipientlist">
<summary><span>Retrieve the lists that a recipient is on — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getrecipientlist</code></span></summary>
<p>Run <strong>Retrieve the lists that a recipient is on</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getrecipientlist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.recipient_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the recipient for whom you are retrieving lists.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getrecipientlist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "recipient_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getbillable">
<summary><span>Retrieve the count of billable recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getbillable</code></span></summary>
<p>Run <strong>Retrieve the count of billable recipients</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getbillable">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getbillable">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listrecipientcount">
<summary><span>Retrieve a Count of Recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listrecipientcount</code></span></summary>
<p>Run <strong>Retrieve a Count of Recipients</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listrecipientcount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listrecipientcount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listsearchrecipient">
<summary><span>Search recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listsearchrecipient</code></span></summary>
<p>Run <strong>Search recipients</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listsearchrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.{field_name}</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listsearchrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-searchrecipient">
<summary><span>Search recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>searchrecipient</code></span></summary>
<p>Run <strong>Search recipients</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.searchrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conditions</code></td>
<td>array</td>
<td>Required</td>
<td>The conditions by which this segment should be created.</td>
<td></td>
</tr>
<tr>
<td><code>body.conditions[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ContactdbSegmentsConditions&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.searchrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listreservedfield">
<summary><span>Retrieve reserved fields — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listreservedfield</code></span></summary>
<p>Run <strong>Retrieve reserved fields</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listreservedfield">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listreservedfield">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-createsegment">
<summary><span>Create a Segment — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>createsegment</code></span></summary>
<p>Run <strong>Create a Segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.createsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ContactdbSegments&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.createsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listsegment">
<summary><span>Retrieve all segments — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listsegment</code></span></summary>
<p>Run <strong>Retrieve all segments</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getsegment">
<summary><span>Retrieve a segment — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getsegment</code></span></summary>
<p>Run <strong>Retrieve a segment</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-updatesegment">
<summary><span>Update a segment — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>updatesegment</code></span></summary>
<p>Run <strong>Update a segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.updatesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_id</code></td>
<td>number</td>
<td>Optional</td>
<td>The list ID you would like this segment to be built from.</td>
<td></td>
</tr>
<tr>
<td><code>body.conditions</code></td>
<td>array</td>
<td>Optional</td>
<td>The conditions by which this segment should be created.</td>
<td></td>
</tr>
<tr>
<td><code>body.conditions[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ContactdbSegmentsConditions&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.updatesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-deletesegment">
<summary><span>Delete a segment — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>deletesegment</code></span></summary>
<p>Run <strong>Delete a segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.deletesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.delete_contacts</code></td>
<td>boolean</td>
<td>Optional</td>
<td>True to delete all contacts matching the segment in addition to deleting the segment</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.deletesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listrecipientforsegment">
<summary><span>Retrieve recipients on a segment — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listrecipientforsegm<wbr>ent</code></span></summary>
<p>Run <strong>Retrieve recipients on a segment</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listrecipientforsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the segment from which you want to retrieve recipients.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listrecipientforsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-liststatus">
<summary><span>Get Recipient Upload Status — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>liststatus</code></span></summary>
<p>Run <strong>Get Recipient Upload Status</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.liststatus">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.liststatus">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-exportrecipient">
<summary><span>Export Recipients — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>exportrecipient</code></span></summary>
<p>Run <strong>Export Recipients</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.exportrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>IDs of the recipient lists you want to export.</td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.segment_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>IDs of the recipient segments you want to export.</td>
<td></td>
</tr>
<tr>
<td><code>body.segment_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.notifications</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.notifications.email</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/FileType&quot;</code></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;csv&quot;</code></td>
</tr>
<tr>
<td><code>body.max_file_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The maximum size of an export file in MB. Note that when this option is specified, multiple output files may be returned from the export.</td>
<td><code>default: 5000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.exportrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-listexportrecipient">
<summary><span>Get All Existing Exports — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>listexportrecipient</code></span></summary>
<p>Run <strong>Get All Existing Exports</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.listexportrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.listexportrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_contactdb-getexportrecipient">
<summary><span>Export Recipients Status — <code>sendgrid.<wbr>lmc_<wbr>contactdb.<wbr>getexportrecipient</code></span></summary>
<p>Run <strong>Export Recipients Status</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_contactdb.getexportrecipient">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_contactdb.getexportrecipient">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-createsender">
<summary><span>Create a Sender Identity — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>createsender</code></span></summary>
<p>Run <strong>Create a Sender Identity</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.createsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.nickname</code></td>
<td>string</td>
<td>Required</td>
<td>A nickname for the sender identity. Not used for sending.</td>
<td></td>
</tr>
<tr>
<td><code>body.from</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.reply_to</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.address</code></td>
<td>string</td>
<td>Required</td>
<td>The physical address of the sender identity.</td>
<td></td>
</tr>
<tr>
<td><code>body.address_2</code></td>
<td>string</td>
<td>Optional</td>
<td>Additional sender identity address information.</td>
<td></td>
</tr>
<tr>
<td><code>body.city</code></td>
<td>string</td>
<td>Required</td>
<td>The city of the sender identity.</td>
<td></td>
</tr>
<tr>
<td><code>body.state</code></td>
<td>string</td>
<td>Optional</td>
<td>The state of the sender identity.</td>
<td></td>
</tr>
<tr>
<td><code>body.zip</code></td>
<td>string</td>
<td>Optional</td>
<td>The zipcode of the sender identity.</td>
<td></td>
</tr>
<tr>
<td><code>body.country</code></td>
<td>string</td>
<td>Required</td>
<td>The country of the sender identity.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.createsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-listsender">
<summary><span>Get all Sender Identities — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>listsender</code></span></summary>
<p>Run <strong>Get all Sender Identities</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.listsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.listsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-getsender">
<summary><span>View a Sender Identity — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>getsender</code></span></summary>
<p>Run <strong>View a Sender Identity</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.getsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.sender_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the sender identity that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.getsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "sender_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-updatesender">
<summary><span>Update a Sender Identity — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>updatesender</code></span></summary>
<p>Run <strong>Update a Sender Identity</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.updatesender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.sender_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the sender identity that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SenderIdRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.updatesender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "sender_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-deletesender">
<summary><span>Delete a Sender Identity — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>deletesender</code></span></summary>
<p>Run <strong>Delete a Sender Identity</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.deletesender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.sender_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the sender identity that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.deletesender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "sender_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-lmc_senders-resetsenderverification">
<summary><span>Resend Sender Identity Verification — <code>sendgrid.<wbr>lmc_<wbr>senders.<wbr>resetsenderverificat<wbr>ion</code></span></summary>
<p>Run <strong>Resend Sender Identity Verification</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.lmc_senders.resetsenderverification">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.sender_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of the sender identity for which you would like to resend a verification email.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.lmc_senders.resetsenderverification">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "sender_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-logs-getmessagebyid">
<summary><span>Get all details for the specified message ID. — <code>sendgrid.<wbr>logs.<wbr>getmessagebyid</code></span></summary>
<p>Run <strong>Get all details for the specified message ID.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.logs.getmessagebyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.sg_message_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the message you are requesting details for.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.subuser</code></td>
<td>string</td>
<td>Optional</td>
<td>For requests authenticated as the parent account, this argument must be passed if the desired message belongs to a subuser.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.logs.getmessagebyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "sg_message_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-logs-listmessagesbyfilter">
<summary><span>Search all messages using the provided query filters. — <code>sendgrid.<wbr>logs.<wbr>listmessagesbyfilter</code></span></summary>
<p>Run <strong>Search all messages using the provided query filters.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.logs.listmessagesbyfilter">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/EmailLogsGetMessagesByFilterRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.logs.listmessagesbyfilter">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listmailsetting">
<summary><span>Retrieve all mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listmailsetting</code></span></summary>
<p>Run <strong>Retrieve all mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listmailsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listmailsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updateaddresswhitelist">
<summary><span>Update address whitelist mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updateaddresswhiteli<wbr>st</code></span></summary>
<p>Run <strong>Update address whitelist mail settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updateaddresswhitelist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if your email address whitelist is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.list</code></td>
<td>array</td>
<td>Optional</td>
<td>Either a single email address that you want whitelisted or a domain, for which all email addresses belonging to this domain will be whitelisted.</td>
<td></td>
</tr>
<tr>
<td><code>body.list[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updateaddresswhitelist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listaddresswhitelist">
<summary><span>Retrieve address whitelist mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listaddresswhitelist</code></span></summary>
<p>Run <strong>Retrieve address whitelist mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listaddresswhitelist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listaddresswhitelist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updatebouncepurge">
<summary><span>Update Bounce Purge Mail Settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updatebouncepurge</code></span></summary>
<p>Run <strong>Update Bounce Purge Mail Settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updatebouncepurge">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailSettingsBouncePurge&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updatebouncepurge">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listbouncepurge">
<summary><span>Retrieve Bounce Purge Mail Settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listbouncepurge</code></span></summary>
<p>Run <strong>Retrieve Bounce Purge Mail Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listbouncepurge">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listbouncepurge">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updatefooter">
<summary><span>Update footer mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updatefooter</code></span></summary>
<p>Run <strong>Update footer mail settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updatefooter">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailSettingsFooter&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updatefooter">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listfooter">
<summary><span>Retrieve footer mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listfooter</code></span></summary>
<p>Run <strong>Retrieve footer mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listfooter">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listfooter">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updateforwardbounce">
<summary><span>Update forward bounce mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updateforwardbounce</code></span></summary>
<p>Run <strong>Update forward bounce mail settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updateforwardbounce">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailSettingsForwardBounce&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updateforwardbounce">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listforwardbounce">
<summary><span>Retrieve forward bounce mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listforwardbounce</code></span></summary>
<p>Run <strong>Retrieve forward bounce mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listforwardbounce">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listforwardbounce">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updateforwardspam">
<summary><span>Update forward spam mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updateforwardspam</code></span></summary>
<p>Run <strong>Update forward spam mail settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updateforwardspam">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailSettingsForwardSpam&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updateforwardspam">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listforwardspam">
<summary><span>Retrieve forward spam mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listforwardspam</code></span></summary>
<p>Run <strong>Retrieve forward spam mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listforwardspam">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listforwardspam">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-updatetemplate">
<summary><span>Update template mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>updatetemplate</code></span></summary>
<p>Run <strong>Update template mail settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.updatetemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if you want to enable the legacy email template mail setting.</td>
<td></td>
</tr>
<tr>
<td><code>body.html_content</code></td>
<td>string</td>
<td>Optional</td>
<td>The new HTML content for your legacy email template.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.updatetemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail_settings-listtemplate">
<summary><span>Retrieve legacy template mail settings — <code>sendgrid.<wbr>mail_<wbr>settings.<wbr>listtemplate</code></span></summary>
<p>Run <strong>Retrieve legacy template mail settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail_settings.listtemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail_settings.listtemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail-createmailbatch">
<summary><span>Create a batch ID. — <code>sendgrid.<wbr>mail.<wbr>createmailbatch</code></span></summary>
<p>Run <strong>Create a batch ID.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail.createmailbatch">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>Use the <code>on-behalf-of</code> header to make API calls for a particular Subuser through the parent account. You can use this header to automate bulk updates or to administer a Subuser without changing the authentication in your code. You will use the parent account&#39;s API key when using this header.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail.createmailbatch">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail-getmailbatch">
<summary><span>Validate a batch ID. — <code>sendgrid.<wbr>mail.<wbr>getmailbatch</code></span></summary>
<p>Run <strong>Validate a batch ID.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail.getmailbatch">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.batch_id</code></td>
<td>string</td>
<td>Required</td>
<td>Set this parameter to the batch ID that&#39;s associated with the mail send you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>Use the <code>on-behalf-of</code> header to make API calls for a particular Subuser through the parent account. You can use this header to automate bulk updates or to administer a Subuser without changing the authentication in your code. You will use the parent account&#39;s API key when using this header.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail.getmailbatch">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "batch_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mail-sendmail">
<summary><span>Send Email with Twilio SendGrid. — <code>sendgrid.<wbr>mail.<wbr>sendmail</code></span></summary>
<p>Run <strong>Send Email with Twilio SendGrid.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mail.sendmail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Content-Encoding</code></td>
<td>—</td>
<td>Optional</td>
<td>Use this header when sending a gzip compressed mail body. Mail body compression is available to some high volume accounts. Submit a <a href="https://support.sendgrid.com/hc/en-us">request to support</a> to have gzip enabled on your account.</td>
<td></td>
</tr>
<tr>
<td><code>headers.Content-Encoding</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/ContentEncoding&quot;</code></td>
</tr>
<tr>
<td><code>headers.Content-Encoding</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.personalizations</code></td>
<td>array</td>
<td>Required</td>
<td>An array of messages and their metadata. Each object within the <code>personalizations</code> array can be thought of as a mail envelope—it defines who should receive an individual message and how that message should be handled. See <a href="https://sendgrid.com/docs/for-developers/sending-email/personalizations/"><strong>Personalizations</strong></a> for more information.</td>
<td><code>maxItems: 1000; uniqueItems: false</code></td>
</tr>
<tr>
<td><code>body.personalizations[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.personalizations[].from</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailFrom&quot;</code></td>
</tr>
<tr>
<td><code>body.personalizations[].to</code></td>
<td>array</td>
<td>Required</td>
<td>An array of recipients to whom the email will be sent. Each object in this array must contain a recipient&#39;s email address. Each object in the array may optionally contain a recipient&#39;s name.</td>
<td></td>
</tr>
<tr>
<td><code>body.personalizations[].to[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailTo&quot;</code></td>
</tr>
<tr>
<td><code>body.personalizations[].cc</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of recipients to whom a copy of the email will be sent. Each object in this array must contain a recipient&#39;s email address. Each object in the array may optionally contain a recipient&#39;s name.</td>
<td><code>maxItems: 1000</code></td>
</tr>
<tr>
<td><code>body.personalizations[].cc[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailTo&quot;</code></td>
</tr>
<tr>
<td><code>body.personalizations[].bcc</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of recipients to whom a blind carbon copy of your email will be sent. Each object in this array must contain a recipient&#39;s email address. Each object in the array may optionally contain a recipient&#39;s name.</td>
<td><code>maxItems: 1000</code></td>
</tr>
<tr>
<td><code>body.personalizations[].bcc[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailTo&quot;</code></td>
</tr>
<tr>
<td><code>body.personalizations[].subject</code></td>
<td>string</td>
<td>Optional</td>
<td>The subject of your email. See line length limits specified in <a href="https://www.rfc-editor.org/rfc/rfc2822#section-2.1.1">RFC 2822</a> for guidance on subject line character limits.</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.personalizations[].headers</code></td>
<td>object</td>
<td>Optional</td>
<td>A collection of JSON property name and property value pairs allowing you to specify handling instructions for your email. You may not override the following headers: <code>x-sg-id</code>, <code>x-sg-eid</code>, <code>received</code>, <code>dkim-signature</code>, <code>Content-Type</code>, <code>Content-Transfer-Encoding</code>, <code>To</code>, <code>From</code>, <code>Subject</code>, <code>Reply-To</code>, <code>CC</code>, <code>BCC</code>.</td>
<td></td>
</tr>
<tr>
<td><code>body.personalizations[].substitutions</code></td>
<td>object</td>
<td>Optional</td>
<td>A collection property names that will be substituted by their corresponding property values in the <code>subject</code>, <code>reply-to</code> and <code>content</code> portions of your message. Name and value pairs follow the pattern <code>&quot;substitution_tag&quot;:&quot;value to substitute&quot;</code>. The total collective size of your substitutions may not exceed 100,000 bytes per personalization object. Substitutions allow you to insert data without using SendGrid&#39;s Dynamic Templates. This property should not be used in combination with a Dynamic Template, which can be identified by a <code>template_id</code> starting with <code>d-</code>. See <a href="https://docs.sendgrid.com/for-developers/sending-email/substitution-tags"><strong>Substitution Tags</strong></a> for more information.</td>
<td><code>maxProperties: 10000; additionalProperties: {&quot;type&quot;:&quot;string&quot;}</code></td>
</tr>
<tr>
<td><code>body.personalizations[].dynamic_template_data</code></td>
<td>object</td>
<td>Optional</td>
<td>A collection property names that will be substituted by their corresponding property values in the <code>subject</code>, <code>reply-to</code> and <code>content</code> portions of a SendGrid Dynamic Template. Dynamic template data is available in a template using <a href="https://docs.sendgrid.com/for-developers/sending-email/using-handlebars">Handlebars</a> syntax. This property should be used in combination with a Dynamic Template, which can be identified by a <code>template_id</code> starting with <code>d-</code>. See <a href="https://docs.sendgrid.com/ui/sending-email/how-to-send-an-email-with-dynamic-templates"><strong>How to Send an Email with Dynamic Templates</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body.personalizations[].custom_args</code></td>
<td>object</td>
<td>Optional</td>
<td>Values that are specific to this personalization that will be carried along with the email and its activity data. Substitutions will not be made on custom arguments, so any string that is assigned to this property will be assumed to be the custom argument that you would like to be used. This field may not exceed 10,000 bytes.</td>
<td><code>maxProperties: 10000</code></td>
</tr>
<tr>
<td><code>body.personalizations[].send_at</code></td>
<td>integer</td>
<td>Optional</td>
<td>A <a href="https://en.wikipedia.org/wiki/Unix_time">unix timestamp</a> allowing you to specify when your email should be sent. A send cannot be scheduled more than 72 hours in advance.</td>
<td></td>
</tr>
<tr>
<td><code>body.from</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailFrom&quot;</code></td>
</tr>
<tr>
<td><code>body.reply_to</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailTo&quot;</code></td>
</tr>
<tr>
<td><code>body.reply_to_list</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of recipients to whom replies will be sent. Each object in this array must contain a recipient&#39;s email address. Each object in the array may optionally contain a recipient&#39;s name. You can use either the <code>reply_to</code> property or <code>reply_to_list</code> property but not both.</td>
<td><code>maxItems: 1000; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.reply_to_list[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/MailTo&quot;</code></td>
</tr>
<tr>
<td><code>body.subject</code></td>
<td>string</td>
<td>Optional</td>
<td>The global or <em>message level</em> subject of your email. Subject lines set in personalizations objects will override this global subject line. See line length limits specified in <a href="https://www.rfc-editor.org/rfc/rfc2822#section-2.1.1">RFC 2822</a> for guidance on subject line character limits.</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.content</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of objects, each containing a message body&#39;s content and <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a>. You must specify at least one MIME type and may include multiple. To include more than one MIME type, add an object for each type to the array.</td>
<td></td>
</tr>
<tr>
<td><code>body.content[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.content[].type</code></td>
<td>string</td>
<td>Required</td>
<td>The MIME type of the content assigned in the <code>value</code> property of this object (e.g., <code>text/plain</code> or <code>text/html</code>).</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.content[].value</code></td>
<td>string</td>
<td>Required</td>
<td>The content of your message in the specified MIME type assigned in the <code>type</code> property of this object.</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.attachments</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of objects where you can define any attachments to be included with the message. Each object contains a <code>content</code> property, which must be a Base64 encoded string of the attachment itself, and <code>type</code>, <code>filename</code>, <code>disposition</code>, and <code>content_id</code> properties that tell SendGrid how to handle the attachment.</td>
<td></td>
</tr>
<tr>
<td><code>body.attachments[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.attachments[].content</code></td>
<td>string</td>
<td>Required</td>
<td>The Base64 encoded content of the attachment.</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.attachments[].type</code></td>
<td>string</td>
<td>Optional</td>
<td>The MIME type of the content you are attaching (e.g., <code>image/jpeg</code> or <code>application/pdf</code>).</td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.attachments[].filename</code></td>
<td>string</td>
<td>Required</td>
<td>The attachment&#39;s filename, including the file extension.</td>
<td></td>
</tr>
<tr>
<td><code>body.attachments[].disposition</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.attachments[].disposition</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Disposition&quot;</code></td>
</tr>
<tr>
<td><code>body.attachments[].disposition</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;attachment&quot;</code></td>
</tr>
<tr>
<td><code>body.attachments[].content_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The attachment&#39;s content ID. The <code>content_id</code> is used when the <code>disposition</code> is set to <code>inline</code> and the attachment is an image, allowing the file to be displayed within the body of the email.</td>
<td></td>
</tr>
<tr>
<td><code>body.template_id</code></td>
<td>string</td>
<td>Optional</td>
<td>An email template ID. A template that contains a subject and content—either text or html—will override any subject and content values specified at the <code>personalizations</code> or message level. If a template ID begins with <code>d-</code>, it is a dynamic template and will work with the <code>dynamic_template_data</code> property. If the template ID does not begin with <code>d-</code>, it is a standard SendGrid template and will work with the <code>substitutions</code> property. See <a href="https://docs.sendgrid.com/ui/sending-email/how-to-send-an-email-with-dynamic-templates"><strong>How to Send an Email with Dynamic Templates</strong></a> for more information about working with templates.</td>
<td></td>
</tr>
<tr>
<td><code>body.headers</code></td>
<td>object</td>
<td>Optional</td>
<td>A collection of JSON property name and property value pairs allowing you to specify handling instructions for your email. You may not override the following headers: <code>x-sg-id</code>, <code>x-sg-eid</code>, <code>received</code>, <code>dkim-signature</code>, <code>Content-Type</code>, <code>Content-Transfer-Encoding</code>, <code>To</code>, <code>From</code>, <code>Subject</code>, <code>Reply-To</code>, <code>CC</code>, <code>BCC</code>.</td>
<td></td>
</tr>
<tr>
<td><code>body.categories</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of category names assigned to this message. Categories allow you to group messages by categories you define. Categories should be used sparingly to create general groups that are relevant to you. Categories are not meant to be used to track individual mail sends. For more granular categorization and tracking, use the <code>custom_args</code> property. A category name cannot exceed 255 characters. See <a href="https://docs.sendgrid.com/for-developers/sending-email/categories"><strong>Working with Categories</strong></a> for more information.</td>
<td><code>maxItems: 10; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.categories[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 255</code></td>
</tr>
<tr>
<td><code>body.custom_args</code></td>
<td>string</td>
<td>Optional</td>
<td>Values that are specific to the entire send that will be carried along with the email and its activity data. Substitutions will not be made on custom arguments, so any string that is assigned to this property will be assumed to be the custom argument that you would like to be used. This parameter is overridden by <code>custom_args</code> set at the personalizations level. Total <code>custom_args</code> size may not exceed 10,000 bytes.</td>
<td></td>
</tr>
<tr>
<td><code>body.send_at</code></td>
<td>integer</td>
<td>Optional</td>
<td>A <a href="https://en.wikipedia.org/wiki/Unix_time">unix timestamp</a> allowing you to specify when your email should be sent. A send cannot be scheduled more than 72 hours in advance. This property may be overridden by the <code>send_at</code> property set at the personalizations level.</td>
<td></td>
</tr>
<tr>
<td><code>body.batch_id</code></td>
<td>string</td>
<td>Optional</td>
<td>An ID representing a batch of emails to be sent at the same time. Including a <code>batch_id</code> in your request allows you to include this email in that batch. It also enables you to cancel or pause the delivery of that batch. See the <a href="https://sendgrid.com/docs/api-reference/">Scheduled Sends API</a> for more information about scheduling your email.</td>
<td></td>
</tr>
<tr>
<td><code>body.asm</code></td>
<td>object</td>
<td>Optional</td>
<td>An object allowing you to specify how to handle unsubscribes. With SendGrid, an unsubscribe is the action an email recipient takes when they opt-out of receiving your messages. A suppression is the action you take as a sender to filter or suppress an unsubscribed address from your email send. From the perspective of the recipient, your suppression is the result of their unsubscribe. See <a href="https://www.twilio.com/docs/sendgrid/api-reference/suppressions-unsubscribe-groups/create-a-new-suppression-group"><strong>Suppression Groups</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body.asm.group_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unsubscribe group to associate with this email. See the <a href="https://docs.sendgrid.com/api-reference/suppressions/">Suppressions API</a> to manage unsubscribe group IDs.</td>
<td></td>
</tr>
<tr>
<td><code>body.asm.groups_to_display</code></td>
<td>array</td>
<td>Optional</td>
<td>An array containing the unsubscribe groups that you would like to be displayed to a recipient on the unsubscribe preferences page. This page is displayed in the recipient&#39;s browser when they click the unsubscribe link in your message.</td>
<td><code>maxItems: 25</code></td>
</tr>
<tr>
<td><code>body.asm.groups_to_display[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ip_pool_name</code></td>
<td>string</td>
<td>Optional</td>
<td>The IP Pool that you would like to send this email from. IP Pools allow you to group your dedicated Twilio SendGrid IP addresses in order to have more control over your deliverability. See <a href="https://docs.sendgrid.com/ui/account-and-settings/ip-pools"><strong>IP Pools</strong></a> for more information.</td>
<td><code>minLength: 2; maxLength: 64</code></td>
</tr>
<tr>
<td><code>body.mail_settings</code></td>
<td>object</td>
<td>Optional</td>
<td>A collection of different mail settings that you can use to specify how you would like this email to be handled. Mail settings provide extra functionality to your mail send. See <a href="https://docs.sendgrid.com/ui/account-and-settings/mail"><strong>Mail Settings</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_list_management</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to bypass all unsubscribe groups and suppressions to ensure that the email is delivered to every single recipient. This should only be used in emergencies when it is absolutely necessary that every recipient receives your email. This filter cannot be combined with any other bypass filters. See the <a href="https://sendgrid.com/docs/ui/sending-email/index-suppressions/#bypass-suppressions">the &quot;Bypass suppressions&quot; section of our <strong>Suppressions Overview</strong></a> for more about bypass filters.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_list_management.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_spam_management</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to bypass the spam report list to ensure that the email is delivered to recipients. Bounce and unsubscribe lists will still be checked; addresses on these other lists will not receive the message. This filter cannot be combined with the <code>bypass_list_management</code> filter. See the <a href="https://sendgrid.com/docs/ui/sending-email/index-suppressions/#bypass-suppressions">the &quot;Bypass suppressions&quot; section of our <strong>Suppressions Overview</strong></a> for more about bypass filters.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_spam_management.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_bounce_management</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to bypass the bounce list to ensure that the email is delivered to recipients. Spam report and unsubscribe lists will still be checked; addresses on these other lists will not receive the message. This filter cannot be combined with the <code>bypass_list_management</code> filter. See the <a href="https://sendgrid.com/docs/ui/sending-email/index-suppressions/#bypass-suppressions">the &quot;Bypass suppressions&quot; section of our <strong>Suppressions Overview</strong></a> for more about bypass filters.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_bounce_management.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_unsubscribe_management</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to bypass the global unsubscribe list to ensure that the email is delivered to recipients. Bounce and spam report lists will still be checked; addresses on these other lists will not receive the message. This filter applies only to global unsubscribes and will not bypass group unsubscribes. This filter cannot be combined with the <code>bypass_list_management</code> filter. See the <a href="https://sendgrid.com/docs/ui/sending-email/index-suppressions/#bypass-suppressions">the &quot;Bypass suppressions&quot; section of our <strong>Suppressions Overview</strong></a> for more about bypass filters.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.bypass_unsubscribe_management.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.footer</code></td>
<td>object</td>
<td>Optional</td>
<td>Inserts a custom footer at the bottom of the text and HTML bodies of your messages. Use the <code>html</code> and <code>text</code> properties to include the content of the footers to be inserted.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.footer.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.footer.text</code></td>
<td>string</td>
<td>Optional</td>
<td>The plain text content of your footer.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.footer.html</code></td>
<td>string</td>
<td>Optional</td>
<td>The HTML content of your footer.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.sandbox_mode</code></td>
<td>object</td>
<td>Optional</td>
<td>Sandbox Mode allows you to send a test email to ensure that your request body is valid and formatted correctly.</td>
<td></td>
</tr>
<tr>
<td><code>body.mail_settings.sandbox_mode.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings</code></td>
<td>object</td>
<td>Optional</td>
<td>Settings to determine how you would like to track the metrics of how your recipients interact with your email. See <a href="https://docs.sendgrid.com/ui/account-and-settings/tracking"><strong>Tracking Settings</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.click_tracking</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to track if a recipient clicked a link in your email.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.click_tracking.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.click_tracking.enable_text</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting should be included in the <code>text/plain</code> portion of your email.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.open_tracking</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to track if the email was opened by including a single transparent pixel image in the body of the message content. When the message is opened, a request for the pixel is sent. That request indicates to Twilio SendGrid that the message was opened.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.open_tracking.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.open_tracking.substitution_tag</code></td>
<td>string</td>
<td>Optional</td>
<td>Allows you to specify a substitution tag that you can insert in the body of your email at a location that you desire. This tag will be replaced by the open tracking pixel.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.subscription_tracking</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to insert a subscription management link at the bottom of the text and HTML bodies of your email. If you would like to specify the location of the link within your email, you may use the <code>substitution_tag</code> property.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.subscription_tracking.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.subscription_tracking.text</code></td>
<td>string</td>
<td>Optional</td>
<td>Text to be appended to the email with the subscription tracking link.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.subscription_tracking.html</code></td>
<td>string</td>
<td>Optional</td>
<td>HTML to be appended to the email with the subscription tracking link.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.subscription_tracking.substitution_tag</code></td>
<td>string</td>
<td>Optional</td>
<td>A tag that will be replaced with the unsubscribe URL. If this property is used, it will override both the <code>text</code> and <code>html</code> properties. The URL of the link will be placed at the substitution tag&#39;s location in the message body with no additional formatting.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics</code></td>
<td>object</td>
<td>Optional</td>
<td>Allows you to enable tracking provided by Google Analytics. See <a href="https://docs.sendgrid.com/ui/analytics-and-reporting/google-analytics"><strong>Google Analytics and SendGrid Statistics</strong></a> for more information about this property.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.enable</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if this setting is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.utm_source</code></td>
<td>string</td>
<td>Optional</td>
<td>Name of the referrer source. (e.g., Google, SomeDomain.com, or Marketing Email)</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.utm_medium</code></td>
<td>string</td>
<td>Optional</td>
<td>Name of the marketing medium. (e.g., Email)</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.utm_term</code></td>
<td>string</td>
<td>Optional</td>
<td>Used to identify any paid keywords.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.utm_content</code></td>
<td>string</td>
<td>Optional</td>
<td>Used to differentiate your campaign from advertisements.</td>
<td></td>
</tr>
<tr>
<td><code>body.tracking_settings.ganalytics.utm_campaign</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of the campaign.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mail.sendmail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-updatecontact">
<summary><span>Add or Update a Contact — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>updatecontact</code></span></summary>
<p>Run <strong>Add or Update a Contact</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.updatecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of List ID strings that this contact will be added to.</td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body.contacts</code></td>
<td>array</td>
<td>Required</td>
<td>One or more contacts objects that you intend to upsert. Each contact needs to include at least one of <code>email</code>, <code>phone_number_id</code>, <code>external_id</code>, or <code>anonymous_id</code> as an identifier.</td>
<td><code>minItems: 1; maxItems: 30000</code></td>
</tr>
<tr>
<td><code>body.contacts[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ContactRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.updatecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-deletecontact">
<summary><span>Delete Contacts — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>deletecontact</code></span></summary>
<p>Run <strong>Delete Contacts</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.deletecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.delete_all_contacts</code></td>
<td>string</td>
<td>Optional</td>
<td>Must be set to <code>&quot;true&quot;</code> to delete all contacts.</td>
<td></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>string</td>
<td>Optional</td>
<td>A comma-separated list of contact IDs.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.deletecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-listcontact">
<summary><span>Get Sample Contacts — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>listcontact</code></span></summary>
<p>Run <strong>Get Sample Contacts</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.listcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.listcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-getcontact">
<summary><span>Get a Contact by ID — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>getcontact</code></span></summary>
<p>Run <strong>Get a Contact by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.getcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.getcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-listbatchedcontact">
<summary><span>Get Batched Contacts by IDs — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>listbatchedcontact</code></span></summary>
<p>Run <strong>Get Batched Contacts by IDs</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.listbatchedcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Array of IDs</td>
<td></td>
</tr>
<tr>
<td><code>body.ids</code></td>
<td>array</td>
<td>Required</td>
<td></td>
<td><code>maxItems: 100</code></td>
</tr>
<tr>
<td><code>body.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.listbatchedcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-deletecontactidentifier">
<summary><span>Delete a Contact Identifier — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>deletecontactidentif<wbr>ier</code></span></summary>
<p>Run <strong>Delete a Contact Identifier</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.deletecontactidentifier">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>Must be set to the <code>contact_id</code> of the contact you want to remove the identifier from.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.identifier_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.identifier_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/IdentifierType&quot;</code></td>
</tr>
<tr>
<td><code>body.identifier_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body.identifier_value</code></td>
<td>string</td>
<td>Required</td>
<td>The value of the identifier you want to remove from the contact.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.deletecontactidentifier">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-listcontactcount">
<summary><span>Get Total Contact Count — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>listcontactcount</code></span></summary>
<p>Run <strong>Get Total Contact Count</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.listcontactcount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.listcontactcount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-exportcontact">
<summary><span>Export Contacts — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>exportcontact</code></span></summary>
<p>Run <strong>Export Contacts</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.exportcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>IDs of the contact lists you want to export.</td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body.segment_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>IDs of the contact segments you want to export.</td>
<td></td>
</tr>
<tr>
<td><code>body.segment_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.notifications</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.notifications.email</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/FileType&quot;</code></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;csv&quot;</code></td>
</tr>
<tr>
<td><code>body.max_file_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The maximum size of an export file in MB. Note that when this option is specified, multiple output files may be returned from the export.</td>
<td><code>default: 5000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.exportcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-listexportcontact">
<summary><span>Get All Existing Exports — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>listexportcontact</code></span></summary>
<p>Run <strong>Get All Existing Exports</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.listexportcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.listexportcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-getexportcontact">
<summary><span>Export Contacts Status — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>getexportcontact</code></span></summary>
<p>Run <strong>Export Contacts Status</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.getexportcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.getexportcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-importcontact">
<summary><span>Import Contacts — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>importcontact</code></span></summary>
<p>Run <strong>Import Contacts</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.importcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>All contacts will be added to each of the specified lists.</td>
<td></td>
</tr>
<tr>
<td><code>body.list_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/FileType1&quot;</code></td>
</tr>
<tr>
<td><code>body.file_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body.field_mappings</code></td>
<td>array</td>
<td>Required</td>
<td>Import file header to reserved/custom field mapping.</td>
<td><code>minItems: 1; uniqueItems: false</code></td>
</tr>
<tr>
<td><code>body.field_mappings[]</code></td>
<td>string &#124; null</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.importcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-getimportcontact">
<summary><span>Import Contacts Status — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>getimportcontact</code></span></summary>
<p>Run <strong>Import Contacts Status</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.getimportcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.getimportcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-searchcontact">
<summary><span>Search Contacts — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>searchcontact</code></span></summary>
<p>Run <strong>Search Contacts</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.searchcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.query</code></td>
<td>string</td>
<td>Required</td>
<td>An SGQL search string or other pattern.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.searchcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-listcontactbyemail">
<summary><span>Get Contacts by Emails — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>listcontactbyemail</code></span></summary>
<p>Run <strong>Get Contacts by Emails</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.listcontactbyemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Required</td>
<td>One or more primary and/or alternate email addresses to search for in your Marketing Campaigns contacts.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 100</code></td>
</tr>
<tr>
<td><code>body.phone_number_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The contact&#39;s Phone Number ID. This is required to be a valid phone number.</td>
<td></td>
</tr>
<tr>
<td><code>body.external_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The contact&#39;s External ID.</td>
<td><code>maxLength: 254</code></td>
</tr>
<tr>
<td><code>body.anonymous_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The contact&#39;s Anonymous ID.</td>
<td><code>maxLength: 254</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.listcontactbyemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_contacts-getcontactbyidentifiers">
<summary><span>Get Contacts by Identifiers — <code>sendgrid.<wbr>mc_<wbr>contacts.<wbr>getcontactbyidentifi<wbr>ers</code></span></summary>
<p>Run <strong>Get Contacts by Identifiers</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_contacts.getcontactbyidentifiers">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.identifier_type</code></td>
<td>—</td>
<td>Required</td>
<td>The type of identifier to search for. You can use only one type of identifier per search.</td>
<td></td>
</tr>
<tr>
<td><code>path.identifier_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/IdentifierType1&quot;</code></td>
</tr>
<tr>
<td><code>path.identifier_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.identifiers</code></td>
<td>array</td>
<td>Required</td>
<td>One or more more identifier values of the given identifier type to search for in your Marketing Campaigns contacts.</td>
<td></td>
</tr>
<tr>
<td><code>body.identifiers[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_contacts.getcontactbyidentifiers">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "identifier_type": "email"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_custom_fields-createfielddefinition">
<summary><span>Create Custom Field Definition — <code>sendgrid.<wbr>mc_<wbr>custom_<wbr>fields.<wbr>createfielddefinitio<wbr>n</code></span></summary>
<p>Run <strong>Create Custom Field Definition</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_custom_fields.createfielddefinition">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>body.field_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.field_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/FieldType&quot;</code></td>
</tr>
<tr>
<td><code>body.field_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_custom_fields.createfielddefinition">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_custom_fields-listfielddefinition">
<summary><span>Get All Field Definitions — <code>sendgrid.<wbr>mc_<wbr>custom_<wbr>fields.<wbr>listfielddefinition</code></span></summary>
<p>Run <strong>Get All Field Definitions</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_custom_fields.listfielddefinition">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_custom_fields.listfielddefinition">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_custom_fields-updatefielddefinition">
<summary><span>Update Custom Field Definition — <code>sendgrid.<wbr>mc_<wbr>custom_<wbr>fields.<wbr>updatefielddefinitio<wbr>n</code></span></summary>
<p>Run <strong>Update Custom Field Definition</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_custom_fields.updatefielddefinition">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_field_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_custom_fields.updatefielddefinition">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_field_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_custom_fields-deletefielddefinition">
<summary><span>Delete Custom Field Definition — <code>sendgrid.<wbr>mc_<wbr>custom_<wbr>fields.<wbr>deletefielddefinitio<wbr>n</code></span></summary>
<p>Run <strong>Delete Custom Field Definition</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_custom_fields.deletefielddefinition">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_field_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_custom_fields.deletefielddefinition">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_field_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-createdesign">
<summary><span>Create Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>createdesign</code></span></summary>
<p>Run <strong>Create Design</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.createdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/DesignInput&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.createdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-listdesign">
<summary><span>List Designs — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>listdesign</code></span></summary>
<p>Run <strong>List Designs</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.listdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>number of results to return</td>
<td><code>default: 100; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>token corresponding to a specific page of results, as provided by metadata</td>
<td></td>
</tr>
<tr>
<td><code>query.summary</code></td>
<td>boolean</td>
<td>Optional</td>
<td>set to false to return all fields</td>
<td><code>default: true</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.listdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-duplicatedesign">
<summary><span>Duplicate Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>duplicatedesign</code></span></summary>
<p>Run <strong>Duplicate Design</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.duplicatedesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/DesignDuplicateInput&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.duplicatedesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-getdesign">
<summary><span>Get Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>getdesign</code></span></summary>
<p>Run <strong>Get Design</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.getdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.getdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-updatedesign">
<summary><span>Update Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>updatedesign</code></span></summary>
<p>Run <strong>Update Design</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.updatedesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>Name of the Design.</td>
<td><code>default: &quot;My Design&quot;; maxLength: 100</code></td>
</tr>
<tr>
<td><code>body.html_content</code></td>
<td>string</td>
<td>Optional</td>
<td>The HTML content of the Design.</td>
<td><code>maxLength: 1048576</code></td>
</tr>
<tr>
<td><code>body.plain_content</code></td>
<td>string</td>
<td>Optional</td>
<td>Plain text content of the Design.</td>
<td><code>default: &quot;&lt;generated from html_content if left empty&gt;&quot;; maxLength: 1048576</code></td>
</tr>
<tr>
<td><code>body.generate_plain_content</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If true, plain_content is always generated from html_content. If false, plain_content is not altered.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>body.subject</code></td>
<td>string</td>
<td>Optional</td>
<td>Subject of the Design.</td>
<td><code>maxLength: 5000</code></td>
</tr>
<tr>
<td><code>body.categories</code></td>
<td>array</td>
<td>Optional</td>
<td>The list of categories applied to the design</td>
<td><code>maxItems: 10; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.categories[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 255</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.updatedesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-deletedesign">
<summary><span>Delete Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>deletedesign</code></span></summary>
<p>Run <strong>Delete Design</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.deletedesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.deletedesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-listprebuiltdesign">
<summary><span>List SendGrid Pre-built Designs — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>listprebuiltdesign</code></span></summary>
<p>Run <strong>List SendGrid Pre-built Designs</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.listprebuiltdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>number of results to return</td>
<td><code>default: 100; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>token corresponding to a specific page of results, as provided by metadata</td>
<td></td>
</tr>
<tr>
<td><code>query.summary</code></td>
<td>boolean</td>
<td>Optional</td>
<td>set to false to return all fields</td>
<td><code>default: true</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.listprebuiltdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-duplicateprebuiltdesign">
<summary><span>Duplicate SendGrid Pre-built Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>duplicateprebuiltdes<wbr>ign</code></span></summary>
<p>Run <strong>Duplicate SendGrid Pre-built Design</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.duplicateprebuiltdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the pre-built Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/DesignDuplicateInput&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.duplicateprebuiltdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_designs-getprebuiltdesign">
<summary><span>Get SendGrid Pre-built Design — <code>sendgrid.<wbr>mc_<wbr>designs.<wbr>getprebuiltdesign</code></span></summary>
<p>Run <strong>Get SendGrid Pre-built Design</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_designs.getprebuiltdesign">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the pre-built Design you want to duplicate.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_designs.getprebuiltdesign">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-createmarketinglist">
<summary><span>Create List — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>createmarketinglist</code></span></summary>
<p>Run <strong>Create List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.createmarketinglist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>Your name for your list</td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.createmarketinglist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-listmarketinglist">
<summary><span>Get All Lists — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>listmarketinglist</code></span></summary>
<p>Run <strong>Get All Lists</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.listmarketinglist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>number</td>
<td>Optional</td>
<td>Maximum number of elements to return. Defaults to 100, returns 1000 max</td>
<td><code>default: 100; minimum: 1; maximum: 1000</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.listmarketinglist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-getmarketinglist">
<summary><span>Get a List by ID — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>getmarketinglist</code></span></summary>
<p>Run <strong>Get a List by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.getmarketinglist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the list on which you want to perform the operation.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.contact_sample</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Setting this parameter to the true  will cause the contact_sample to be returned</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.getmarketinglist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-updatemarketinglist">
<summary><span>Update List — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>updatemarketinglist</code></span></summary>
<p>Run <strong>Update List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.updatemarketinglist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the list on which you want to perform the operation.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>Your name for your list.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.updatemarketinglist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-deletemarketinglist">
<summary><span>Delete a list — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>deletemarketinglist</code></span></summary>
<p>Run <strong>Delete a list</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.deletemarketinglist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the list on which you want to perform the operation.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.delete_contacts</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Flag indicates that all contacts on the list are also to be deleted.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.deletemarketinglist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-deletecontact">
<summary><span>Remove Contacts from a List — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>deletecontact</code></span></summary>
<p>Run <strong>Remove Contacts from a List</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.deletecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the list on which you want to perform the operation.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.contact_ids</code></td>
<td>string</td>
<td>Required</td>
<td>Comma separated list of contact IDs that you want to remove from the specified contacts list.</td>
<td><code>minLength: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.deletecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  },
  "query": {
    "contact_ids": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_lists-listcontactcount">
<summary><span>Get List Contact Count — <code>sendgrid.<wbr>mc_<wbr>lists.<wbr>listcontactcount</code></span></summary>
<p>Run <strong>Get List Contact Count</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_lists.listcontactcount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_lists.listcontactcount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-createsegment">
<summary><span>Create Segment — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>createsegment</code></span></summary>
<p>Run <strong>Create Segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.createsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SegmentWriteV2&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.createsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-listsegment">
<summary><span>Get List of Segments — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>listsegment</code></span></summary>
<p>Run <strong>Get List of Segments</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.listsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>A list of segment IDs to retrieve. When this parameter is included, the <code>no_parent_list_ids</code> and <code>parent_list_ids</code> parameters are ignored and only segments with given IDs are returned.</td>
<td></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.parent_list_ids</code></td>
<td>string</td>
<td>Optional</td>
<td>A comma separated list up to 50 in size, to filter segments on.  Only segments that have any of these list ids as the parent list will be retrieved. This is different from the parameter of the same name used when creating a segment.</td>
<td></td>
</tr>
<tr>
<td><code>query.no_parent_list_id</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to <code>true</code>, segments with an empty value of <code>parent_list_id</code> will be returned in the filter.  If the value is not present, it defaults to &#39;false&#39;.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.listsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-updatesegment">
<summary><span>Update Segment — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>updatesegment</code></span></summary>
<p>Run <strong>Update Segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.updatesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SegmentUpdate&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.updatesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-getsegment">
<summary><span>Get Segment by ID — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>getsegment</code></span></summary>
<p>Run <strong>Get Segment by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.getsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.contacts_sample</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Defaults to <code>true</code>. Set to <code>false</code> to exclude the contacts_sample in the response.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.getsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-deletesegment">
<summary><span>Delete segment — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>deletesegment</code></span></summary>
<p>Run <strong>Delete segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.deletesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.deletesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments_2-0-refreshsegment">
<summary><span>Manually refresh a segment — <code>sendgrid.<wbr>mc_<wbr>segments_<wbr>2.<wbr>0.<wbr>refreshsegment</code></span></summary>
<p>Run <strong>Manually refresh a segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments_2.0.refreshsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 36; maxLength: 36; format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SegmentRefreshRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments_2.0.refreshsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "00000000-0000-4000-8000-000000000000"
  },
  "body": {
    "user_time_zone": "America/Chicago"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments-listsegment">
<summary><span>Get List of Segments — <code>sendgrid.<wbr>mc_<wbr>segments.<wbr>listsegment</code></span></summary>
<p>Run <strong>Get List of Segments</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments.listsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>A list of segment IDs to retrieve. When this parameter is included, the <code>no_parent_list_ids</code> and <code>parent_list_ids</code> parameters are ignored and only segments with given IDs are returned.</td>
<td></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.parent_list_ids</code></td>
<td>string</td>
<td>Optional</td>
<td>A comma separated list of list ids to be used when searching for segments with the specified parent_list_id, no more than 50 is allowed</td>
<td></td>
</tr>
<tr>
<td><code>query.no_parent_list_id</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to <code>true</code> segments with an empty value of <code>parent_list_id</code> will be returned in the filter.  If the value is not present it defaults to &#39;false&#39;.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments.listsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments-getsegment">
<summary><span>Get Segment by ID — <code>sendgrid.<wbr>mc_<wbr>segments.<wbr>getsegment</code></span></summary>
<p>Run <strong>Get Segment by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments.getsegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 36; maxLength: 36; format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.query_json</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Defaults to <code>false</code>.  Set to <code>true</code> to return the parsed SQL AST as a JSON object in the field <code>query_json</code></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments.getsegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_segments-deletesegment">
<summary><span>Delete Segment — <code>sendgrid.<wbr>mc_<wbr>segments.<wbr>deletesegment</code></span></summary>
<p>Run <strong>Delete Segment</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_segments.deletesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 36; maxLength: 36; format: &quot;uuid&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_segments.deletesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-createsender">
<summary><span>Create a Sender — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>createsender</code></span></summary>
<p>Run <strong>Create a Sender</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.createsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.nickname</code></td>
<td>string</td>
<td>Required</td>
<td>A nickname for the Sender. Not used for sending.</td>
<td></td>
</tr>
<tr>
<td><code>body.from</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.from.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address from which your recipient will receive emails.</td>
<td></td>
</tr>
<tr>
<td><code>body.from.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name appended to the from email field. Typically your name or company name.</td>
<td></td>
</tr>
<tr>
<td><code>body.reply_to</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.reply_to.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address to which your recipient will reply.</td>
<td></td>
</tr>
<tr>
<td><code>body.reply_to.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name appended to the reply to email field. Typically your name or company name.</td>
<td></td>
</tr>
<tr>
<td><code>body.address</code></td>
<td>string</td>
<td>Required</td>
<td>The physical address of the Sender.</td>
<td></td>
</tr>
<tr>
<td><code>body.address_2</code></td>
<td>string</td>
<td>Optional</td>
<td>Additional Sender address information.</td>
<td></td>
</tr>
<tr>
<td><code>body.city</code></td>
<td>string</td>
<td>Required</td>
<td>The city of the Sender.</td>
<td></td>
</tr>
<tr>
<td><code>body.state</code></td>
<td>string</td>
<td>Optional</td>
<td>The state of the Sender.</td>
<td></td>
</tr>
<tr>
<td><code>body.zip</code></td>
<td>string</td>
<td>Optional</td>
<td>The zipcode of the Sender.</td>
<td></td>
</tr>
<tr>
<td><code>body.country</code></td>
<td>string</td>
<td>Required</td>
<td>The country of the Sender.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.createsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-listsender">
<summary><span>Get a list of all Senders — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>listsender</code></span></summary>
<p>Run <strong>Get a list of all Senders</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.listsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.listsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-getsender">
<summary><span>Get a specific Sender — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>getsender</code></span></summary>
<p>Run <strong>Get a specific Sender</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.getsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of the Sender.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.getsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-updatesender">
<summary><span>Update a Sender — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>updatesender</code></span></summary>
<p>Run <strong>Update a Sender</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.updatesender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of the Sender.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SenderRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.updatesender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-deletesender">
<summary><span>Delete a Sender — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>deletesender</code></span></summary>
<p>Run <strong>Delete a Sender</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.deletesender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of the Sender.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.deletesender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_senders-resetsenderverification">
<summary><span>Resend a Sender verification — <code>sendgrid.<wbr>mc_<wbr>senders.<wbr>resetsenderverificat<wbr>ion</code></span></summary>
<p>Run <strong>Resend a Sender verification</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_senders.resetsenderverification">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of the Sender.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_senders.resetsenderverification">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-createsinglesend">
<summary><span>Create Single Send — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>createsinglesend</code></span></summary>
<p>Run <strong>Create Single Send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.createsinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SinglesendRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.createsinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-listsinglesend">
<summary><span>Get All Single Sends — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>listsinglesend</code></span></summary>
<p>Run <strong>Get All Single Sends</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.listsinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.listsinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-deletesinglesends">
<summary><span>Bulk Delete Single Sends — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>deletesinglesends</code></span></summary>
<p>Run <strong>Bulk Delete Single Sends</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.deletesinglesends">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Single Send IDs to delete</td>
<td><code>minItems: 1; maxItems: 50</code></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.deletesinglesends">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-duplicatesinglesend">
<summary><span>Duplicate Single Send — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>duplicatesinglesend</code></span></summary>
<p>Run <strong>Duplicate Single Send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.duplicatesinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of the duplicate Single Send. If you choose to leave the name field blank, your duplicate will be assigned the name of the Single Send it was copied from with the text &#39;Copy of &#39; prepended to it. The end of the new Single Send name, including &#39;Copy of &#39;, will be trimmed if the name exceeds the character limit.</td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.duplicatesinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-updatesinglesend">
<summary><span>Update Single Send — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>updatesinglesend</code></span></summary>
<p>Run <strong>Update Single Send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.updatesinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SinglesendRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.updatesinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-getsinglesend">
<summary><span>Get Single Send by ID — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>getsinglesend</code></span></summary>
<p>Run <strong>Get Single Send by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.getsinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.getsinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-deletesinglesend">
<summary><span>Delete Single Send by ID — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>deletesinglesend</code></span></summary>
<p>Run <strong>Delete Single Send by ID</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.deletesinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.deletesinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-schedulesinglesend">
<summary><span>Schedule Single Send — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>schedulesinglesend</code></span></summary>
<p>Run <strong>Schedule Single Send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.schedulesinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.send_at</code></td>
<td>string</td>
<td>Required</td>
<td>The ISO 8601 time at which to send the Single Send. This must be in future or the string <code>now</code>. SendGrid <a href="https://docs.sendgrid.com/api-reference/mail-send/mail-send">Mail Send</a> emails can be scheduled up to 72 hours in advance. However, this scheduling constraint does not apply to emails sent via <a href="https://docs.sendgrid.com/ui/sending-email/how-to-send-email-with-marketing-campaigns/">Marketing Campaigns</a>.</td>
<td><code>format: &quot;date-time&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.schedulesinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-deletescheduledsinglesend">
<summary><span>Delete Single Send Schedule — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>deletescheduledsingl<wbr>esend</code></span></summary>
<p>Run <strong>Delete Single Send Schedule</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.deletescheduledsinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.deletescheduledsinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-listcategory">
<summary><span>Get All Categories — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>listcategory</code></span></summary>
<p>Run <strong>Get All Categories</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.listcategory">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.listcategory">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_singlesends-searchsinglesend">
<summary><span>Get Single Sends Search — <code>sendgrid.<wbr>mc_<wbr>singlesends.<wbr>searchsinglesend</code></span></summary>
<p>Run <strong>Get Single Sends Search</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_singlesends.searchsinglesend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SinglesendSearch&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_singlesends.searchsinglesend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-listautomationstat">
<summary><span>Get All Automation Stats — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>listautomationstat</code></span></summary>
<p>Run <strong>Get All Automation Stats</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.listautomationstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.automation_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>This endpoint returns all automation IDs if no <code>automation_ids</code> are specified.</td>
<td><code>minItems: 1; maxItems: 25</code></td>
</tr>
<tr>
<td><code>query.automation_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.listautomationstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-getautomationstat">
<summary><span>Get Automation Stats by ID — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>getautomationstat</code></span></summary>
<p>Run <strong>Get Automation Stats by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.getautomationstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Automation for which you want to retrieve statistics.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.group_by</code></td>
<td>array</td>
<td>Optional</td>
<td>Automations can have multiple steps. Including <code>step_id</code> as a <code>group_by</code> metric allows further granularity of stats.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Items&quot;</code></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.step_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Comma-separated list of <code>step_ids</code> that you want the link stats for.</td>
<td><code>uniqueItems: true</code></td>
</tr>
<tr>
<td><code>query.step_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>Dictates how the stats are time-sliced. Currently, <code>&quot;total&quot;</code> and <code>&quot;day&quot;</code> are supported.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;total&quot;</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Optional</td>
<td>Format: <code>YYYY-MM-DD</code>. If this parameter is included, the stats&#39; start date is included in the search.</td>
<td><code>default: &quot;2021-01-01&quot;; format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>Format: <code>YYYY-MM-DD</code>.If this parameter is included, the stats&#39; end date is included in the search.</td>
<td><code>default: &quot;2021-12-31&quot;; format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.timezone</code></td>
<td>string</td>
<td>Optional</td>
<td><a href="https://en.wikipedia.org/wiki/Tz_database#Names_of_timezones">IANA Area/Region</a> string representing the timezone in which the stats are to be presented, e.g., &quot;America/Chicago&quot;.</td>
<td><code>default: &quot;UTC&quot;</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.getautomationstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-listclicktrackingstat">
<summary><span>Get Automation Click Tracking Stats by ID — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>listclicktrackingsta<wbr>t</code></span></summary>
<p>Run <strong>Get Automation Click Tracking Stats by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.listclicktrackingstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Automation you want to get click tracking stats for.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.group_by</code></td>
<td>array</td>
<td>Optional</td>
<td>Automations can have multiple steps. Including <code>step_id</code> as a <code>group_by</code> metric allows further granularity of stats.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Items&quot;</code></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.step_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Comma-separated list of <code>step_ids</code> that you want the link stats for.</td>
<td><code>uniqueItems: true</code></td>
</tr>
<tr>
<td><code>query.step_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.listclicktrackingstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-exportautomationstat">
<summary><span>Export Single Send Stats — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>exportautomationstat</code></span></summary>
<p>Run <strong>Export Single Send Stats</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.exportautomationstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>The IDs of Single Sends for which to export stats.</td>
<td><code>minItems: 1; maxItems: 50</code></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.timezone</code></td>
<td>string</td>
<td>Optional</td>
<td>The <a href="https://en.wikipedia.org/wiki/Tz_database#Names_of_timezones">IANA Area/Region</a> string representing the timezone in which the stats are to be presented; i.e. <code>&quot;America/Chicago&quot;</code>. This parameter changes the timezone format only; it does not alter which stats are returned.</td>
<td><code>default: &quot;UTC&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.exportautomationstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-listsinglesendstat">
<summary><span>Get All Single Sends Stats — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>listsinglesendstat</code></span></summary>
<p>Run <strong>Get All Single Sends Stats</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.listsinglesendstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.singlesend_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>This endpoint returns all Single Send IDs if no IDs are included in <code>singlesend_ids</code>.</td>
<td><code>minItems: 1; maxItems: 25</code></td>
</tr>
<tr>
<td><code>query.singlesend_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.listsinglesendstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-getsinglesendstat">
<summary><span>Get Single Send Stats by ID — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>getsinglesendstat</code></span></summary>
<p>Run <strong>Get Single Send Stats by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.getsinglesendstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of Single Send for which you want to retrieve stats.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>Dictates how the stats are time-sliced. Currently, <code>&quot;total&quot;</code> and <code>&quot;day&quot;</code> are supported.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;total&quot;</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Optional</td>
<td>Format: <code>YYYY-MM-DD</code>. If this parameter is included, the stats&#39; start date is included in the search.</td>
<td><code>default: &quot;2021-01-01&quot;; format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>Format: <code>YYYY-MM-DD</code>.If this parameter is included, the stats&#39; end date is included in the search.</td>
<td><code>default: &quot;2021-12-31&quot;; format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.timezone</code></td>
<td>string</td>
<td>Optional</td>
<td><a href="https://en.wikipedia.org/wiki/Tz_database#Names_of_timezones">IANA Area/Region</a> string representing the timezone in which the stats are to be presented, e.g., &quot;America/Chicago&quot;.</td>
<td><code>default: &quot;UTC&quot;</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by</code></td>
<td>array</td>
<td>Optional</td>
<td>A/B Single Sends have multiple variation IDs and phase IDs. Including these additional fields allows further granularity of stats by these fields.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Items1&quot;</code></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.getsinglesendstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-listsinglesendtrackingstat">
<summary><span>Get Single Send Click Tracking Stats by ID — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>listsinglesendtracki<wbr>ngstat</code></span></summary>
<p>Run <strong>Get Single Send Click Tracking Stats by ID</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.listsinglesendtrackingstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of Single Send for which you want to retrieve link stats.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of elements you want returned on each page.</td>
<td><code>default: 25; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>The stats endpoints are paginated. To get the next page, call the passed <code>_metadata.next</code> URL. If <code>_metadata.prev</code> doesn&#39;t exist, you&#39;re at the first page. Similarly, if <code>_metadata.next</code> is not present, you&#39;re at the last page.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by</code></td>
<td>array</td>
<td>Optional</td>
<td>A/B Single Sends have multiple variation IDs and phase IDs. Including these additional fields allows further granularity of stats by these fields.</td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Items2&quot;</code></td>
</tr>
<tr>
<td><code>query.group_by[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.ab_variation_id</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>query.ab_phase_id</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.ab_phase_id</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AbPhaseId&quot;</code></td>
</tr>
<tr>
<td><code>query.ab_phase_id</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.listsinglesendtrackingstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_stats-exportsinglesendstat">
<summary><span>Export Single Send Stats — <code>sendgrid.<wbr>mc_<wbr>stats.<wbr>exportsinglesendstat</code></span></summary>
<p>Run <strong>Export Single Send Stats</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_stats.exportsinglesendstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ids</code></td>
<td>array</td>
<td>Optional</td>
<td>The IDs of Single Sends for which to export stats.</td>
<td><code>minItems: 1; maxItems: 50</code></td>
</tr>
<tr>
<td><code>query.ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.timezone</code></td>
<td>string</td>
<td>Optional</td>
<td>The <a href="https://en.wikipedia.org/wiki/Tz_database#Names_of_timezones">IANA Area/Region</a> string representing the timezone in which the stats are to be presented; i.e. <code>&quot;America/Chicago&quot;</code>. This parameter changes the timezone format only; it does not alter which stats are returned.</td>
<td><code>default: &quot;UTC&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_stats.exportsinglesendstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-mc_test-sendtestmarketingemail">
<summary><span>Send a Test Marketing Email — <code>sendgrid.<wbr>mc_<wbr>test.<wbr>sendtestmarketingema<wbr>il</code></span></summary>
<p>Run <strong>Send a Test Marketing Email</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.mc_test.sendtestmarketingemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.template_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the template that you would like to use. If you use a template that contains a subject and content (either text or HTML), then those values specified at the personalizations or message level will not be used.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body.version_id_override</code></td>
<td>string</td>
<td>Optional</td>
<td>You can override the active template with an alternative template version by passing the version ID in this field. If this field is blank, the active template version will be used.</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>body.sender_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>This ID must belong to a verified sender. Alternatively, you may supply a <code>from_address</code> email.</td>
<td></td>
</tr>
<tr>
<td><code>body.custom_unsubscribe_url</code></td>
<td>string</td>
<td>Optional</td>
<td>A custom unsubscribe URL.</td>
<td></td>
</tr>
<tr>
<td><code>body.suppression_group_id</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Required</td>
<td>An array of email addresses you want to send the test message to.</td>
<td><code>minItems: 1; maxItems: 10; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body.from_address</code></td>
<td>string</td>
<td>Optional</td>
<td>You can either specify this address or specify a verified sender ID.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.mc_test.sendtestmarketingemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-partner-listpartnersetting">
<summary><span>Returns a list of all partner settings. — <code>sendgrid.<wbr>partner.<wbr>listpartnersetting</code></span></summary>
<p>Run <strong>Returns a list of all partner settings.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.partner.listpartnersetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.partner.listpartnersetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-recipients_data_erasure-eraserecipientemaildata">
<summary><span>Erase recipients' email data — <code>sendgrid.<wbr>recipients_<wbr>data_<wbr>erasure.<wbr>eraserecipientemaild<wbr>ata</code></span></summary>
<p>Run <strong>Erase recipients&#39; email data</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.recipients_data_erasure.eraserecipientemaildata">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/RecipientsDataErasureEraseRecipientsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.recipients_data_erasure.eraserecipientemaildata">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "email_addresses": [
      "user1@example.com",
      "user2@example.com"
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-reverse_dns-setupreversedns">
<summary><span>Set up reverse DNS — <code>sendgrid.<wbr>reverse_<wbr>dns.<wbr>setupreversedns</code></span></summary>
<p>Run <strong>Set up reverse DNS</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.reverse_dns.setupreversedns">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.ip</code></td>
<td>string</td>
<td>Required</td>
<td>The IP address for which you want to set up reverse DNS.</td>
<td></td>
</tr>
<tr>
<td><code>body.subdomain</code></td>
<td>string</td>
<td>Optional</td>
<td>The subdomain that will be used to send emails from the IP address. This should be the same as the subdomain used to set up an authenticated domain.</td>
<td></td>
</tr>
<tr>
<td><code>body.domain</code></td>
<td>string</td>
<td>Required</td>
<td>The root, or sending, domain that will be used to send message from the IP address.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.reverse_dns.setupreversedns">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-reverse_dns-listreversedns">
<summary><span>Retrieve all reverse DNS records — <code>sendgrid.<wbr>reverse_<wbr>dns.<wbr>listreversedns</code></span></summary>
<p>Run <strong>Retrieve all reverse DNS records</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.reverse_dns.listreversedns">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.ip</code></td>
<td>string</td>
<td>Optional</td>
<td>The IP address segment that you&#39;d like to use in a prefix search.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.reverse_dns.listreversedns">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-reverse_dns-getreversedns">
<summary><span>Retrieve a reverse DNS record — <code>sendgrid.<wbr>reverse_<wbr>dns.<wbr>getreversedns</code></span></summary>
<p>Run <strong>Retrieve a reverse DNS record</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.reverse_dns.getreversedns">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the reverse DNS record that you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.reverse_dns.getreversedns">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-reverse_dns-deletereversedns">
<summary><span>Delete a reverse DNS record — <code>sendgrid.<wbr>reverse_<wbr>dns.<wbr>deletereversedns</code></span></summary>
<p>Run <strong>Delete a reverse DNS record</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.reverse_dns.deletereversedns">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the reverse DNS record that you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.reverse_dns.deletereversedns">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-reverse_dns-validatereversedns">
<summary><span>Validate a reverse DNS record — <code>sendgrid.<wbr>reverse_<wbr>dns.<wbr>validatereversedns</code></span></summary>
<p>Run <strong>Validate a reverse DNS record</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.reverse_dns.validatereversedns">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the reverse DNS record that you would like to validate.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.reverse_dns.validatereversedns">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scheduled_sends-createscheduledsend">
<summary><span>Cancel or pause a scheduled send — <code>sendgrid.<wbr>scheduled_<wbr>sends.<wbr>createscheduledsend</code></span></summary>
<p>Run <strong>Cancel or pause a scheduled send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scheduled_sends.createscheduledsend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td>Cancel or pause a scheduled send request</td>
<td></td>
</tr>
<tr>
<td><code>body.batch_id</code></td>
<td>string</td>
<td>Required</td>
<td>The batch ID is the identifier that your scheduled mail sends share.</td>
<td><code>pattern: &quot;^[a-zA-Z0-9]&quot;</code></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Status&quot;</code></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]; default: &quot;pause&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scheduled_sends.createscheduledsend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scheduled_sends-listscheduledsend">
<summary><span>Retrieve all scheduled sends — <code>sendgrid.<wbr>scheduled_<wbr>sends.<wbr>listscheduledsend</code></span></summary>
<p>Run <strong>Retrieve all scheduled sends</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scheduled_sends.listscheduledsend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scheduled_sends.listscheduledsend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scheduled_sends-getscheduledsend">
<summary><span>Retrieve scheduled send — <code>sendgrid.<wbr>scheduled_<wbr>sends.<wbr>getscheduledsend</code></span></summary>
<p>Run <strong>Retrieve scheduled send</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scheduled_sends.getscheduledsend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.batch_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scheduled_sends.getscheduledsend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "batch_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scheduled_sends-updatescheduledsend">
<summary><span>Update a scheduled send — <code>sendgrid.<wbr>scheduled_<wbr>sends.<wbr>updatescheduledsend</code></span></summary>
<p>Run <strong>Update a scheduled send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scheduled_sends.updatescheduledsend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.batch_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Status1&quot;</code></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scheduled_sends.updatescheduledsend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "batch_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scheduled_sends-deletescheduledsend">
<summary><span>Delete a cancellation or pause from a scheduled send — <code>sendgrid.<wbr>scheduled_<wbr>sends.<wbr>deletescheduledsend</code></span></summary>
<p>Run <strong>Delete a cancellation or pause from a scheduled send</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scheduled_sends.deletescheduledsend">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.batch_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scheduled_sends.deletescheduledsend">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "batch_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-scopes-listscope">
<summary><span>Retrieve a list of scopes for which this user has access. — <code>sendgrid.<wbr>scopes.<wbr>listscope</code></span></summary>
<p>Run <strong>Retrieve a list of scopes for which this user has access.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.scopes.listscope">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.scopes.listscope">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-seq-listengagementqualityscore">
<summary><span>Get Engagement Quality Scores — <code>sendgrid.<wbr>seq.<wbr>listengagementqualit<wbr>yscore</code></span></summary>
<p>Run <strong>Get Engagement Quality Scores</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.seq.listengagementqualityscore">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.from</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date in YYYY-MM-DD format (UTC) for which you want to retrieve scores.</td>
<td><code>format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.to</code></td>
<td>string</td>
<td>Required</td>
<td>The ending date in YYYY-MM-DD format (UTC) for which you want to retrieve scores.</td>
<td><code>format: &quot;date&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.seq.listengagementqualityscore">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "from": "2006-01-02",
    "to": "2006-01-02"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-seq-listsubuserengagementqualityscore">
<summary><span>Get Subusers' Engagement Quality Scores — <code>sendgrid.<wbr>seq.<wbr>listsubuserengagemen<wbr>tqualityscore</code></span></summary>
<p>Run <strong>Get Subusers&#39; Engagement Quality Scores</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.seq.listsubuserengagementqualityscore">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies the number of results to be returned by the API. This parameter can be used to limit the results returned or in combination with the <code>after_key</code> parameter to iterate through paginated results.</td>
<td><code>default: 1000; minimum: 0; maximum: 1000</code></td>
</tr>
<tr>
<td><code>query.date</code></td>
<td>string</td>
<td>Required</td>
<td>The date in YYYY-MM-DD format (UTC) for which you want to retrieve a SendGrid Engagement Quality score.</td>
<td><code>format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.after_key</code></td>
<td>integer</td>
<td>Optional</td>
<td>Specifies which items to be returned by the API. When the <code>after_key</code> is specified, the API will return items beginning from the first item after the item specified. This parameter can be used in combination with <code>limit</code> to iterate through paginated results.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.seq.listsubuserengagementqualityscore">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "date": "2026-01-01"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-createssocertificate">
<summary><span>Create an SSO Certificate — <code>sendgrid.<wbr>sso.<wbr>createssocertificate</code></span></summary>
<p>Run <strong>Create an SSO Certificate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.createssocertificate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.public_certificate</code></td>
<td>string</td>
<td>Required</td>
<td>This public certificate allows SendGrid to verify that SAML requests it receives are signed by an IdP that it recognizes.</td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if the certificate is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.integration_id</code></td>
<td>string</td>
<td>Required</td>
<td>An ID that matches a certificate to a specific IdP integration. This is the <code>id</code> returned by the &quot;Get All SSO Integrations&quot; endpoint.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.createssocertificate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-getssocertificate">
<summary><span>Get an SSO Certificate — <code>sendgrid.<wbr>sso.<wbr>getssocertificate</code></span></summary>
<p>Run <strong>Get an SSO Certificate</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.getssocertificate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.cert_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.getssocertificate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "cert_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-updatessocertificate">
<summary><span>Update SSO Certificate — <code>sendgrid.<wbr>sso.<wbr>updatessocertificate</code></span></summary>
<p>Run <strong>Update SSO Certificate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.updatessocertificate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.cert_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.public_certificate</code></td>
<td>string</td>
<td>Optional</td>
<td>This public certificate allows SendGrid to verify that SAML requests it receives are signed by an IdP that it recognizes.</td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates whether or not the certificate is enabled.</td>
<td></td>
</tr>
<tr>
<td><code>body.integration_id</code></td>
<td>string</td>
<td>Optional</td>
<td>An ID that matches a certificate to a specific IdP integration.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.updatessocertificate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "cert_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-deletessocertificate">
<summary><span>Delete an SSO Certificate — <code>sendgrid.<wbr>sso.<wbr>deletessocertificate</code></span></summary>
<p>Run <strong>Delete an SSO Certificate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.deletessocertificate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.cert_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.deletessocertificate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "cert_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-createssointegration">
<summary><span>Create an SSO Integration — <code>sendgrid.<wbr>sso.<wbr>createssointegration</code></span></summary>
<p>Run <strong>Create an SSO Integration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.createssointegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/PostPatchIntegrationRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.createssointegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-listssointegration">
<summary><span>Get All SSO Integrations — <code>sendgrid.<wbr>sso.<wbr>listssointegration</code></span></summary>
<p>Run <strong>Get All SSO Integrations</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.listssointegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.si</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If this parameter is set to <code>true</code>, the response will include the <code>completed_integration</code> field.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.listssointegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-getssointegration">
<summary><span>Get an SSO Integration — <code>sendgrid.<wbr>sso.<wbr>getssointegration</code></span></summary>
<p>Run <strong>Get an SSO Integration</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.getssointegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.si</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If this parameter is set to <code>true</code>, the response will include the <code>completed_integration</code> field.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.getssointegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-updatessointegration">
<summary><span>Update an SSO Integration — <code>sendgrid.<wbr>sso.<wbr>updatessointegration</code></span></summary>
<p>Run <strong>Update an SSO Integration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.updatessointegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.si</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If this parameter is set to <code>true</code>, the response will include the <code>completed_integration</code> field.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/PostPatchIntegrationRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.updatessointegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-deletessointegration">
<summary><span>Delete an SSO Integration — <code>sendgrid.<wbr>sso.<wbr>deletessointegration</code></span></summary>
<p>Run <strong>Delete an SSO Integration</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.deletessointegration">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.deletessointegration">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-listssointegrationcertificate">
<summary><span>Get All SSO Certificates by Integration — <code>sendgrid.<wbr>sso.<wbr>listssointegrationce<wbr>rtificate</code></span></summary>
<p>Run <strong>Get All SSO Certificates by Integration</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.listssointegrationcertificate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.integration_id</code></td>
<td>string</td>
<td>Required</td>
<td>An ID that matches a certificate to a specific IdP integration.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.listssointegrationcertificate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "integration_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-sso-updatessoteammate">
<summary><span>Edit an SSO Teammate — <code>sendgrid.<wbr>sso.<wbr>updatessoteammate</code></span></summary>
<p>Run <strong>Edit an SSO Teammate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.sso.updatessoteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.username</code></td>
<td>string</td>
<td>Required</td>
<td>Set this parameter to the Teammate&#39;s email address. This address must be the same address assigned to the Teammate in your IdP.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/PatchSsoTeammatesRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.sso.updatessoteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "username": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listbrowserstat">
<summary><span>Retrieve email statistics by browser. — <code>sendgrid.<wbr>stats.<wbr>listbrowserstat</code></span></summary>
<p>Run <strong>Retrieve email statistics by browser.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listbrowserstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.browsers</code></td>
<td>string</td>
<td>Optional</td>
<td>The browsers to get statistics for. You can include up to 10 different browsers by including this parameter multiple times.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy3&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listbrowserstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listcategory">
<summary><span>Retrieve all categories — <code>sendgrid.<wbr>stats.<wbr>listcategory</code></span></summary>
<p>Run <strong>Retrieve all categories</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listcategory">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td><code>default: 50; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.category</code></td>
<td>string</td>
<td>Optional</td>
<td>Allows you to perform a prefix search on this particular category.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listcategory">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listcategorystat">
<summary><span>Retrieve Email Statistics for Categories — <code>sendgrid.<wbr>stats.<wbr>listcategorystat</code></span></summary>
<p>Run <strong>Retrieve Email Statistics for Categories</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listcategorystat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.categories</code></td>
<td>string</td>
<td>Required</td>
<td>The individual categories that you want to retrieve statistics for. You may include up to 10 different categories.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listcategorystat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example",
    "categories": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listcategorystatsum">
<summary><span>Retrieve sums of email stats for each category. — <code>sendgrid.<wbr>stats.<wbr>listcategorystatsum</code></span></summary>
<p>Run <strong>Retrieve sums of email stats for each category.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listcategorystatsum">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>string</td>
<td>Optional</td>
<td>The metric that you want to sort by.  Must be a single metric.</td>
<td><code>default: &quot;delivered&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td>The direction you want to sort.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByDirection&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;desc&quot;</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limits the number of results returned.</td>
<td><code>default: 5</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The point in the list to begin retrieving results.</td>
<td><code>default: 0</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy1&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listcategorystatsum">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listclientstat">
<summary><span>Retrieve email statistics by client type. — <code>sendgrid.<wbr>stats.<wbr>listclientstat</code></span></summary>
<p>Run <strong>Retrieve email statistics by client type.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listclientstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy2&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listclientstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-getclientstat">
<summary><span>Retrieve stats by a specific client type. — <code>sendgrid.<wbr>stats.<wbr>getclientstat</code></span></summary>
<p>Run <strong>Retrieve stats by a specific client type.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.getclientstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.client_type</code></td>
<td>—</td>
<td>Required</td>
<td>Specifies the type of client to retrieve stats for. Must be either &quot;phone&quot;, &quot;tablet&quot;, &quot;webmail&quot;, or &quot;desktop&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>path.client_type</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/ClientType&quot;</code></td>
</tr>
<tr>
<td><code>path.client_type</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy2&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.getclientstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "client_type": "phone"
  },
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listdevicestat">
<summary><span>Retrieve email statistics by device type. — <code>sendgrid.<wbr>stats.<wbr>listdevicestat</code></span></summary>
<p>Run <strong>Retrieve email statistics by device type.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listdevicestat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy3&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listdevicestat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-listmailboxproviderstat">
<summary><span>Retrieve email statistics by mailbox provider. — <code>sendgrid.<wbr>stats.<wbr>listmailboxproviders<wbr>tat</code></span></summary>
<p>Run <strong>Retrieve email statistics by mailbox provider.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.listmailboxproviderstat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.mailbox_providers</code></td>
<td>string</td>
<td>Optional</td>
<td>The mail box providers to get statistics for. You can include up to 10 by including this parameter multiple times.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy3&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.listmailboxproviderstat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-stats-liststat">
<summary><span>Retrieve global email statistics — <code>sendgrid.<wbr>stats.<wbr>liststat</code></span></summary>
<p>Run <strong>Retrieve global email statistics</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.stats.liststat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy3&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.stats.liststat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-listsubuser">
<summary><span>List all Subusers — <code>sendgrid.<wbr>subusers.<wbr>listsubuser</code></span></summary>
<p>Run <strong>List all Subusers</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.listsubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td>The username of this subuser.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td>Filter for Subusers in this region. If not provided, all Subusers will be returned. All users can also be explicitly requested by using the filter <code>all</code>. Users who are not pinned to a region will be displayed as <code>global</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region&quot;</code></td>
</tr>
<tr>
<td><code>query.region</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;all&quot;</code></td>
</tr>
<tr>
<td><code>query.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Optional flag to include the regions of the Subusers in the response. If not provided, the region will be omitted from the response.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.listsubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-createsubuser">
<summary><span>Create Subuser — <code>sendgrid.<wbr>subusers.<wbr>createsubuser</code></span></summary>
<p>Run <strong>Create Subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.createsubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username for this subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the subuser.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>body.password</code></td>
<td>string</td>
<td>Required</td>
<td>The password this subuser will use when logging into SendGrid.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips</code></td>
<td>array</td>
<td>Required</td>
<td>The IP addresses that should be assigned to this subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body.ips[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;ipv4&quot;</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Region1&quot;</code></td>
</tr>
<tr>
<td><code>body.region</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;global&quot;</code></td>
</tr>
<tr>
<td><code>body.include_region</code></td>
<td>boolean</td>
<td>Optional</td>
<td>A flag that determines if the Subuser&#39;s region should be returned in the response. (Regional email is in Public Beta and requires SendGrid Pro plan or above.)</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.createsubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-updatesubuser">
<summary><span>Enable/disable a subuser — <code>sendgrid.<wbr>subusers.<wbr>updatesubuser</code></span></summary>
<p>Run <strong>Enable/disable a subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.updatesubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.disabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Whether or not this subuser is disabled. <code>true</code> means disabled, <code>false</code> means enabled.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.updatesubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-deletesubuser">
<summary><span>Delete a subuser — <code>sendgrid.<wbr>subusers.<wbr>deletesubuser</code></span></summary>
<p>Run <strong>Delete a subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.deletesubuser">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.deletesubuser">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-updatesubuserwebsiteaccess">
<summary><span>Enable/Disable website access for a Subuser — <code>sendgrid.<wbr>subusers.<wbr>updatesubuserwebsite<wbr>access</code></span></summary>
<p>Run <strong>Enable/Disable website access for a Subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.updatesubuserwebsiteaccess">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.disabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Whether or not to disable website access to the Subuser. <code>true</code> means disabled, <code>false</code> means enabled.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.updatesubuserwebsiteaccess">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-getsubusercredit">
<summary><span>Get the Credits for a Subuser — <code>sendgrid.<wbr>subusers.<wbr>getsubusercredit</code></span></summary>
<p>Run <strong>Get the Credits for a Subuser</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.getsubusercredit">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.getsubusercredit">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-updatesubusercredit">
<summary><span>Update the Credits for a Subuser — <code>sendgrid.<wbr>subusers.<wbr>updatesubusercredit</code></span></summary>
<p>Run <strong>Update the Credits for a Subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.updatesubusercredit">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SubuserCreditsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.updatesubusercredit">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  },
  "body": {
    "type": "unlimited"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-updatesubuserremainingcredit">
<summary><span>Update the remaining credits for a Subuser — <code>sendgrid.<wbr>subusers.<wbr>updatesubuserremaini<wbr>ngcredit</code></span></summary>
<p>Run <strong>Update the remaining credits for a Subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.updatesubuserremainingcredit">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.allocation_update</code></td>
<td>integer</td>
<td>Required</td>
<td>The number of credits to add to or subtract from the current remaining credits for the Subuser. Use a positive number to increase the remaining credits or a negative number to reduce the remaining credits.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.updatesubuserremainingcredit">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  },
  "body": {
    "allocation_update": 99
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-updatesubuserip">
<summary><span>Update IPs assigned to a subuser — <code>sendgrid.<wbr>subusers.<wbr>updatesubuserip</code></span></summary>
<p>Run <strong>Update IPs assigned to a subuser</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.updatesubuserip">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>array</td>
<td>Optional</td>
<td>The IP addresses you would like to assign to the subuser.</td>
<td></td>
</tr>
<tr>
<td><code>body[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;ipv4&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.updatesubuserip">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-listsubusermonthlystat">
<summary><span>Retrieve the monthly email statistics for a single subuser — <code>sendgrid.<wbr>subusers.<wbr>listsubusermonthlyst<wbr>at</code></span></summary>
<p>Run <strong>Retrieve the monthly email statistics for a single subuser</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.listsubusermonthlystat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.subuser_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Subuser.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.date</code></td>
<td>string</td>
<td>Required</td>
<td>The date of the month to retrieve statistics for. Must be formatted YYYY-MM-DD</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>string</td>
<td>Optional</td>
<td>The metric that you want to sort by. Metrics that you can sort by are: <code>blocks</code>, <code>bounces</code>, <code>clicks</code>, <code>delivered</code>, <code>opens</code>, <code>requests</code>, <code>unique_clicks</code>, <code>unique_opens</code>, and <code>unsubscribes</code>.&#39;</td>
<td><code>default: &quot;delivered&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td>The direction you want to sort.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByDirection&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;desc&quot;</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Optional field to limit the number of results returned.</td>
<td><code>default: 5</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>Optional beginning point in the list to retrieve from.</td>
<td><code>default: 0</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.listsubusermonthlystat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "subuser_name": "example"
  },
  "query": {
    "date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-listreputation">
<summary><span>Retrieve Subuser Reputations — <code>sendgrid.<wbr>subusers.<wbr>listreputation</code></span></summary>
<p>Run <strong>Retrieve Subuser Reputations</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.listreputation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.usernames</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.listreputation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-liststat">
<summary><span>Retrieve email statistics for your subusers. — <code>sendgrid.<wbr>subusers.<wbr>liststat</code></span></summary>
<p>Run <strong>Retrieve email statistics for your subusers.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.liststat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limits the number of results returned per page.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The point in the list to begin retrieving results from.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How to group the statistics. Must be either &quot;day&quot;, &quot;week&quot;, or &quot;month&quot;.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.subusers</code></td>
<td>string</td>
<td>Required</td>
<td>The subuser you want to retrieve statistics for. You may include this parameter up to 10 times to retrieve statistics for multiple subusers.</td>
<td></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.liststat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "subusers": "example",
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-listmonthlystat">
<summary><span>Retrieve monthly stats for all subusers — <code>sendgrid.<wbr>subusers.<wbr>listmonthlystat</code></span></summary>
<p>Run <strong>Retrieve monthly stats for all subusers</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.listmonthlystat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.date</code></td>
<td>string</td>
<td>Required</td>
<td>The date of the month to retrieve statistics for. Must be formatted YYYY-MM-DD</td>
<td></td>
</tr>
<tr>
<td><code>query.subuser</code></td>
<td>string</td>
<td>Optional</td>
<td>A substring search of your subusers.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>—</td>
<td>Optional</td>
<td>The metric that you want to sort by. Metrics that you can sort by are: <code>blocks</code>, <code>bounces</code>, <code>clicks</code>, <code>delivered</code>, <code>opens</code>, <code>requests</code>, <code>unique_clicks</code>, <code>unique_opens</code>, and <code>unsubscribes</code>.&#39;</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByMetric&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;delivered&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td>The direction you want to sort.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByDirection1&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;desc&quot;</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Optional field to limit the number of results returned.</td>
<td><code>default: 5</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>Optional beginning point in the list to retrieve from.</td>
<td><code>default: 0</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.listmonthlystat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-subusers-liststatsum">
<summary><span>Retrieve the totals for each email statistic metric for all subusers. — <code>sendgrid.<wbr>subusers.<wbr>liststatsum</code></span></summary>
<p>Run <strong>Retrieve the totals for each email statistic metric for all subusers.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.subusers.liststatsum">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td>The direction you want to sort.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/SortByDirection2&quot;</code></td>
</tr>
<tr>
<td><code>query.sort_by_direction</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;desc&quot;</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics to retrieve. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics to retrieve. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limits the number of results returned per page.</td>
<td><code>default: 5</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The point in the list to begin retrieving results from.</td>
<td><code>default: 0</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td>How to group the statistics. Defaults to today. Must follow format YYYY-MM-DD.</td>
<td></td>
</tr>
<tr>
<td><code>query.sort_by_metric</code></td>
<td>string</td>
<td>Optional</td>
<td>The metric that you want to sort by.  Must be a single metric.</td>
<td><code>default: &quot;delivered&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.subusers.liststatsum">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-creatasmgroup">
<summary><span>Create a new suppression group — <code>sendgrid.<wbr>suppressions.<wbr>creatasmgroup</code></span></summary>
<p>Run <strong>Create a new suppression group</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.creatasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SuppressionGroupRequestBaseProps&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.creatasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listasmgroup">
<summary><span>Retrieve all suppression groups associated with the user. — <code>sendgrid.<wbr>suppressions.<wbr>listasmgroup</code></span></summary>
<p>Run <strong>Retrieve all suppression groups associated with the user.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.id</code></td>
<td>integer</td>
<td>Optional</td>
<td>The ID of the suppression group(s) you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getasmgroup">
<summary><span>Get information on a single suppression group. — <code>sendgrid.<wbr>suppressions.<wbr>getasmgroup</code></span></summary>
<p>Run <strong>Get information on a single suppression group.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the suppression group you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-updateasmgroup">
<summary><span>Update a suppression group. — <code>sendgrid.<wbr>suppressions.<wbr>updateasmgroup</code></span></summary>
<p>Run <strong>Update a suppression group.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.updateasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the suppression group you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of your suppression group. Required when creating a group.</td>
<td><code>maxLength: 30</code></td>
</tr>
<tr>
<td><code>body.description</code></td>
<td>string</td>
<td>Optional</td>
<td>A brief description of your suppression group. Required when creating a group.</td>
<td><code>maxLength: 100</code></td>
</tr>
<tr>
<td><code>body.is_default</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if you would like this to be your default suppression group.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.updateasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deleteasmgroup">
<summary><span>Delete a Suppression Group — <code>sendgrid.<wbr>suppressions.<wbr>deleteasmgroup</code></span></summary>
<p>Run <strong>Delete a Suppression Group</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deleteasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the suppression group you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deleteasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-addsuppressiontoasmgroup">
<summary><span>Add suppressions to a suppression group — <code>sendgrid.<wbr>suppressions.<wbr>addsuppressiontoasmg<wbr>roup</code></span></summary>
<p>Run <strong>Add suppressions to a suppression group</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.addsuppressiontoasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the unsubscribe group that you are adding suppressions to.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SuppressionsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.addsuppressiontoasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listsuppressionfromasmgroup">
<summary><span>Retrieve all suppressions for a suppression group — <code>sendgrid.<wbr>suppressions.<wbr>listsuppressionfroma<wbr>smgroup</code></span></summary>
<p>Run <strong>Retrieve all suppressions for a suppression group</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listsuppressionfromasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the unsubscribe group that you are adding suppressions to.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listsuppressionfromasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletesuppressionfromasmgroup">
<summary><span>Delete a suppression from a suppression group — <code>sendgrid.<wbr>suppressions.<wbr>deletesuppressionfro<wbr>masmgroup</code></span></summary>
<p>Run <strong>Delete a suppression from a suppression group</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletesuppressionfromasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the suppression group that you are removing an email address from.</td>
<td></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address that you want to remove from the suppression group.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletesuppressionfromasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example",
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-searchsuppressionfromasmgroup">
<summary><span>Search for suppressions within a group — <code>sendgrid.<wbr>suppressions.<wbr>searchsuppressionfro<wbr>masmgroup</code></span></summary>
<p>Run <strong>Search for suppressions within a group</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.searchsuppressionfromasmgroup">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.group_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the suppression group that you would like to search.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SuppressionsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.searchsuppressionfromasmgroup">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "group_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listasmsuppression">
<summary><span>Retrieve all suppressions — <code>sendgrid.<wbr>suppressions.<wbr>listasmsuppression</code></span></summary>
<p>Run <strong>Retrieve all suppressions</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listasmsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listasmsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getasmsuppression">
<summary><span>Retrieve all suppression groups for an email address — <code>sendgrid.<wbr>suppressions.<wbr>getasmsuppression</code></span></summary>
<p>Run <strong>Retrieve all suppression groups for an email address</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getasmsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address that you want to search suppression groups for.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getasmsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listsuppressionblock">
<summary><span>Retrieve all blocks — <code>sendgrid.<wbr>suppressions.<wbr>listsuppressionblock</code></span></summary>
<p>Run <strong>Retrieve all blocks</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listsuppressionblock">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>The start of the time range when a blocked email was created (inclusive). This is a unix timestamp.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>The end of the time range when a blocked email was created (inclusive). This is a unix timestamp.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>minimum: 1; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies which records to return based on the records&#39; associated email addresses. For example, <code>sales</code> returns records with email addresses that start with &#39;sales&#39;, such as <code>salesdepartment@example.com</code> or <code>sales@example.com</code>.  You can also use <code>%25</code> as a wildcard. For example, <code>%25market</code> returns records containing email addresses with the string &#39;market&#39; anywhere in the email address, and <code>%25market%25tree</code> returns records containing email addresses with the string &#39;market&#39; followed by the string &#39;tree&#39;. Any reserved characters should be <a href="https://en.wikipedia.org/wiki/Percent-encoding#Reserved_characters">percent-encoded</a>, e.g., the <code>@</code> symbol should be encoded as <code>%40</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listsuppressionblock">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletesuppressionblocks">
<summary><span>Delete blocks — <code>sendgrid.<wbr>suppressions.<wbr>deletesuppressionblo<wbr>cks</code></span></summary>
<p>Run <strong>Delete blocks</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletesuppressionblocks">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.delete_all</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if you want to delete all blocked email addresses.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Optional</td>
<td>The specific blocked email addresses that you want to delete.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletesuppressionblocks">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getsuppressionblock">
<summary><span>Retrieve a specific block — <code>sendgrid.<wbr>suppressions.<wbr>getsuppressionblock</code></span></summary>
<p>Run <strong>Retrieve a specific block</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getsuppressionblock">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the specific block.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getsuppressionblock">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletesuppressionblock">
<summary><span>Delete a specific block — <code>sendgrid.<wbr>suppressions.<wbr>deletesuppressionblo<wbr>ck</code></span></summary>
<p>Run <strong>Delete a specific block</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletesuppressionblock">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the specific block.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletesuppressionblock">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listsuppressionbounces">
<summary><span>Retrieve all bounces — <code>sendgrid.<wbr>suppressions.<wbr>listsuppressionbounc<wbr>es</code></span></summary>
<p>Run <strong>Retrieve all bounces</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listsuppressionbounces">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers start of the time range in unix timestamp when a bounce was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers end of the time range in unix timestamp when a bounce was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>minimum: 1; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies which records to return based on the records&#39; associated email addresses. For example, <code>sales</code> returns records with email addresses that start with &#39;sales&#39;, such as <code>salesdepartment@example.com</code> or <code>sales@example.com</code>.  You can also use <code>%25</code> as a wildcard. For example, <code>%25market</code> returns records containing email addresses with the string &#39;market&#39; anywhere in the email address, and <code>%25market%25tree</code> returns records containing email addresses with the string &#39;market&#39; followed by the string &#39;tree&#39;. Any reserved characters should be <a href="https://en.wikipedia.org/wiki/Percent-encoding#Reserved_characters">percent-encoded</a>, e.g., the <code>@</code> symbol should be encoded as <code>%40</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>default: &quot;application/json&quot;</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listsuppressionbounces">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "headers": {
    "Accept": "application/json"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletesuppressionbounces">
<summary><span>Delete bounces — <code>sendgrid.<wbr>suppressions.<wbr>deletesuppressionbou<wbr>nces</code></span></summary>
<p>Run <strong>Delete bounces</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletesuppressionbounces">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.delete_all</code></td>
<td>boolean</td>
<td>Optional</td>
<td>This parameter allows you to delete <strong>every</strong> email in your bounce list. This should not be used with the emails parameter.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Optional</td>
<td>Delete multiple emails from your bounce list at the same time. This should not be used with the delete_all parameter.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletesuppressionbounces">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getsuppressionbounces">
<summary><span>Retrieve a Bounce — <code>sendgrid.<wbr>suppressions.<wbr>getsuppressionbounce<wbr>s</code></span></summary>
<p>Run <strong>Retrieve a Bounce</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getsuppressionbounces">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the specific bounce you would like to retrieve</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getsuppressionbounces">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletesuppressionbounce">
<summary><span>Delete a bounce — <code>sendgrid.<wbr>suppressions.<wbr>deletesuppressionbou<wbr>nce</code></span></summary>
<p>Run <strong>Delete a bounce</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletesuppressionbounce">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address you would like to remove from the bounce list.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletesuppressionbounce">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listsuppressionbouncesclassifications">
<summary><span>Retrieve bounce classification totals — <code>sendgrid.<wbr>suppressions.<wbr>listsuppressionbounc<wbr>esclassifications</code></span></summary>
<p>Run <strong>Retrieve bounce classification totals</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listsuppressionbouncesclassifications">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>—</td>
<td>Required</td>
<td>Specifies the content type to be returned by this endpoint. You can choose to receive CSV-formatted data by passing &quot;text/csv&quot; in the header.</td>
<td></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Accept&quot;</code></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]; default: &quot;application/json&quot;</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The start of the time range, in YYYY-MM-DD format, when a bounce was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end of the time range, in YYYY-MM-DD format, when a bounce was created (inclusive).</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listsuppressionbouncesclassifications">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "headers": {
    "Accept": "application/json"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getsuppressionbouncesclassifications">
<summary><span>Retrieve bounce classification over time by domain stats — <code>sendgrid.<wbr>suppressions.<wbr>getsuppressionbounce<wbr>sclassifications</code></span></summary>
<p>Run <strong>Retrieve bounce classification over time by domain stats</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getsuppressionbouncesclassifications">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>—</td>
<td>Required</td>
<td>Specifies the content type to be returned by this endpoint. You can choose to receive CSV-formatted data by passing &quot;text/csv&quot; in the header.</td>
<td></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Accept1&quot;</code></td>
</tr>
<tr>
<td><code>headers.Accept</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]; default: &quot;application/json&quot;</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.classification</code></td>
<td>—</td>
<td>Required</td>
<td>The classification you want to filter by. Possible values are: <code>Content</code>, <code>Frequency or Volume Too High</code>, <code>Invalid Address</code>, <code>Mailbox Unavailable</code>, <code>Reputation</code>, <code>Technical Failure</code>, <code>Unclassified</code>.</td>
<td></td>
</tr>
<tr>
<td><code>path.classification</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Classification1&quot;</code></td>
</tr>
<tr>
<td><code>path.classification</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The start of the time range, in YYYY-MM-DD format, when a bounce was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end of the time range, in YYYY-MM-DD format, when a bounce was created (inclusive).</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getsuppressionbouncesclassifications">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "headers": {
    "Accept": "application/json"
  },
  "path": {
    "classification": "Content"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-createglobalsuppression">
<summary><span>Add recipient addresses to the global suppression group. — <code>sendgrid.<wbr>suppressions.<wbr>createglobalsuppress<wbr>ion</code></span></summary>
<p>Run <strong>Add recipient addresses to the global suppression group.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.createglobalsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SuppressionsRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.createglobalsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getglobalsuppression">
<summary><span>Retrieve a Global Suppression — <code>sendgrid.<wbr>suppressions.<wbr>getglobalsuppression</code></span></summary>
<p>Run <strong>Retrieve a Global Suppression</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getglobalsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the global suppression you want to retrieve. Or, if you want to check if an email address is on the global suppressions list, enter that email address here.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getglobalsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deleteglobalsuppression">
<summary><span>Delete a Global Suppression — <code>sendgrid.<wbr>suppressions.<wbr>deleteglobalsuppress<wbr>ion</code></span></summary>
<p>Run <strong>Delete a Global Suppression</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deleteglobalsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of the global suppression you want to retrieve. Or, if you want to check if an email address is on the global suppressions list, enter that email address here.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deleteglobalsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listinvalidemail">
<summary><span>Retrieve all invalid emails — <code>sendgrid.<wbr>suppressions.<wbr>listinvalidemail</code></span></summary>
<p>Run <strong>Retrieve all invalid emails</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listinvalidemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers start of the time range in unix timestamp when an invalid email was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers end of the time range in unix timestamp when an invalid email was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>minimum: 1; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>This parameter allows you to filter results by email address. Only invalid addresses matching an address passed in this parameter will be returned.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listinvalidemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deleteinvalidemails">
<summary><span>Delete invalid emails — <code>sendgrid.<wbr>suppressions.<wbr>deleteinvalidemails</code></span></summary>
<p>Run <strong>Delete invalid emails</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deleteinvalidemails">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.delete_all</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if you want to remove all email address from the invalid emails list.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Optional</td>
<td>The list of specific email addresses that you want to remove.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deleteinvalidemails">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getinvalidemail">
<summary><span>Retrieve a specific invalid email — <code>sendgrid.<wbr>suppressions.<wbr>getinvalidemail</code></span></summary>
<p>Run <strong>Retrieve a specific invalid email</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getinvalidemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The specific email address of the invalid email entry that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getinvalidemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deleteinvalidemail">
<summary><span>Delete a specific invalid email — <code>sendgrid.<wbr>suppressions.<wbr>deleteinvalidemail</code></span></summary>
<p>Run <strong>Delete a specific invalid email</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deleteinvalidemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The specific email address of the invalid email entry that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deleteinvalidemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listspamreport">
<summary><span>Retrieve all spam reports — <code>sendgrid.<wbr>suppressions.<wbr>listspamreport</code></span></summary>
<p>Run <strong>Retrieve all spam reports</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listspamreport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>The start of the time range when a spam report was created (inclusive). This is a unix timestamp.</td>
<td></td>
</tr>
<tr>
<td><code>query.end_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>The end of the time range when a spam report was created (inclusive). This is a unix timestamp.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>minimum: 1; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies which records to return based on the records&#39; associated email addresses. For example, <code>sales</code> returns records with email addresses that start with &#39;sales&#39;, such as <code>salesdepartment@example.com</code> or <code>sales@example.com</code>.  You can also use <code>%25</code> as a wildcard. For example, <code>%25market</code> returns records containing email addresses with the string &#39;market&#39; anywhere in the email address, and <code>%25market%25tree</code> returns records containing email addresses with the string &#39;market&#39; followed by the string &#39;tree&#39;. Any reserved characters should be <a href="https://en.wikipedia.org/wiki/Percent-encoding#Reserved_characters">percent-encoded</a>, e.g., the <code>@</code> symbol should be encoded as <code>%40</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listspamreport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletespamreports">
<summary><span>Delete spam reports — <code>sendgrid.<wbr>suppressions.<wbr>deletespamreports</code></span></summary>
<p>Run <strong>Delete spam reports</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletespamreports">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.delete_all</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Indicates if you want to delete all email addresses on the spam report list.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails</code></td>
<td>array</td>
<td>Optional</td>
<td>A list of specific email addresses that you want to remove from the spam report list.</td>
<td></td>
</tr>
<tr>
<td><code>body.emails[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletespamreports">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-getspamreport">
<summary><span>Retrieve a specific spam report — <code>sendgrid.<wbr>suppressions.<wbr>getspamreport</code></span></summary>
<p>Run <strong>Retrieve a specific spam report</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.getspamreport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of a specific spam report that you want to retrieve.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.getspamreport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-deletespamreport">
<summary><span>Delete a specific spam report — <code>sendgrid.<wbr>suppressions.<wbr>deletespamreport</code></span></summary>
<p>Run <strong>Delete a specific spam report</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.deletespamreport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.email</code></td>
<td>string</td>
<td>Required</td>
<td>The email address of a specific spam report that you want to retrieve.</td>
<td><code>format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.deletespamreport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "email": "developer@example.com"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-suppressions-listglobalsuppression">
<summary><span>Retrieve all global suppressions — <code>sendgrid.<wbr>suppressions.<wbr>listglobalsuppressio<wbr>n</code></span></summary>
<p>Run <strong>Retrieve all global suppressions</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.suppressions.listglobalsuppression">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers start of the time range in unix timestamp when an unsubscribe email was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_time</code></td>
<td>integer</td>
<td>Optional</td>
<td>Refers end of the time range in unix timestamp when an unsubscribe email was created (inclusive).</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>minimum: 1; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>Specifies which records to return based on the records&#39; associated email addresses. For example, <code>sales</code> returns records with email addresses that start with &#39;sales&#39;, such as <code>salesdepartment@example.com</code> or <code>sales@example.com</code>.  You can also use <code>%25</code> as a wildcard. For example, <code>%25market</code> returns records containing email addresses with the string &#39;market&#39; anywhere in the email address, and <code>%25market%25tree</code> returns records containing email addresses with the string &#39;market&#39; followed by the string &#39;tree&#39;. Any reserved characters should be <a href="https://en.wikipedia.org/wiki/Percent-encoding#Reserved_characters">percent-encoded</a>, e.g., the <code>@</code> symbol should be encoded as <code>%40</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). It is important to use the Base URL that corresponds to the region of the account or Subuser you specify in the <code>on-behalf-of</code> header. See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.suppressions.listglobalsuppression">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-inviteteammate">
<summary><span>Invite teammate — <code>sendgrid.<wbr>teammates.<wbr>inviteteammate</code></span></summary>
<p>Run <strong>Invite teammate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.inviteteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.email</code></td>
<td>string</td>
<td>Required</td>
<td>New teammate&#39;s email</td>
<td><code>minLength: 5; maxLength: 255; pattern: &quot;^.*@.*\\..*&quot;</code></td>
</tr>
<tr>
<td><code>body.scopes</code></td>
<td>array</td>
<td>Required</td>
<td>Set to specify list of scopes that teammate should have. Should be empty if teammate is an admin.</td>
<td></td>
</tr>
<tr>
<td><code>body.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.is_admin</code></td>
<td>boolean</td>
<td>Required</td>
<td>Set to true if teammate should be an admin user</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.inviteteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-listteammate">
<summary><span>Retrieve all teammates — <code>sendgrid.<wbr>teammates.<wbr>listteammate</code></span></summary>
<p>Run <strong>Retrieve all teammates</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.listteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td><code>limit</code> sets the page size, i.e. maximum number of items from the list to be returned for a single API request. If omitted, the default page size is used. The maximum page size for this endpoint is 500 items per page.</td>
<td><code>default: 500; minimum: 0; maximum: 500</code></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of items in the list to skip over before starting to retrieve the items for the requested page. The default <code>offset</code> of <code>0</code> represents the beginning of the list, i.e. the start of the first page. To request the second page of the list, set the <code>offset</code> to the page size as determined by <code>limit</code>. Use multiples of the page size as your <code>offset</code> to request further consecutive pages. E.g. assume your page size is set to <code>10</code>. An <code>offset</code> of <code>10</code> requests the second page, an <code>offset</code> of <code>20</code> requests the third page and so on, provided there are sufficiently many items in your list.</td>
<td><code>default: 0; minimum: 0</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.listteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-listsubuserbytemplate">
<summary><span>Get Teammate Subuser Access — <code>sendgrid.<wbr>teammates.<wbr>listsubuserbytemplat<wbr>e</code></span></summary>
<p>Run <strong>Get Teammate Subuser Access</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.listsubuserbytemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.teammate_name</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the Teammate for whom you want to retrieve Subuser access information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.after_subuser_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>The Subuser ID from which the API request will begin retrieving Subusers. This query parameter can be used in successive API calls to retrieve additional Subusers.</td>
<td></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Limit the number of Subusers to be returned. The default <code>limit</code> is <code>100</code> per request.</td>
<td><code>default: 100</code></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td>A Subuser&#39;s username that will be used to filter the returned result.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.listsubuserbytemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "teammate_name": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-getteammate">
<summary><span>Retrieve specific teammate — <code>sendgrid.<wbr>teammates.<wbr>getteammate</code></span></summary>
<p>Run <strong>Retrieve specific teammate</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.getteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the teammate that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.getteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-updateteammate">
<summary><span>Update teammate's permissions — <code>sendgrid.<wbr>teammates.<wbr>updateteammate</code></span></summary>
<p>Run <strong>Update teammate&#39;s permissions</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.updateteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the teammate that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.scopes</code></td>
<td>array</td>
<td>Required</td>
<td>Provide list of scopes that should be given to teammate. If specifying list of scopes, is_admin should be set to False.</td>
<td></td>
</tr>
<tr>
<td><code>body.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.is_admin</code></td>
<td>boolean</td>
<td>Required</td>
<td>Set to True if this teammate should be promoted to an admin user. If True, scopes should be an empty array.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.updateteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-deleteteammate">
<summary><span>Delete teammate — <code>sendgrid.<wbr>teammates.<wbr>deleteteammate</code></span></summary>
<p>Run <strong>Delete teammate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.deleteteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.username</code></td>
<td>string</td>
<td>Required</td>
<td>The username of the teammate that you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.deleteteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "username": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-listpendingteammate">
<summary><span>Retrieve all pending teammates — <code>sendgrid.<wbr>teammates.<wbr>listpendingteammate</code></span></summary>
<p>Run <strong>Retrieve all pending teammates</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.listpendingteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.listpendingteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-deletependingteammate">
<summary><span>Delete pending teammate — <code>sendgrid.<wbr>teammates.<wbr>deletependingteammat<wbr>e</code></span></summary>
<p>Run <strong>Delete pending teammate</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.deletependingteammate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.token</code></td>
<td>string</td>
<td>Required</td>
<td>The token for the invite you want to delete.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.deletependingteammate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "token": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-teammates-resendteammateinvite">
<summary><span>Resend teammate invite — <code>sendgrid.<wbr>teammates.<wbr>resendteammateinvite</code></span></summary>
<p>Run <strong>Resend teammate invite</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.teammates.resendteammateinvite">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.token</code></td>
<td>string</td>
<td>Required</td>
<td>The token for the invite that you want to resend.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.teammates.resendteammateinvite">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "token": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-createtemplate">
<summary><span>Create a transactional template. — <code>sendgrid.<wbr>templates.<wbr>createtemplate</code></span></summary>
<p>Run <strong>Create a transactional template.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.createtemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name for the new transactional template.</td>
<td><code>maxLength: 100</code></td>
</tr>
<tr>
<td><code>body.generation</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.generation</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Generation&quot;</code></td>
</tr>
<tr>
<td><code>body.generation</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;legacy&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.createtemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-listtemplate">
<summary><span>Retrieve paged transactional templates. — <code>sendgrid.<wbr>templates.<wbr>listtemplate</code></span></summary>
<p>Run <strong>Retrieve paged transactional templates.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.listtemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.generations</code></td>
<td>—</td>
<td>Optional</td>
<td>Comma-delimited list specifying which generations of templates to return. Options are <code>legacy</code>, <code>dynamic</code> or <code>legacy,dynamic</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.generations</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/Generations&quot;</code></td>
</tr>
<tr>
<td><code>query.generations</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]; default: &quot;legacy&quot;</code></td>
</tr>
<tr>
<td><code>query.page_size</code></td>
<td>number</td>
<td>Required</td>
<td>The number of templates to be returned in each page of results</td>
<td><code>minimum: 1; maximum: 200</code></td>
</tr>
<tr>
<td><code>query.page_token</code></td>
<td>string</td>
<td>Optional</td>
<td>A token corresponding to a specific page of results, as provided by metadata</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.listtemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "page_size": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-duplicatetemplate">
<summary><span>Duplicate a transactional template. — <code>sendgrid.<wbr>templates.<wbr>duplicatetemplate</code></span></summary>
<p>Run <strong>Duplicate a transactional template.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.duplicatetemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name for the new transactional template.</td>
<td><code>maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.duplicatetemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-gettemplate">
<summary><span>Retrieve a single transactional template. — <code>sendgrid.<wbr>templates.<wbr>gettemplate</code></span></summary>
<p>Run <strong>Retrieve a single transactional template.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.gettemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.gettemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-updatetemplate">
<summary><span>Edit a transactional template. — <code>sendgrid.<wbr>templates.<wbr>updatetemplate</code></span></summary>
<p>Run <strong>Edit a transactional template.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.updatetemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of the transactional template.</td>
<td><code>maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.updatetemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-deletetemplate">
<summary><span>Delete a template. — <code>sendgrid.<wbr>templates.<wbr>deletetemplate</code></span></summary>
<p>Run <strong>Delete a template.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.deletetemplate">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.deletetemplate">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-createtemplateversion">
<summary><span>Create a new transactional template version. — <code>sendgrid.<wbr>templates.<wbr>createtemplateversio<wbr>n</code></span></summary>
<p>Run <strong>Create a new transactional template version.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.createtemplateversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/TransactionalTemplateVersionCreate&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.createtemplateversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-gettemplateversion">
<summary><span>Retrieve a specific transactional template version. — <code>sendgrid.<wbr>templates.<wbr>gettemplateversion</code></span></summary>
<p>Run <strong>Retrieve a specific transactional template version.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.gettemplateversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the original template</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the template version</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.gettemplateversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "00000000-0000-4000-8000-000000000000",
    "version_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-updatetemplateversion">
<summary><span>Edit a transactional template version. — <code>sendgrid.<wbr>templates.<wbr>updatetemplateversio<wbr>n</code></span></summary>
<p>Run <strong>Edit a transactional template version.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.updatetemplateversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the original template</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the template version</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/TransactionalTemplateVersionCreate&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.updatetemplateversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "00000000-0000-4000-8000-000000000000",
    "version_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-deletetemplateversion">
<summary><span>Delete a transactional template version. — <code>sendgrid.<wbr>templates.<wbr>deletetemplateversio<wbr>n</code></span></summary>
<p>Run <strong>Delete a transactional template version.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.deletetemplateversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the original template</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the template version</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.deletetemplateversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "00000000-0000-4000-8000-000000000000",
    "version_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-templates-activatetemplateversion">
<summary><span>Activate a transactional template version. — <code>sendgrid.<wbr>templates.<wbr>activatetemplatevers<wbr>ion</code></span></summary>
<p>Run <strong>Activate a transactional template version.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.templates.activatetemplateversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.template_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the original template</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the template version</td>
<td><code>format: &quot;uuid&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.templates.activatetemplateversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "template_id": "00000000-0000-4000-8000-000000000000",
    "version_id": "00000000-0000-4000-8000-000000000000"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-listtrackingsetting">
<summary><span>Retrieve Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>listtrackingsetting</code></span></summary>
<p>Run <strong>Retrieve Tracking Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.listtrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.listtrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-listclicktrackingsetting">
<summary><span>Retrieve Click Track Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>listclicktrackingset<wbr>ting</code></span></summary>
<p>Run <strong>Retrieve Click Track Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.listclicktrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.listclicktrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-updateclicktrackingsetting">
<summary><span>Update Click Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>updateclicktrackings<wbr>etting</code></span></summary>
<p>Run <strong>Update Click Tracking Settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.updateclicktrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>The setting you want to use for click tracking.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.updateclicktrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-listgoogleanalyticstrackingsetting">
<summary><span>Retrieve Google Analytics Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>listgoogleanalyticst<wbr>rackingsetting</code></span></summary>
<p>Run <strong>Retrieve Google Analytics Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.listgoogleanalyticstrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.listgoogleanalyticstrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-updategoogleanalyticstrackingsetting">
<summary><span>Update Google Analytics Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>updategoogleanalytic<wbr>strackingsetting</code></span></summary>
<p>Run <strong>Update Google Analytics Settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.updategoogleanalyticstrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/GoogleAnalyticsSettings&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.updategoogleanalyticstrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-listopentrackingsetting">
<summary><span>Get Open Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>listopentrackingsett<wbr>ing</code></span></summary>
<p>Run <strong>Get Open Tracking Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.listopentrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.listopentrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-updateopentrackingsetting">
<summary><span>Update Open Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>updateopentrackingse<wbr>tting</code></span></summary>
<p>Run <strong>Update Open Tracking Settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.updateopentrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td>The new status that you want to set for open tracking.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.updateopentrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-listsubscriptiontrackingsetting">
<summary><span>Retrieve Subscription Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>listsubscriptiontrac<wbr>kingsetting</code></span></summary>
<p>Run <strong>Retrieve Subscription Tracking Settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.listsubscriptiontrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.listsubscriptiontrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-tracking_settings-updatesubscriptiontrackingsetting">
<summary><span>Update Subscription Tracking Settings — <code>sendgrid.<wbr>tracking_<wbr>settings.<wbr>updatesubscriptiontr<wbr>ackingsetting</code></span></summary>
<p>Run <strong>Update Subscription Tracking Settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.tracking_settings.updatesubscriptiontrackingsetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/SubscriptionTrackingSettings&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.tracking_settings.updatesubscriptiontrackingsetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-listaccount">
<summary><span>Get a user's account information. — <code>sendgrid.<wbr>user.<wbr>listaccount</code></span></summary>
<p>Run <strong>Get a user&#39;s account information.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.listaccount">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.listaccount">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-listcredit">
<summary><span>Retrieve your credit balance — <code>sendgrid.<wbr>user.<wbr>listcredit</code></span></summary>
<p>Run <strong>Retrieve your credit balance</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.listcredit">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.listcredit">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-listemail">
<summary><span>Retrieve your account email address — <code>sendgrid.<wbr>user.<wbr>listemail</code></span></summary>
<p>Run <strong>Retrieve your account email address</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.listemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.listemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-updateemail">
<summary><span>Update your account email address — <code>sendgrid.<wbr>user.<wbr>updateemail</code></span></summary>
<p>Run <strong>Update your account email address</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.updateemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.email</code></td>
<td>string</td>
<td>Optional</td>
<td>The new email address that you would like to use for your account.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.updateemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-updatepassword">
<summary><span>Update your password — <code>sendgrid.<wbr>user.<wbr>updatepassword</code></span></summary>
<p>Run <strong>Update your password</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.updatepassword">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.new_password</code></td>
<td>string</td>
<td>Required</td>
<td>The new password you would like to use for your account.</td>
<td></td>
</tr>
<tr>
<td><code>body.old_password</code></td>
<td>string</td>
<td>Required</td>
<td>The old password for your account.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.updatepassword">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-listprofile">
<summary><span>Get a user's profile — <code>sendgrid.<wbr>user.<wbr>listprofile</code></span></summary>
<p>Run <strong>Get a user&#39;s profile</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.listprofile">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.listprofile">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-updateprofile">
<summary><span>Update a user's profile — <code>sendgrid.<wbr>user.<wbr>updateprofile</code></span></summary>
<p>Run <strong>Update a user&#39;s profile</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.updateprofile">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/UserProfile&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.updateprofile">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-listusername">
<summary><span>Retrieve your username — <code>sendgrid.<wbr>user.<wbr>listusername</code></span></summary>
<p>Run <strong>Retrieve your username</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.listusername">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.listusername">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-user-updateusername">
<summary><span>Update your username — <code>sendgrid.<wbr>user.<wbr>updateusername</code></span></summary>
<p>Run <strong>Update your username</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.user.updateusername">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.username</code></td>
<td>string</td>
<td>Optional</td>
<td>The new username you would like to use for your account.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.user.updateusername">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-createverifiedsender">
<summary><span>Create Verified Sender Request — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>createverifiedsender</code></span></summary>
<p>Run <strong>Create Verified Sender Request</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.createverifiedsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/VerifiedSenderRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.createverifiedsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-listverifiedsender">
<summary><span>Get All Verified Senders — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>listverifiedsender</code></span></summary>
<p>Run <strong>Get All Verified Senders</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.listverifiedsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>number</td>
<td>Optional</td>
<td>Specifies the number of results to be returned by the API. This parameter can be used to limit the results returned or in combination with the <code>lastSeenID</code> parameter to iterate through paginated results.</td>
<td></td>
</tr>
<tr>
<td><code>query.lastSeenID</code></td>
<td>number</td>
<td>Optional</td>
<td>Returns senders with an ID number occurring after the passed in ID. In other words, the <code>lastSeenID</code> provides a starting point from which SendGrid will iterate to find Sender Identities associated with your account.</td>
<td></td>
</tr>
<tr>
<td><code>query.id</code></td>
<td>integer</td>
<td>Optional</td>
<td>Returns information about only the Sender Identity passed in the request.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.listverifiedsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-updateverifiedsender">
<summary><span>Edit Verified Sender — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>updateverifiedsender</code></span></summary>
<p>Run <strong>Edit Verified Sender</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.updateverifiedsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/VerifiedSenderRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.updateverifiedsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-deleteverifiedsender">
<summary><span>Delete Verified Sender — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>deleteverifiedsender</code></span></summary>
<p>Run <strong>Delete Verified Sender</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.deleteverifiedsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.deleteverifiedsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-listverifiedsenderdomain">
<summary><span>Domain Warn List — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>listverifiedsenderdo<wbr>main</code></span></summary>
<p>Run <strong>Domain Warn List</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.listverifiedsenderdomain">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.listverifiedsenderdomain">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-resendverifiedsender">
<summary><span>Resend Verified Sender Request — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>resendverifiedsender</code></span></summary>
<p>Run <strong>Resend Verified Sender Request</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.resendverifiedsender">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.resendverifiedsender">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-listverifiedsenderstepscompleted">
<summary><span>Completed Steps — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>listverifiedsenderst<wbr>epscompleted</code></span></summary>
<p>Run <strong>Completed Steps</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.listverifiedsenderstepscompleted">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.listverifiedsenderstepscompleted">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-verified_senders-verifysendertoken">
<summary><span>Verify Sender Request — <code>sendgrid.<wbr>verified_<wbr>senders.<wbr>verifysendertoken</code></span></summary>
<p>Run <strong>Verify Sender Request</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.verified_senders.verifysendertoken">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.token</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.verified_senders.verifysendertoken">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "token": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-createeventwebhook">
<summary><span>Create a new Event Webhook — <code>sendgrid.<wbr>webhooks.<wbr>createeventwebhook</code></span></summary>
<p>Run <strong>Create a new Event Webhook</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.createeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/EventWebhookRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.createeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-listeventwebhook">
<summary><span>Retrieve all of your Event Webhooks. — <code>sendgrid.<wbr>webhooks.<wbr>listeventwebhook</code></span></summary>
<p>Run <strong>Retrieve all of your Event Webhooks.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.listeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include</code></td>
<td>string</td>
<td>Optional</td>
<td>Use this to include optional fields in the response payload. When this is set to <code>include=account_status_change</code>, the <code>account_status_change</code> field will be part of the response payload and set to <code>false</code> by default. See <a href="https://docs.sendgrid.com/api-reference/webhooks/update-an-event-webhook">Update an event webhook</a> for enabling this webhook notification which lets you subscribe to account status change events related to compliance action taken by SendGrid.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.listeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-getsignedeventwebhook">
<summary><span>Get Signed Event Webhook's Public Key — <code>sendgrid.<wbr>webhooks.<wbr>getsignedeventwebhoo<wbr>k</code></span></summary>
<p>Run <strong>Get Signed Event Webhook&#39;s Public Key</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.getsignedeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Event Webhook you want to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.getsignedeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-updatesignedeventwebhook">
<summary><span>Toggle signature verification for a single Event Webhook by ID — <code>sendgrid.<wbr>webhooks.<wbr>updatesignedeventweb<wbr>hook</code></span></summary>
<p>Run <strong>Toggle signature verification for a single Event Webhook by ID</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.updatesignedeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Event Webhook you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.enabled</code></td>
<td>boolean</td>
<td>Required</td>
<td>Enable or disable the webhook by setting this property to <code>true</code> or <code>false</code>, respectively.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.updatesignedeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-testeventwebhook">
<summary><span>Test an Event Webhook's settings — <code>sendgrid.<wbr>webhooks.<wbr>testeventwebhook</code></span></summary>
<p>Run <strong>Test an Event Webhook&#39;s settings</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.testeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/EventWebhookTestRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.testeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-geteventwebhook">
<summary><span>Get the settings for a single Event Webhook. — <code>sendgrid.<wbr>webhooks.<wbr>geteventwebhook</code></span></summary>
<p>Run <strong>Get the settings for a single Event Webhook.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.geteventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Event Webhook you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include</code></td>
<td>string</td>
<td>Optional</td>
<td>Use this to include optional fields in the response payload. When this is set to <code>include=account_status_change</code>, the <code>account_status_change</code> field will be part of the response payload and set to <code>false</code> by default. See <a href="https://docs.sendgrid.com/api-reference/webhooks/update-an-event-webhook">Update an event webhook</a> for enabling this webhook notification which lets you subscribe to account status change events related to compliance action taken by SendGrid.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.geteventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-updateeventwebhook">
<summary><span>Update a single Event Webhook by ID. — <code>sendgrid.<wbr>webhooks.<wbr>updateeventwebhook</code></span></summary>
<p>Run <strong>Update a single Event Webhook by ID.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.updateeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Event Webhook you want to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include</code></td>
<td>string</td>
<td>Optional</td>
<td>Use this to include optional fields in the response payload. When this is set to <code>include=account_status_change</code>, the <code>account_status_change</code> field will be part of the response payload and set to <code>false</code> by default. See <a href="https://docs.sendgrid.com/api-reference/webhooks/update-an-event-webhook">Update an event webhook</a> for enabling this webhook notification which lets you subscribe to account status change events related to compliance action taken by SendGrid.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/EventWebhookRequest&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.updateeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-deleteeventwebhook">
<summary><span>Delete a single Event Webhook by ID. — <code>sendgrid.<wbr>webhooks.<wbr>deleteeventwebhook</code></span></summary>
<p>Run <strong>Delete a single Event Webhook by ID.</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.deleteeventwebhook">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the Event Webhook you want to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.deleteeventwebhook">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-listparsesetting">
<summary><span>Retrieve all parse settings — <code>sendgrid.<wbr>webhooks.<wbr>listparsesetting</code></span></summary>
<p>Run <strong>Retrieve all parse settings</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.listparsesetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.listparsesetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-createparsesetting">
<summary><span>Create a parse setting — <code>sendgrid.<wbr>webhooks.<wbr>createparsesetting</code></span></summary>
<p>Run <strong>Create a parse setting</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.createparsesetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ParseSetting&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.createparsesetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-getparsesetting">
<summary><span>Retrieve a specific parse setting — <code>sendgrid.<wbr>webhooks.<wbr>getparsesetting</code></span></summary>
<p>Run <strong>Retrieve a specific parse setting</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.getparsesetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.hostname</code></td>
<td>string</td>
<td>Required</td>
<td>The hostname associated with the inbound parse setting that you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.getparsesetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "hostname": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-updateparsesetting">
<summary><span>Update a parse setting — <code>sendgrid.<wbr>webhooks.<wbr>updateparsesetting</code></span></summary>
<p>Run <strong>Update a parse setting</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.updateparsesetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.hostname</code></td>
<td>string</td>
<td>Required</td>
<td>The hostname associated with the inbound parse setting that you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ParseSetting&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.updateparsesetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "hostname": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-deleteparsesetting">
<summary><span>Delete a parse setting — <code>sendgrid.<wbr>webhooks.<wbr>deleteparsesetting</code></span></summary>
<p>Run <strong>Delete a parse setting</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.deleteparsesetting">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.hostname</code></td>
<td>string</td>
<td>Required</td>
<td>The hostname associated with the inbound parse setting that you would like to retrieve.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.deleteparsesetting">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "hostname": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-listparsestatic">
<summary><span>Retrieves Inbound Parse Webhook statistics. — <code>sendgrid.<wbr>webhooks.<wbr>listparsestatic</code></span></summary>
<p>Run <strong>Retrieves Inbound Parse Webhook statistics.</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.listparsestatic">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>string</td>
<td>Optional</td>
<td>The number of statistics to return on each page.</td>
<td></td>
</tr>
<tr>
<td><code>query.offset</code></td>
<td>string</td>
<td>Optional</td>
<td>The number of statistics to skip.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td>How you would like the statistics to by grouped.</td>
<td></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/AggregatedBy&quot;</code></td>
</tr>
<tr>
<td><code>query.aggregated_by</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>The starting date of the statistics you want to retrieve. Must be in the format YYYY-MM-DD</td>
<td></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date of the statistics you want to retrieve. Must be in the format YYYY-MM-DD</td>
<td><code>default: &quot;The day the request is made.&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.listparsestatic">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "start_date": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-createsecuritypolicy">
<summary><span>Create a new webhook security policy — <code>sendgrid.<wbr>webhooks.<wbr>createsecuritypolicy</code></span></summary>
<p>Run <strong>Create a new webhook security policy</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.createsecuritypolicy">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>User-defined policy name</td>
<td></td>
</tr>
<tr>
<td><code>body.oauth</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.client_id</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.client_secret</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.token_url</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.scopes</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.signature</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.signature.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.createsecuritypolicy">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-listallsecuritypolicies">
<summary><span>Retrieve all webhook security policies for your account — <code>sendgrid.<wbr>webhooks.<wbr>listallsecuritypolic<wbr>ies</code></span></summary>
<p>Run <strong>Retrieve all webhook security policies for your account</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.listallsecuritypolicies">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.listallsecuritypolicies">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-updatesecuritypolicy">
<summary><span>Update an existing webhook security policy — <code>sendgrid.<wbr>webhooks.<wbr>updatesecuritypolicy</code></span></summary>
<p>Run <strong>Update an existing webhook security policy</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.updatesecuritypolicy">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.name</code></td>
<td>string</td>
<td>Optional</td>
<td>User-defined policy name</td>
<td></td>
</tr>
<tr>
<td><code>body.oauth</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.client_id</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.client_secret</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.token_url</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.scopes</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.oauth.scopes[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.signature</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.signature.enabled</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.updatesecuritypolicy">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-getsecuritypolicy">
<summary><span>Retrieve a specific webhook security policy — <code>sendgrid.<wbr>webhooks.<wbr>getsecuritypolicy</code></span></summary>
<p>Run <strong>Retrieve a specific webhook security policy</strong> with Twilio SendGrid. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.getsecuritypolicy">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.getsecuritypolicy">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sendgrid-webhooks-deletesecuritypolicy">
<summary><span>Delete a specific webhook security policy — <code>sendgrid.<wbr>webhooks.<wbr>deletesecuritypolicy</code></span></summary>
<p>Run <strong>Delete a specific webhook security policy</strong> with Twilio SendGrid. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sendgrid?command=sendgrid.webhooks.deletesecuritypolicy">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.force</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.on-behalf-of</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>on-behalf-of</code> header allows you to make API calls from a parent account on behalf of the parent&#39;s Subusers or customer accounts. You will use the parent account&#39;s API key when using this header. When making a call on behalf of a customer account, the property value should be &quot;account-id&quot; followed by the customer account&#39;s ID (e.g., <code>on-behalf-of: account-id &amp;lt;account-id&amp;gt;</code>). When making a call on behalf of a Subuser, the property value should be the Subuser&#39;s username (e.g., <code>on-behalf-of: &amp;lt;subuser-username&amp;gt;</code>). See <a href="https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of"><strong>On Behalf Of</strong></a> for more information.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sendgrid/commands/sendgrid.webhooks.deletesecuritypolicy">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://www.twilio.com/docs/sendgrid/api-reference">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/sendgrid/index.mdx
