Gcore REST API - Gcore Documentation

One API token authenticates to every Gcore product in the Gcore Customer Portal — Cloud, CDN, DNS, Storage, FastEdge, and others — so authentication, request format, and response patterns are consistent across all of them.

Learning path

Start here and follow the guides in order:

Step	Guide	What it covers
1	API basics	Terminal, curl, JSON, environment variables — the tools and concepts used throughout
2	Authentication	Create an API token and send it with every request
3	First API call	Verify the token, find project and region IDs, make the first resource call
4	Async operations	Create and delete calls return a task ID — here is how to wait for the result
5	Error handling	Error response format, common error types, and retry strategy
6	Pagination	Retrieve large result sets with `limit` and `offset`
7	Tools	Postman, HTTPie, VS Code REST Client — setup and usage
8	SDKs	Python, Go, and JavaScript clients for production code

Base URLs

Each Gcore product has a dedicated base URL. The same permanent API token authenticates to all of them — no separate credentials per product:

Product	Base URL
Cloud — VMs, Kubernetes, LB, Volumes	`https://api.gcore.com/cloud`
GPU Cloud	`https://api.gcore.com/cloud`
Everywhere Inference	`https://api.gcore.com/cloud`
IAM (users, tokens)	`https://api.gcore.com/iam`
CDN	`https://api.gcore.com/cdn`
Managed DNS	`https://api.gcore.com/dns`
Object Storage	`https://api.gcore.com/storage`
FastEdge	`https://api.gcore.com/fastedge`
Streaming	`https://api.gcore.com/streaming`
WAAP	`https://api.gcore.com/waap`
DDoS Protection	`https://api.gcore.com/security`