# Import a Gmail account's aliases and signatures

Reads the send-as list Gmail holds for one of the caller's OWN connected Google accounts and makes the workspace agree with it: every alias Gmail has accepted becomes an inbox the caller owns, an alias Gmail no longer lists is removed, and the signature Gmail keeps for the account or an alias is copied to that address — never over a signature somebody typed here. Answers the aliases as they now stand, how many were added and removed, how many signatures were copied, and each address it left out with the reason (not verified in Gmail, already connected as its own account, a typed signature kept). Safe to run again. Put people on an alias afterwards with `put_comms_inboxes_medium_identifier_members_accountId`. An Outlook account is refused, and Gmail's own refusal comes back as a 502 in Gmail's words.

Access class: `workspace`.

## Endpoint

`POST /v1/comms/connections/{id}/aliases/import`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| id | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "added": 1.5,
    "aliases": [
      {
        "address": "string",
        "display_name": "string",
        "id": "",
        "imported_at": "string"
      }
    ],
    "removed": 1.5,
    "signatures": 1.5,
    "skipped": [
      {
        "address": "string",
        "reason": "string"
      }
    ]
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
