**Source URL:** https://general.veevavault.dev/vault-sdk/deploying-code/deploy-vpk.md # Deploy the VPK After importing your VPK, you need to deploy it. This is the final step which makes your Vault extension run for all users. The following instructions deploy the VPK using Vault API, but you can also [deploy through the Vault UI](https://platform.veevavault.help/en/gr/36919). We recommend using the UI, which has a multi-step wizard that ensures validation. Deploy your package with the [Deploy Package endpoint](/vault-api/api-reference/26.1/configuration-migration/deploy-package). You can find the `package_id` URI Path Parameter in the API response from your import request. If you lost this ID, you can also find it in **Admin > Deployment > Inbound Packages**. When you run the deploy endpoint, Vault first validates the VPK. If you have any validation errors, such as using non-allowlisted classes, deployment will fail. To avoid this, we recommend [validating](/vault-api/api-reference/26.1/configuration-migration/validate-package) your package frequently throughout the development process. After successful deployment, you can view deployed extensions in the Admin UI, located in **Admin** > **Configuration** > **VAULT JAVA SDK**. Learn more about the [Admin UI in Vault Help](https://platform.veevavault.help/en/gr/45776). ### Deployment Errors {#deployment-errors} If the deployment encounters any errors, Vault stops the deployment but does not roll back any changes it already made. We recommend downloading and checking the log file for details. Learn more about [deployment errors in Vault Help](https://platform.veevavault.help/en/gr/36919). --- **Previous:** [Import the VPK to Vault](/vault-sdk/deploying-code/import-vpk) **Next:** [Managing Deployed Code](/vault-sdk/deploying-code/managing-deployed-code)