Skip to main content

Connecting cloud providers (credentials)

CloudCO needs your provider API credentials to:

  • Pull live inventory into Sniper Hub
  • Run connection checks before you enable rules
  • Place orders when you turn on Auto-Buy (paid plans) or when you confirm a manual snipe

All of this is configured in the dashboard:

https://cloudco.me/dashboard/settings/providers

Log in, open Settings → Providers, then complete each block for the providers you use. You do not have to fill in every provider—only the ones where you want CloudCO to act on your behalf.

What you see on the Providers page​

Each provider has its own card with:

ElementMeaning
Status (dot + word)Whether the last verification succeeded. Use the refresh icon to test saved credentials without saving again.
Save & VerifyStores credentials (encrypted) and asks the backend to confirm they work with the provider API.
Encrypted storage bannerCredentials are encrypted at rest; CloudCO uses them only for procurement-related API calls.

If you change a password, token, or key later, update the fields and click Save & Verify again. The Sniper Hub also has a per-provider Verify / Sync control once you select that provider in the dropdown.

Hetzner Online (Robot Webservice)​

CloudCO talks to Hetzner through the Robot Webservice login—not your normal Robot web UI password unless you intentionally reuse it (not recommended).

Where credentials live in CloudCO​

Dashboard fieldWhat it is
Robot Webservice UsernameWebservice user (often your client_login like K1234567).
Robot Webservice PasswordThe Webservice password you set in Robot (separate from the main portal password).

How to obtain them​

  1. Sign in to Hetzner Robot.
  2. Open Preferences → Webservice (direct link also shown from the Providers card).
  3. Under Webservice, enable access if it is disabled.
  4. Open the Ordering tab and ensure Webservice ordering is allowed so CloudCO can place auction orders when Auto-Buy or manual snipe runs.
  5. Return to Webservice, note the username, and set a strong dedicated password for API use.
  6. Copy username + password into CloudCO Settings → Providers → Hetzner and click Save & Verify.

If verification fails, check Robot-side permissions, account limits, and that you did not paste your normal web-login password by mistake.

OVHcloud Europe (ovh-eu)​

Used for EU subsidiary APIs (Eco / Kimsufi / So you Start–style bare-metal catalog). Credentials are not interchangeable with Canada—use the OVHcloud Europe block only.

Where credentials live in CloudCO​

Dashboard fieldWhat it is
Application Keyapplication_key from the OVH API application.
Application Secretapplication_secret from the same application.
Consumer KeyUser-approved token (consumer_key) that authorizes API access for your account.

How to obtain them​

  1. Create an API application on the EU portal: Create an EU API application.
    Choose a name (e.g. CloudCO) and note the Application Key and Application Secret.
  2. Generate a Consumer Key using OVH’s standard API login flow (credential request). You must grant rights sufficient for CloudCO to read availability/pricing and place orders for dedicated servers (cart / order endpoints).
    Official overview: First steps with the OVHcloud API (follow the guide for your contract; paths may vary slightly by subsidiary).
  3. Paste into CloudCO Settings → Providers → OVHcloud Europe:
    • Application Key → Application Key
    • Application Secret → Application Secret
    • Consumer Key → Consumer Key
  4. Click Save & Verify.

Older installs may have stored Application Secret and Consumer Key together as secret:consumer_key in the secret field only. That still works if Consumer Key is left empty, but three separate fields are clearer and supported—prefer those.

OVHcloud North America (ovh-ca)​

Same three-field layout as Europe, but you must register the application on the Canadian API host so tokens match your NA account.

How to obtain them​

  1. Create the application here: Create a Canadian API application.
  2. Follow the same Consumer Key / access-rules process as for EU, using CA endpoints and documentation for your account currency (CAD/USD).
  3. Enter Application Key, Application Secret, and Consumer Key in Settings → Providers → OVHcloud North America, then Save & Verify.

DigitalOcean​

CloudCO uses a Personal Access Token as the secret. The first field is only a label for your own reference (stored alongside the token in CloudCO).

Where credentials live in CloudCO​

Dashboard fieldWhat it is
Token Description (Reference)Human-readable label (e.g. CloudCO-Sniper). Not sent as the API credential.
Personal Access TokenThe actual token string generated in DigitalOcean.

How to obtain them​

  1. Open DigitalOcean API tokens (Account → API → Generate New Token).
  2. Name the token (match what you put in Token Description if you like).
  3. Choose scopes that allow CloudCO to read account/resources and create Droplets when Auto-Buy fires. A scoped token is fine if it includes the permissions required for Droplet create and region/size discovery; full access is simpler but broader than necessary.
  4. Copy the token once (DigitalOcean shows it only at creation) into Personal Access Token, set the description field, then Save & Verify.

Vultr​

CloudCO stores your Vultr API key in the secret field. The API Description field is for your notes only.

Where credentials live in CloudCO​

Dashboard fieldWhat it is
API DescriptionLabel for you (e.g. CloudCO-Vultr).
API KeyThe key from the Vultr control panel.

How to obtain them​

  1. Sign in to Vultr and open API settings.
  2. Enable the API if needed, generate or copy the API Key.
  3. Optionally use Vultr’s access controls (IP allowlist, etc.) per your security policy—remember that CloudCO’s servers must be allowed to call the API if you restrict by IP.
  4. Paste the key into API Key, fill API Description, then Save & Verify.

Verification & troubleshooting​

  • After saving, status should move toward VERIFIED. If it shows ERROR, open the message: wrong key, expired token, missing Consumer Key, or insufficient API permissions are the usual causes.
  • OVH: Wrong subsidiary (EU keys on CA card or vice versa) always fails—create the app on the matching eu.api.ovh.com vs ca.api.ovh.com host.
  • Hetzner: “Forbidden” / ordering errors often mean Webservice ordering is disabled or the API user cannot order.
  • DigitalOcean / Vultr: Regenerate the token/key if rotated or leaked; update CloudCO and verify again.

Security summary​

  • Credentials are encrypted when stored; CloudCO does not display full secrets again after save (only masked hints where applicable).
  • You bill directly with the provider; CloudCO never holds your server budget.