Skip to main content

# TransactionDetails

    type TransactionDetails = {
      request: {
         options?: Record<string, string | boolean | number>;
         resources: TransactionResource[];
         type: string;
      };
    };

details about the transaction

## Properties​

### request​

    request: {
      options?: Record<string, string | boolean | number>;
      resources: TransactionResource[];
      type: string;
    };

details about the transaction that is created / updated

Name | Type | Description
--- | --- | ---
`options?` | `Record`<`string`, `string` | `boolean` | `number`> | The specific set of selectable options that apply to the specific type of transaction request, as modeled by your application
`resources` | `TransactionResource`[] | The collection of file attachments - referred to as resource objects in the EPC API - to be attached to the transaction request. The id, name, and mimeType attribute needed for each resource object in the collection can be created in one of two ways: Your application utilized the transaction.createResource method to build a custom file upload experience, and the user invoked this functionality and uploaded a file from their local drive. Your application utilized the application.performAction("getAvailableResources") method to launch the host application's file explorer, and the user invoked this functionality and attached a file[s] from the host application. Once the resource objects are collected from these methods, be sure to echo them back to the EPC platform when creating a transaction!
`type` | `string` | The type of transaction request being initiated for the subject product. This must be one of the supported values for the request type that your application is configured to support - based on which its data entitlements are scoped.