Testing a Subscription Request with dryRun

Testing a Subscription Request

Setting dryRun to TRUE for the Create Asset endpoint causes the platform to run the data validations without creating an asset or storing data in the database and/or blockchain.

The dryRun option is useful for:

• testing sample payloads during coding of an integration

• providing advisors with a button that confirms the payload is complete and correct before proceeding with other steps in the subscription process, such as uploading documents

Because the only difference between running Create Asset with dryRun set to TRUE vs FALSE is the step of persisting the resulting objects to the database and blockchain, there is no need to execute a dryRun call before every Create Asset call.