Latest Content

How to Submit an OAuth Application for Review

Updated on 21 July, 2026

Submit an OAuth application on Vultr for administrative review, move it to Pending Review, and make it available to all customers once it is approved.

Submitting an OAuth application sends it to Vultr for review. An approved application reaches Active status and becomes available to any Vultr customer, and the allowlist requirement no longer applies. Submission moves the application from Draft to PendingReview and locks it against edits. If Vultr rejects the application, it moves to Rejected status. Review the rejection feedback, edit the application to address it, which returns it to Draft, then submit it again. An approved application stays locked in Active status and cannot be edited or deleted.

Follow this guide to submit an OAuth application for review using the Vultr Console and the Vultr API.

Note
Submitting requires the organization's root user. A non-root user receives an HTTP 403 Forbidden response. Before submitting, the application must have at least one https callback URL and at least one attached scope, and your account must be funded. A funded account is one that has completed at least one payment, deposit, paid invoice, or gift-code redemption.
  • Vultr Console
  • Vultr API

  1. Log in to the Vultr Console.

  2. Click the organization name in the top navigation bar.

  3. Click Manage Organization.

  4. Click OAuth Applications.

  5. Submit the application:

    • When you create the application, click Send for Review in the Application Created dialog instead of Save as Draft.
    • To submit an application you saved as a draft, open it from the OAuth Applications list and click Send for Review.

    The application status changes to Pending Review. If Vultr rejects it, the management page shows the rejection reason. Review it, make the necessary changes, which returns the application to Draft status, then submit it again.

  1. Send a POST request to the Submit OAuth Client endpoint to submit the application for review. Replace {client-id} with your application id.

    console 
    $ curl "https://api.vultr.com/v2/oauth/clients/{client-id}/submit" \
    -X POST \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

    A successful request returns an HTTP 200 OK response with review_status set to PendingReview and date_submitted populated. An application that is not in Draft or Rejected status returns an HTTP 409 Conflict response.

  2. Send a GET request to the Read OAuth Client endpoint to retrieve the application status. Replace {client-id} with your application id.

    console 
    $ curl "https://api.vultr.com/v2/oauth/clients/{client-id}" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

    Verify that the review_status shows PendingReview. If Vultr rejects the application, the rejection_reason and rejection_comment fields on the application object explain why. Review them, update the application to address the feedback, which returns it to Draft status, then submit it again.

Comments