---
title: "Amazon SES"
description: "Sends transactional email through Amazon SES v2. Requires a verified sending identity and IAM credentials with the ses:SendEmail permission."
---

> 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.

# Amazon SES

<p>Sends transactional email through Amazon SES v2. Requires a verified sending identity and IAM credentials with the ses:SendEmail permission.</p>

<details data-command-index><summary>What you can do (1)</summary>
<h2>What you can do</h2>
<p>Available commands: 1 (0 read, 1 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/amazon-ses#command-amazon-ses-send">Send email</a> — <code>amazon-ses.send</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/amazon-ses">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 Amazon SES, then enter the issued values in the connection form below.</p>
<ol>
<li>In your AWS account, configure an SES sending identity and obtain IAM access credentials limited to the required SES operations. Enter the access key ID, secret access key and SES region; sandbox accounts also require verified recipients.</li>
</ol>
<p><a href="https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_SendEmail.html">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>Access key ID</td>
<td>Required</td>
</tr>
<tr>
<td>Secret access key</td>
<td>Required</td>
</tr>
<tr>
<td>Region</td>
<td>Required</td>
</tr>
<tr>
<td>Configuration set</td>
<td>Optional</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": {
    "from": {
      "address": "notifications@planner.li",
      "name": "Planner.li"
    },
    "to": [
      {
        "address": "person@example.com",
        "name": "Example user"
      }
    ],
    "replyTo": [
      {
        "address": "support@planner.li"
      }
    ],
    "subject": "Your trip is confirmed",
    "text": "Hello — your trip is confirmed. Sign in at https://planner.li to see the full itinerary.",
    "html": "&lt;p&gt;Hello — your trip is confirmed.&lt;/p&gt;&lt;p&gt;&lt;a href=\"https://planner.li\"&gt;See the full itinerary&lt;/a&gt;&lt;/p&gt;",
    "headers": {
      "X-Entity-Ref-Id": "trip-2026-09-09-0001"
    },
    "tags": {
      "campaign": "trip-confirmation"
    }
  }
}'
</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-amazon-ses-send">
<summary><span>Send email — <code>amazon-<wbr>ses.<wbr>send</code></span></summary>
<p>Run <strong>Send email</strong> with Amazon SES. 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/amazon-ses?command=amazon-ses.send">Connect and use</a></p>

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

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

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>from</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>from.address</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 320; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>from.name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 200</code></td>
</tr>
<tr>
<td><code>to</code></td>
<td>array</td>
<td>Required</td>
<td></td>
<td><code>minItems: 1; maxItems: 50</code></td>
</tr>
<tr>
<td><code>to[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>to[].address</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 320; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>to[].name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 200</code></td>
</tr>
<tr>
<td><code>cc</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 50</code></td>
</tr>
<tr>
<td><code>cc[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>cc[].address</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 320; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>cc[].name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 200</code></td>
</tr>
<tr>
<td><code>bcc</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 50</code></td>
</tr>
<tr>
<td><code>bcc[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>bcc[].address</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 320; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>bcc[].name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 200</code></td>
</tr>
<tr>
<td><code>replyTo</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 5</code></td>
</tr>
<tr>
<td><code>replyTo[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>replyTo[].address</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 320; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>replyTo[].name</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>maxLength: 200</code></td>
</tr>
<tr>
<td><code>subject</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 998</code></td>
</tr>
<tr>
<td><code>text</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 200000</code></td>
</tr>
<tr>
<td><code>html</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 1000000</code></td>
</tr>
<tr>
<td><code>attachments</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 5</code></td>
</tr>
<tr>
<td><code>attachments[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>attachments[].filename</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 255; pattern: &quot;^[A-Za-z0-9][A-Za-z0-9._ -]{0,253}[A-Za-z0-9]$&quot;</code></td>
</tr>
<tr>
<td><code>attachments[].contentType</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>maxLength: 78</code></td>
</tr>
<tr>
<td><code>attachments[].contentBase64</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 4; maxLength: 131072; pattern: &quot;^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$&quot;</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>maxProperties: 20; additionalProperties: {&quot;type&quot;:&quot;string&quot;,&quot;maxLength&quot;:1000}</code></td>
</tr>
<tr>
<td><code>tags</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>maxProperties: 10; additionalProperties: {&quot;type&quot;:&quot;string&quot;,&quot;maxLength&quot;:256}</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/amazon-ses/commands/amazon-ses.send">Full JSON Schema</a></p>

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

<pre><code class="language-json">{
  "from": {
    "address": "notifications@planner.li",
    "name": "Planner.li"
  },
  "to": [
    {
      "address": "person@example.com",
      "name": "Example user"
    }
  ],
  "replyTo": [
    {
      "address": "support@planner.li"
    }
  ],
  "subject": "Your trip is confirmed",
  "text": "Hello — your trip is confirmed. Sign in at https://planner.li to see the full itinerary.",
  "html": "&lt;p&gt;Hello — your trip is confirmed.&lt;/p&gt;&lt;p&gt;&lt;a href=\"https://planner.li\"&gt;See the full itinerary&lt;/a&gt;&lt;/p&gt;",
  "headers": {
    "X-Entity-Ref-Id": "trip-2026-09-09-0001"
  },
  "tags": {
    "campaign": "trip-confirmation"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 20 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://docs.aws.amazon.com/ses/latest/APIReference-V2/API_SendEmail.html">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/amazon-ses/index.mdx