git.eu API Reference

Last updated: 2026-10-09

Overview

The git.eu HTTP API serves your repositories as JSON. Every instance exposes it on its own host, under /api/v0 - for example https://<INSTANCE>.git.eu/api/v0/repos.

• v0 is a beta surface. It is not frozen: routes, fields and problem types may change without a compatibility shim.
• Requests and responses are JSON only. Send Content-Type: application/json with every request that carries a body.
• Every route requires a bearer token. There is no anonymous access - see Authentication below.

Authentication

Every request carries a personal access token in the Authorization header:

Authorization: Bearer giteu_your_token

The token must hold the api scope. Create one under Settings - Tokens on your instance (https://<INSTANCE>.git.eu/settings/tokens), tick the api scope, and copy the value: it is shown once and never again. The Git Access guide walks through token creation in detail.

A token holding only the git scope works for git clone, fetch and push, but not for this API.

The API deliberately diverges from the website: there is no anonymous access, ever. A missing, malformed, expired or revoked token is answered 401 on every route - including a read of a public repository, which the website serves to signed-out visitors.

A valid token without the api scope is answered 403 with the insufficient_scope problem on every route.

Response Envelope

Every JSON body uses the same envelope: exactly one of data and error is set - never both, never neither.

A successful response:

{
  "data": {
    "name": "my-repo",
    "isPrivate": false
  },
  "error": null
}

A failed response, served as application/problem+json:

{
  "data": null,
  "error": {
    "type": "not_found",
    "title": "Not found",
    "status": 404
  }
}

Status Semantics

Endpoints

POST /api/v0/repos/batch

Creates one or more repositories owned by the calling token. This is the only create route: a single create is a one-item batch. Every item is attempted independently, so one failure never aborts the rest; the response is always 200 with a per-item result array (never 207).

Request body

Response payload

The envelope's data member is an array; each element carries:

Example request

curl -X POST https://<INSTANCE>.git.eu/api/v0/repos/batch \
  -H "Authorization: Bearer giteu_your_token" \
  -H "Content-Type: application/json" \
  -d '{"repos":[{"displayName":"string"}]}'

Errors

Per-item errors

These never change the response status: they are carried by a failed item inside an otherwise successful 200 response.

GET /api/v0/repos

Lists every repository owned by the calling token's user, optionally sorted and filtered. There is no pagination: the full owned list is returned.

Query parameters

Optional sort/filter of the returned list. There is no pagination.

Response payload

The envelope's data member is an array; each element carries:

Example request

curl -X GET https://<INSTANCE>.git.eu/api/v0/repos \
  -H "Authorization: Bearer giteu_your_token"

Errors

GET /api/v0/repos/:owner/:name

Returns a single repository. A repository the caller may not read is reported as not found, never as a distinguishable access error.

Path parameters

Response payload

The envelope's data member carries:

Example request

curl -X GET https://<INSTANCE>.git.eu/api/v0/repos/<USERNAME>/{name} \
  -H "Authorization: Bearer giteu_your_token"

Errors

PATCH /api/v0/repos/:owner/:name

Updates a repository. Only the fields present in the body change; an absent field is left untouched, and no account default is ever merged in on update.

Path parameters

Request body

The repository fields to change. Every field is optional; an absent field is left unchanged, and no account default is ever merged in on update.

Response payload

The envelope's data member carries:

Example request

curl -X PATCH https://<INSTANCE>.git.eu/api/v0/repos/<USERNAME>/{name} \
  -H "Authorization: Bearer giteu_your_token" \
  -H "Content-Type: application/json" \
  -d '{"displayName":"string"}'

Errors

DELETE /api/v0/repos/:owner/:name

Permanently deletes a repository and its git data. The deletion is hard and cannot be undone. A successful call returns 204 with an empty body.

Path parameters

Example request

curl -X DELETE https://<INSTANCE>.git.eu/api/v0/repos/<USERNAME>/{name} \
  -H "Authorization: Bearer giteu_your_token"

Errors

Errors

An error body carries an error object in the envelope's error member, served as application/problem+json (the standard problem format, RFC 9457).

Problem Types

Every problem type this API can return, response-level and per-item alike: