# Configure Your Vault for the Intake Inbox Item Vault API

Vault integrates with Vault API to allow organizations to exchange _Inbox Items_ through the Intake Inbox Item Vault API endpoint.

## Receive Inbox Items from Vault API

Vault supports _Inbox Item_ intake by passing a source E2B file through the Vault API using the Intake Inbox Item endpoint. Before your Vault can receive _Inbox Items_ from this Vault API endpoint, you must set up a _Connection_ type _Transmission Profile_ and ensure the user initiating the Vault API is set up correctly.

<a href="/en/gr/01286/">Receive an E2B Transmission</a> provides more information about how Vault processes inbound E2B transmissions.

## Set Up a Connection Transmission Profile

You must configure a _Connection_ type _Transmission Profile_ to use the Intake Inbox Item Vault API.

<a href="/en/gr/01202/">Manage Transmission Profiles</a>  provides instructions on setting up _Transmission Profiles_.

When setting up the _Connection_ type _Transmission Profile_, see the following guidance on setting the fields related to the origin and destination:

* **Origin**: Select the organization set up as _Vault Customer_ (`vault_customer__v`) for your Vault.
* **Origin ID**: Enter the identifier for the organization that will receive E2B files from the Vault API. This field is required to match Vault API calls with the correct _Transmission Profile_.
* **Destination**: Select the trading partner organization that will send the E2B files.
* **Destination ID**: Enter the identifier for the organization that will send the E2B files. This field is required to match Vault API calls with the correct _Transmission Profile_.

## Vault API User Setup Requirements

The user initiating the Vault API must meet the following requirements in the receiving Vault:

* The _User_ record must link to the _Organization_ receiving the transmission in the _Organization_ field. Edit User records in **Admin > Users & Groups**.
* The user must have permissions to create _Transmission_ (`transmission__v`) objects and _Case > Source > Adverse Event Report_ (`case__v` > `source__v` > `adverse_event_report__v`) documents.

## System Configuration Considerations

Consider the following when receiving _Cases_ through the Vault API:

* VQL criteria may cause the job to fail. Do not configure VQL criteria for _Organizations_, _Users_, or _Transmission Profiles_ in the following records:
  * The _Transmission_ (`transmission__v`) and _Inbox Item_ (`inbox_item__v`) objects
  * The _Case > Source > Adverse Event Report_ (`case__v` > `source__v` > `adverse_event_report__v`) document type
* All non-standard mandatory fields must have a default value for the following records:
  * The _Transmission_ (`transmission__v`) and _Inbox Item_ (`inbox_item__v`) objects
  * The _Case > Source > Adverse Event Report_ (`case__v` > `source__v` > `adverse_event_report__v`) document type

## Use the Intake Inbox Item Vault API

Once you've set up the _Transmission Profile_ and user account, the Vault Developer Portal provides more information about using the <a class="external-link " href="https://developer.veevavault.com/api/26.1#intake-inbox-item" target="_blank" rel="noopener">Intake Inbox Item<i class="fa fa-external-link" aria-hidden="true"></i></a> Vault API endpoint.