> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend: Inboxes Create

> Create an inbox. Resend Inboxes Create reference includes SDK V2 and CLI requests, input constraints, response fields, and Deepline cost.

Create an inbox.

> [!NOTE]
>
> Tool ID: `resend_inboxes_create`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'resend_inboxes_create',
  {
    "email_address": "jane.doe@example.com"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run resend_inboxes_create --input '{
  "email_address": "jane.doe@example.com"
}'
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "object": "example",
    "id": "123e4567-e89b-42d3-a456-426614174000"
  }
}
```

Use `deepline describe resend_inboxes_create --json` for the latest machine-readable contract.

## Input reference

Creates an inbox that sends and receives email at an address on one of your domains. The domain must belong to the team. Without `forwarding`, the domain must have receiving enabled, with DKIM and SPF verified and the inbound MX record verified or pending. With `forwarding` set to `true`, the domain only needs DKIM and SPF verified for sending, and Resend generates a `receiving_address` on the team inbound domain, and a team without an inbound domain gets a 422. A domain that does not meet these rules returns a 422 validation\_error. An address or receiving address that is already in use returns a 409. A team that has reached the inbox limit of its plan returns a 403 validation\_error. A blocked account returns a 451.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.email_address` | `string` | Yes | — | The inbox email address on one of your domains. The API trims and lowercases it. The part before the `@` is at most 64 characters and contains only letters, numbers, and `. _ % -`. A `+` returns a 422. It cannot start or end with a dot or contain two dots in a row. |
| `payload.name` | `string` | No | — | Internal name for the inbox. Recipients do not see it. Max 64 characters. Defaults to `email_address`. Maximum length: 64. |
| `payload.from_name` | `string` | No | — | The name recipients see when mail is sent from this inbox. A plain name, not a `Name ` address. Max 78 characters. It cannot contain a colon, ` `, line breaks, or other control characters. An email address inside the name must be on a domain the team has verified for sending. An empty string leaves it unset. Maximum length: 78. |
| `payload.forwarding` | `boolean` | No | `false` | When `true`, Resend provisions a receiving address so you can receive mail without adding an MX record. The address is returned in `receiving_address`. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Creates an inbox that sends and receives email at an address on one of your domains. The domain must belong to the team. Without `forwarding`, the domain must have receiving enabled, with DKIM and SPF verified and the inbound MX record verified or pending. With `forwarding` set to `true`, the domain only needs DKIM and SPF verified for sending, and Resend generates a `receiving_address` on the team inbound domain, and a team without an inbound domain gets a 422. A domain that does not meet these rules returns a 422 validation_error. An address or receiving address that is already in use returns a 409. A team that has reached the inbox limit of its plan returns a 403 validation_error. A blocked account returns a 451.",
    "properties": {
      "email_address": {
        "type": "string",
        "description": "The inbox email address on one of your domains. The API trims and lowercases it. The part before the `@` is at most 64 characters and contains only letters, numbers, and `. _ % -`. A `+` returns a 422. It cannot start or end with a dot or contain two dots in a row."
      },
      "name": {
        "type": "string",
        "description": "Internal name for the inbox. Recipients do not see it. Max 64 characters. Defaults to `email_address`.",
        "maxLength": 64
      },
      "from_name": {
        "type": "string",
        "description": "The name recipients see when mail is sent from this inbox. A plain name, not a `Name ` address. Max 78 characters. It cannot contain a colon, ` `, line breaks, or other control characters. An email address inside the name must be on a domain the team has verified for sending. An empty string leaves it unset.",
        "maxLength": 78
      },
      "forwarding": {
        "type": "boolean",
        "description": "When `true`, Resend provisions a receiving address so you can receive mail without adding an MX record. The address is returned in `receiving_address`.",
        "default": false
      }
    },
    "required": [
      "email_address"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.object` | `string` | Yes | — | Type of the response object. |
| `result.data.id` | `string` | Yes | — | The ID of the inbox. Format: `uuid`. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "object": {
            "type": "string",
            "description": "Type of the response object."
          },
          "id": {
            "type": "string",
            "description": "The ID of the inbox.",
            "format": "uuid"
          }
        },
        "required": [
          "object",
          "id"
        ],
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Connect integrations](https://deepline.com/docs/integrations.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.