Skip to main content
The raw REST API is intended for advanced users only. These endpoints offer maximum flexibility but require you to manage all aspects of integration yourself. Most users will have a significantly better experience using the CLI or the SDK, which handle these details for you. If you are not sure whether you need direct API access, you almost certainly don’t, start with the CLI or SDK instead.
The Vast.ai REST API gives you programmatic control over GPU instances, useful for automation, CI/CD pipelines, or building your own tooling on top of Vast. This guide walks through the complete instance lifecycle: authenticate, search for a GPU, rent it, wait for it to boot, connect to it, and clean up. By the end you’ll understand the core API calls needed to manage instances without touching the web console.

​
Prerequisites

  • A Vast.ai account with credit (~$0.01-0.05, depending on test instance run time)
  • curl installed

​
1. Get Your API Key

Generate an API key from the Keys page by clicking +New. Copy the key, you’ll need it for your API calls, and you’ll only see it once. Export it as an environment variable:

​
2. Verify Authentication

Confirm your key works by listing your current instances. If you have none, this returns an empty list.
If you get a 401 or 403, double-check your API key. If you already have instances, you’ll see them listed here.

​
3. Search for GPUs

Find available machines using the bundles endpoint. This query returns the top 5 on-demand RTX 4090s sorted by deep learning performance benchmarked per dollar:
Each parameter in the query above controls a different filter: The response contains an offers array. Note the id of the offer you want, you’ll use it in the next step. If no offers are returned, try relaxing your filters (e.g. a different GPU model or removing direct_port_count).
See the Search Offers reference for the full list of filter parameters and operators.

​
4. Create an Instance

Rent the machine by sending a PUT request with your Docker image and disk size. Replace OFFER_ID with the id from step 3. disk is in GB and specifies the size of the disk on your new instance.
Save the new_contract value, this is your instance ID. The instance_api_key is a restricted key injected into the container as CONTAINER_API_KEY, it can only start, stop, or destroy that specific instance.

​
5. Wait Until Ready

The instance needs time to pull the Docker image and boot. Poll the status endpoint until actual_status is "running". Replace INSTANCE_ID with the new_contract value from step 4.
Example response:
The actual_status field progresses through these states: Poll every 10 seconds. Boot time is typically 1-5 minutes depending on the Docker image size. You can also use the onstart script to send a callback when the instance is ready, instead of polling.
Always handle non-happy-path statuses in your poll loop. If actual_status becomes "exited" (container crashed), "unknown" (no heartbeat from host), or "offline" (host disconnected), it will never reach "running". Without a timeout or error check, your script will loop forever while the instance continues accruing disk charges. Destroy the instance and retry with a different offer if you see these states.
Once actual_status is "running", you’re ready to connect.

​
6. Connect via SSH

Use the ssh_host and ssh_port from the status response to connect directly to your new instance:

​
7. Clean Up

When you’re done, destroy the instance to stop all billing. Alternatively, to pause an instance temporarily instead of destroying it, you can stop it. Stopping halts compute billing but disk storage charges continue. Destroy (removes everything):
Stop (pauses compute, disk charges continue):
Both return {"success": true}.

​
Next Steps

You’ve now completed the full instance lifecycle through the API: authentication, search, creation, polling, and teardown. From here:
  • Full endpoint reference, Every REST endpoint is documented in the API reference, organized under the Reference tab.
  • Authentication & permissions, Create scoped API keys for CI/CD or shared tooling. See API authentication and permissions.
  • SSH setup, See the SSH guide for key configuration and advanced connection options.
  • Use templates, Avoid repeating image and config parameters on every create call. The Templates API guide covers creating, sharing, and launching from templates.