Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Thank you, I was able to identify the issue. I was sending the size as an integer id instead of a slug value. I was able to correct the request and create the droplet using the following request:
{
"name": "sc-sh-isccs-001",
"region": "sfo2",
"size": "s-2vcpu-4gb",
"image": 34127022,
"ssh_keys": [20594886],
"backups": false,
"ipv6": false,
"user_data": null,
"private_networking": null,
"volumes": null,
"tags":[
"sterling",
"isccs"
]
}
I don’t immediately see anything wrong with the snippets you provided. One thing to note is that a snapshot can only be used in the datacenter where it was created unless you first make it available in a new region. The error you’re seeing is the message that would be returned if you selected a region/datacenter where the image has not been propagated.