Delete a Draft or Rejected OAuth application on Vultr, tear down its attached scope clones, and confirm the removal through the Vultr Console or the Vultr API.
Deleting an OAuth application removes it from your organization and tears down the scope copies it created. You can delete an application only while it is in Draft or Rejected status. A live application, meaning one that is PendingReview or Active, cannot be deleted, which prevents you from accidentally orphaning customers who have already authorized an approved application.
Follow this guide to delete an OAuth application using the Vultr Console and the Vultr API.
403 Forbidden response. You can delete an application only while it is in Draft or Rejected status. A PendingReview or Active application returns an HTTP 409 Conflict response. Deleting an application does not revoke the access that customers have already granted, so revoke outstanding authorizations first if you need to cut off access.
Log in to the Vultr Console.
Click the organization name in the top navigation bar.
Click Manage Organization.
Click OAuth Applications.
Click the Delete icon next to the application in the list, or open the application's management page and click Destroy.
Confirm the deletion when prompted.
The application is removed from the OAuth Applications list.
Send a DELETE request to the Delete OAuth Client endpoint to remove the application. Replace {client-id} with your application id.
$ curl "https://api.vultr.com/v2/oauth/clients/{client-id}" \
-X DELETE \
-H "Authorization: Bearer ${VULTR_API_KEY}"
A successful deletion returns an HTTP 204 No Content response with no response body.
Send a GET request to the Read OAuth Client endpoint to confirm the deletion. Replace {client-id} with your application id.
$ curl "https://api.vultr.com/v2/oauth/clients/{client-id}" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"
Verify that the request returns an HTTP 404 Not Found response, which confirms the application is no longer accessible.