How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
GitLab CI/CD

GitLab CI/CD geo API

Operations related to Geo

Documentation Provider Profile APIs.io OpenAPI GitHub

GitLab CI/CD geo API is one of 98 APIs that GitLab CI/CD publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geo. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 9 operations across 9 paths, and defines 9 schemas. It is described by OpenAPI 2.0, at version v4.

Requests are made against the base URL https://gitlab.com/api/v4.

9 operations 9 paths 9 schemas 3 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
v4
Base URL
https://gitlab.com/api/v4
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

GitLab CI/CD geo API declares 2 security schemes for authenticating requests. An API key is passed in the header as PRIVATE-TOKEN (access_token_header). An API key is passed in the query as private_token (access_token_query).

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 3 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

geo 9

Operations related to Geo

GET
/api/v4/geo/proxy
Determine if a Geo site should proxy requests
getApiV4GeoProxy → 200403
GET
/api/v4/geo/retrieve/{replicable_name}/{replicable_id}
Internal endpoint that returns a replicable file
getApiV4GeoRetrieveReplicableNameReplicableId 2 params → 200401404
GET
/api/v4/geo/repositories/{gl_repository}/pipeline_refs
Used by secondary runners to verify the secondary instance has the very latest version
getApiV4GeoRepositoriesGlRepositoryPipelineRefs 1 param → 200401404
POST
/api/v4/geo/status
Internal endpoint that posts the current node status
postApiV4GeoStatus 1 param → 200400401
POST
/api/v4/geo/proxy_git_ssh/info_refs_upload_pack
Internal endpoint that returns info refs upload pack for clone or pull operations
postApiV4GeoProxyGitSshInfoRefsUploadPack 1 param → 200401
POST
/api/v4/geo/proxy_git_ssh/upload_pack
Internal endpoint that posts git-upload-pack for clone or pull operations
postApiV4GeoProxyGitSshUploadPack 1 param → 200401
POST
/api/v4/geo/proxy_git_ssh/info_refs_receive_pack
Internal endpoint that returns git-received-pack output for git push
postApiV4GeoProxyGitSshInfoRefsReceivePack 1 param → 200401
POST
/api/v4/geo/proxy_git_ssh/receive_pack
Internal endpoint that posts git-receive-pack for git push
postApiV4GeoProxyGitSshReceivePack 1 param → 200401
POST
/api/v4/geo/node_proxy/{id}/graphql
Query the GraphQL endpoint of an existing Geo node
postApiV4GeoNodeProxyIdGraphql 1 param → 200404500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are API_Entities_GeoNodeStatus (410 properties), API_Entities_NamespaceBasic (8 properties), postApiV4GeoProxyGitSshUploadPack (3 properties), postApiV4GeoProxyGitSshReceivePack (3 properties). Each schema is shown below with its type and property counts.

postApiV4GeoProxyGitSshUploadPack
object
Responsible for making HTTP POST /repo.git/git-upload-pack request from secondary gitlab-shell to primary
3 properties 3 required
API_Entities_GeoNodeStatus
object
APIEntitiesGeoNodeStatus model
410 properties 409 required
API_Entities_NamespaceBasic
object
8 properties 8 required
postApiV4GeoProxyGitSshInfoRefsReceivePack
object
Responsible for making HTTP GET /repo.git/info/refs?service=git-receive-pack request from secondary gitlab-shell to primary
2 properties 2 required
postApiV4GeoProxyGitSshInfoRefsUploadPack
object
Responsible for making HTTP GET /repo.git/info/refs?service=git-upload-pack request from secondary gitlab-shell to primary
2 properties 2 required
postApiV4GeoStatus
object
Posts the current node status to the primary site
1 property
StorageShardEntity
object
1 property 1 required
API_Entities_Geo_PipelineRefs
object
APIEntitiesGeoPipelineRefs model
1 property 1 required
postApiV4GeoProxyGitSshReceivePack
object
Responsible for making HTTP POST /repo.git/info/refs?service=git-receive-pack request from secondary gitlab-shell to primary
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gitlab-ci-geo-api-openapi.yml Raw ↑

Other APIs GitLab CI/CD publishes across the network.

GitLab GraphQL API
AE Profile APIs.io
GitLab CI/CD access_requests API
AE Profile APIs.io
GitLab CI/CD access_tokens API
AE Profile APIs.io
GitLab CI/CD agents API
AE Profile APIs.io
GitLab CI/CD alert_management API
AE Profile APIs.io
GitLab CI/CD applications API
AE Profile APIs.io
GitLab CI/CD attestations API
AE Profile APIs.io
GitLab CI/CD audit_events API
AE Profile APIs.io
GitLab CI/CD avatars API
AE Profile APIs.io
GitLab CI/CD award_emoji API
AE Profile APIs.io
GitLab CI/CD badges API
AE Profile APIs.io
GitLab CI/CD batched_background_migrations API
AE Profile APIs.io
#Geo
← Back to G APIs
API Details
ID
gitlab-ci:gitlab-ci-geo-api
Base URL
https://gitlab.com/api/v4
Docs
https://docs.gitlab.com/api/
Provider
GitLab CI/CD
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=gitlab-ci-geo-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/gitlab-ci-geo-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of GitLab CI/CD geo API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.