Skip to main content
Every Gcore product is backed by a public REST API, the same API used by the Gcore Customer Portal and the official SDKs. All product APIs are available under the same base URL: https://api.gcore.com.

​
Use cases

Gcore’s API covers provisioning, configuration changes, and event-driven automation, as well as read operations:
  • Automating CDN cache purges, DNS record updates, and VM provisioning.
  • Integrating Gcore services into CI/CD pipelines, Terraform workflows, Kubernetes Operators, and custom back-office tools.
  • Reacting to real-time metrics and keeping infrastructure in a desired state without manual intervention.

​
Base URLs by product

Each Gcore product has its own path prefix on the shared base https://api.gcore.com. Requests use HTTPS on TCP port 443, which means a firewall that allows outbound HTTPS already covers the API.

​
Authentication

An API token is required, so generate one in the Customer Portal and pass it as an APIKey value in the Authorization header:
The Authorization header is case-insensitive. The same API token works across all Gcore product APIs. Reseller accounts authenticate with a separate Admin Portal token.

​
Rate limits

The API allows 100 requests per second from one IP address. The login endpoint accepts 5 requests per minute from one IP address. That address can fail login 5 times per hour, and a request over either login quota receives 429 Too Many Requests.

​
Quick start

Verify the token by fetching account details:
A 200 OK response confirms the token is valid.

​
SDKs and Terraform

Three official clients cover the most common languages and infrastructure workflows:

​
Support

For production incidents, check status.gcore.com. Developer questions go to GitHub Discussions in the relevant SDK repo or to support@gcore.com. Feature requests and bugs are tracked on Gcore Roadmap.