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.

Receive an E2B Transmission 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.

Manage Transmission Profiles 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) object
    • 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) object
    • 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 Intake Inbox Item Vault API endpoint.