Make a Vultr Marketplace application public using the Vultr Console or Vultr API to list it on the Marketplace and allow all Vultr customers to deploy it.
Making your app public is the final publishing step. While an app is private, it is only visible to your account. A public app is visible to all Vultr customers. Preview your landing page and test your app before you make it public. The app needs at least one published build, icons, a description, a Readme, instructions, and a support email or URL before Vultr accepts it for review.
This guide explains how to make an app public using the Vultr Console or the Vultr API.
Click Marketplace in the Vultr Console's left-hand menu.
Click the application name to open the Edit App screen.
Click the Settings tab.
Click the Make Public button, then click Ok on the Change Visibility confirmation dialog. Vultr submits your app for review, and displays a review-pending status while the review is in progress.
If a required field is missing, the Settings tab displays an error naming the missing field.
Our team tests your application and either approves it or requests changes. Vultr sends an email notification when the app is approved.
Send a PATCH request to the Update Marketplace App Visibility endpoint with public set to true. Replace {app-id} with the app's ID.
$ curl "https://api.vultr.com/v2/marketplace/apps/{app-id}/visibility" \
-X PATCH \
-H "Authorization: Bearer ${VULTR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"public": true
}'
A successful response returns the app object with public still set to false. The request only submits the app for review, and public does not switch to true until Vultr approves it. A 409 Conflict response means the app is already public. A 422 response means one of the required fields above is still missing, for example "App must have 1 published image to go public" if no build is Live. While the app is under review, requests to set public back to false are rejected with a 422 and "App is already being reviewed.".