GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Gcore Documentation home page
  • Contact Us
  • Sign up for free
  • Home
  • Documentation
  • Reseller Documentation
  • Developer Tools
  • API Reference
  • Gcore Status
  • How to use the API Reference
  • Use Postman
  • Quick Access
  • Overview
  • Overview

This view

  • Original page
  • New address

GeezerVison is showing docs.gcore.com — Gcore API overview - Gcore Documentation

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.
ServiceBase URLReseller API
Identity & Access Management (IAM)https://api.gcore.com/iamIAM reseller
Content Delivery Network (CDN)https://api.gcore.com/cdnCDN reseller
Managed DNShttps://api.gcore.com/dns—
Cloud, GPU Cloud & AI Inferencehttps://api.gcore.com/cloudCloud reseller
Object Storagehttps://api.gcore.com/storage—
FastEdge (Edge Functions)https://api.gcore.com/fastedgeFastEdge reseller
Video Streaminghttps://api.gcore.com/streaming—
DDoShttps://api.gcore.com/security/iaas—
Edge Proxyhttps://api.gcore.com/security/edgeproxy—
WAAPhttps://api.gcore.com/waapWAAP reseller
Billing—Billing reseller

​
Authentication

An API token is required, so generate one in the Customer Portal and pass it as an APIKey value in the Authorization header: 
GET https://api.gcore.com/iam/clients/me
Authorization: APIKey <YOUR_TOKEN>
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: 
curl -H "Authorization: APIKey $GCORE_TOKEN" "https://api.gcore.com/iam/clients/me"
A 200 OK response confirms the token is valid. Sending a request from the browser UI is shown in Use the reference.

​
SDKs and Terraform

Three official clients cover the most common languages and infrastructure workflows:
ToolInstall
Python SDKpip install gcore, gcore-python
Go SDKgo get github.com/G-Core/gcore-go, gcore-go
Terraform Providerrequired_providers { gcore = { source = "G-Core/gcore" } }, Terraform Registry

​
Support

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

Was this page helpful?

Suggest editsRaise issue
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.