JSON REST API

Authentication

Create a personal access token in Settings → Tokens, then send it as a Bearer token. API authentication uses the token, rather than your browser session. No CSRF token is needed for these API routes.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     https://git.bvdl.io/api/v1/user

Missing required, invalid, expired, or revoked tokens return 401. Tokens belonging to suspended accounts are also rejected. HTTP Basic authentication is supported with the token as the password, for example curl -u "username:$TOKEN".

Response formats

Successful reads and updates return 200; creation returns 201. A single resource is wrapped in data. Examples throughout this page show the actual field names with illustrative values.

{
    "data": {
        "name": "main",
        "ref": "refs/heads/main",
        "commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "protected": false
    }
}

Paginated collections return data as an array and meta as an object. IDs and counts are numbers, flags are booleans, and timestamps use ISO 8601. Nullable fields are returned as null; fields conditionally included by an endpoint are called out below.

Pagination

List endpoints in both API versions accept an integer page from 1 to 100000 (default 1) and an integer per_page from 1 to 100 (default 30). Malformed, empty, or out-of-range pagination values return 422 with field errors.

{
    "data": [
        {
            "name": "main",
            "ref": "refs/heads/main",
            "commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
            "protected": false
        }
    ],
    "meta": {
        "total": 1,
        "page": 1,
        "per_page": 30,
        "last_page": 1
    }
}

Increment page until it reaches meta.last_page. Pages beyond the collection return an empty data array. No pagination links or cursors are returned. Search and contribution graphs do not use this envelope.

Errors & status codes

For v1 request errors, error is a message string. Use the HTTP status for control flow; message text may vary. Validation errors add a top-level fields map of field names to arrays of messages.

{
    "error": "The title field is required.",
    "fields": {
        "title": [
            "The title field is required."
        ]
    }
}

A merge waiting for commit indexing returns 409 with code: indexing_pending. No merge was performed. Wait at least the Retry-After seconds before retrying the merge with the same reviewed sha; use bounded retries with backoff if it remains pending. The delay is guidance, not a guarantee that indexing will have finished.

{
    "error": "Commit history is still being indexed. Nothing was merged; wait at least 5 seconds, then refresh the pull request or retry the merge.",
    "code": "indexing_pending",
    "retry_after": 5
}

Query filters must have the documented types and allowed values; arrays such as ?state[]=open return 422. Omitted or empty optional filters use their defaults. Unknown label names and milestone IDs simply match no issues.

A private repository you may not read returns 404, exactly like a nonexistent repository: {"error":"Not found."}.

Rate limits

The v1 API allows 60 requests per minute per authenticated token owner, or per IP for anonymous requests. Multiple tokens for one account share the same budget. Unversioned API routes (including contribution graphs) have a separate budget of 120 per minute per token owner, or 60 per minute per anonymous IP.

For v1 responses, inspect X-RateLimit-Limit and X-RateLimit-Remaining. On 429, wait the seconds specified by Retry-After. The v1 rate-limit body also supplies retry_after:

{
    "error": "Too many requests. Please slow down and try again later.",
    "retry_after": 60
}

REST endpoints / v1

Users

Look up the account behind a token or a public user profile. Profiles never include the account email address.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/users/octocat"

{
    "data": {
        "id": 1,
        "username": "octocat",
        "name": "Octocat",
        "bio": null,
        "avatar_url": null,
        "created_at": "2026-09-01T12:00:00+00:00"
    }
}

User fields: id (integer), username and name (strings), bio and avatar_url (nullable strings), created_at (nullable timestamp). avatar_url is an application-served upload URL or null; external avatar URLs are never returned. Nested users use the same fields. Deleted issue, pull request, and release authors are represented by null.

REST endpoints / v1

Repositories

Read repository metadata and manage repositories under your own account. These endpoints do not upload files or Git objects; use Git to push your code.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories?sort=updated&per_page=30"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"name":"hello-world","description":"My first repository","private":false}' \
     "https://git.bvdl.io/api/v1/repositories"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world"

curl -X PATCH -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"description":"Updated project description"}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world"

curl -X DELETE -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world"

{
    "data": {
        "id": 1,
        "name": "hello-world",
        "full_name": "octocat/hello-world",
        "clone_url": "https://git.bvdl.io/octocat/hello-world.git",
        "owner": {
            "id": 1,
            "username": "octocat",
            "name": "Octocat",
            "bio": null,
            "avatar_url": null,
            "created_at": "2026-09-01T12:00:00+00:00"
        },
        "private": false,
        "visibility": "public",
        "description": "My first repository",
        "default_branch": "refs/heads/main",
        "fork": false,
        "forked_from_id": null,
        "stars_count": 0,
        "forks_count": 0,
        "primary_language": null,
        "topics": [],
        "pushed_at": "2026-09-01T12:00:00+00:00",
        "created_at": "2026-09-01T12:00:00+00:00",
        "updated_at": "2026-09-01T12:00:00+00:00"
    }
}

Counts and IDs are integers; private and fork are booleans; topics is a string array. description, default_branch, primary_language, forked_from_id and pushed_at can be null. clone_url is an absolute HTTPS/HTTP URL on this instance. topics is included on reads and updates but omitted on creation.

REST endpoints / v1

Branches

Read branch names, their current commit IDs, and whether a protection rule matches each branch.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/branches"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/branches/main"

{
    "data": {
        "name": "main",
        "ref": "refs/heads/main",
        "commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "protected": false
    }
}

name, ref and commit are strings; protected is a boolean. commit is the full object ID, not an embedded commit object.

REST endpoints / v1

Commits

Read indexed commit history, newest committed first. Indexing happens after a push, so new commits may take time to appear.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/commits?sha=main"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/commits/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"

{
    "data": {
        "sha": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "tree": "cccccccccccccccccccccccccccccccccccccccc",
        "message": "Initial commit",
        "author": {
            "name": "Octocat",
            "email": "octocat@example.com",
            "date": "2026-09-01T12:00:00+00:00"
        },
        "committer": {
            "name": "Octocat",
            "email": "octocat@example.com",
            "date": "2026-09-01T12:00:00+00:00"
        },
        "parents": [],
        "stats": {
            "additions": 4,
            "deletions": 0,
            "total": 4,
            "files_changed": 1
        }
    }
}

sha, tree and message are strings. Git author and committer objects contain name, email and a nullable date, distinct from user profile resources. parents (string array) and stats (integer counts) appear only on the detail endpoint. Stats fall back to zero if stored objects are unavailable.

REST endpoints / v1

Commit statuses

Report CI results by context. The path sha must contain exactly 40 lowercase hexadecimal characters; malformed values return 422.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/commits/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/statuses"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"context":"ci/tests","state":"success","description":"All tests passed"}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/commits/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/statuses"

{
    "data": {
        "commit_id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "context": "ci/tests",
        "state": "success",
        "description": "All tests passed",
        "updated_at": "2026-09-01T12:00:00+00:00"
    }
}

commit_id, context and state are strings. description is nullable; updated_at is a timestamp. Status history is replaced per context rather than appended.

REST endpoints / v1

Issues

Issues are addressed by their per-repository number, not a global database ID.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/issues?state=all&labels=documentation"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"title":"Improve the README","body":"Add installation instructions."}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/issues"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/issues/1"

curl -X PATCH -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"state":"closed"}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/issues/1"

{
    "data": {
        "number": 1,
        "title": "Improve the README",
        "body": "Add installation instructions.",
        "state": "open",
        "author": {
            "id": 1,
            "username": "octocat",
            "name": "Octocat",
            "bio": null,
            "avatar_url": null,
            "created_at": "2026-09-01T12:00:00+00:00"
        },
        "labels": [
            {
                "id": 2,
                "name": "documentation",
                "color": "0969da"
            }
        ],
        "milestone": {
            "id": 1,
            "title": "First release",
            "state": "open",
            "due_date": null
        },
        "comments": 0,
        "closed_at": null,
        "created_at": "2026-09-01T12:00:00+00:00",
        "updated_at": "2026-09-01T12:00:00+00:00"
    }
}

number and comments are integers; comments is a count, not comment bodies. body, author, milestone and closed_at can be null. Labels contain id, name and color. Milestones contain id, title, state and nullable due_date. Timestamps use ISO 8601.

REST endpoints / v1

Pull requests

List, inspect, open and merge pull requests. Closing, reviewing and editing pull requests are available through the web interface.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/pulls?state=all"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"title":"Update documentation","base":"main","head":"docs"}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/pulls"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/pulls/1"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/pulls/1/diff"

curl -X PUT -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"sha":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}' \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/pulls/1/merge"

{
    "data": {
        "number": 2,
        "title": "Update documentation",
        "body": null,
        "state": "open",
        "base_ref": "main",
        "head_ref": "docs",
        "base_commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "head_commit": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
        "merge_commit": null,
        "author": {
            "id": 1,
            "username": "octocat",
            "name": "Octocat",
            "bio": null,
            "avatar_url": null,
            "created_at": "2026-09-01T12:00:00+00:00"
        },
        "merged_at": null,
        "merged_by": null,
        "created_at": "2026-09-01T12:00:00+00:00",
        "updated_at": "2026-09-01T12:00:00+00:00"
    }
}

number is an integer. state is open, closed or merged. base_ref and head_ref are short branch names; base_commit and head_commit are commit IDs. body, author, merged_at and merged_by can be null. merged_by uses the User resource. The /diff JSON data contains available, truncated, changed_files, additions, deletions and files. Each file has filename, status (added/modified/deleted), additions, deletions, binary, available, too_large, base_mode, head_mode and patch (a complete per-file Git diff, or null for binary, oversized or missing blobs). Totals cover only returned, computed files; available describes the comparison baseline, so also check each file. At most 500 files are returned; truncated flags omitted files. Blobs over 1 MiB are not loaded; text rendering is bounded to 512 KiB per side, 5,000 combined lines and 1,000,000 comparison cells. Request-wide read budgets can also return 422. JSON replaces invalid UTF-8 with replacement characters; raw text preserves bytes. Renames appear as deletion plus addition. Raw binary changes use Git binary-difference notices, not binary patches. File modes, submodules and missing final newlines are preserved. Responses are private and not cacheable. Patch/email format is not supported.

REST endpoints / v1

Releases

Read release metadata. Creating releases and uploading assets are currently available through the web interface only. Drafts are visible only to callers who may manage releases; others receive 404 for a draft.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/releases"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/releases/1"

{
    "data": {
        "id": 1,
        "tag_name": "v1.0.0",
        "name": "First release",
        "body": null,
        "draft": false,
        "prerelease": false,
        "author": {
            "id": 1,
            "username": "octocat",
            "name": "Octocat",
            "bio": null,
            "avatar_url": null,
            "created_at": "2026-09-01T12:00:00+00:00"
        },
        "assets_count": 1,
        "assets": [
            {
                "id": 1,
                "filename": "source.zip",
                "size": 1024,
                "content_type": "application/zip",
                "download_count": 0,
                "download_url": "https://git.bvdl.io/octocat/hello-world/releases/1/assets/1/download",
                "uploaded_at": "2026-09-01T12:00:00+00:00",
                "created_at": "2026-09-01T12:00:00+00:00"
            }
        ],
        "published_at": "2026-09-01T12:00:00+00:00",
        "created_at": "2026-09-01T12:00:00+00:00",
        "updated_at": "2026-09-01T12:00:00+00:00"
    }
}

IDs and counts are integers; draft and prerelease are booleans. body, author and published_at can be null. Asset size is bytes. download_url is an absolute web URL (or null when unavailable); private downloads require web authorization and do not use these API token routes.

REST endpoints / v1

Stars & watches

Stars bookmark a repository; watches subscribe to activity. All PUT and DELETE operations here are idempotent and return 204 with an empty body, even when already in the requested state. They need read access to the repository and a write-capable token.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/starred"

curl -X PUT -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/starred/octocat/hello-world"

curl -X DELETE -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/starred/octocat/hello-world"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/stargazers"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/watched"

curl -X PUT -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/watched/octocat/hello-world"

curl -X DELETE -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/user/watched/octocat/hello-world"

List responses use the Repository and User shapes above with the standard pagination envelope. Mutation responses have no JSON body to parse.

REST endpoints / v1

Search

Search repositories, users and open issues in one request. Each group has at most 20 results; there is no pagination.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/search?q=hello&type=repos"

{
    "repositories": [
        {
            "id": 1,
            "name": "hello-world",
            "full_name": "octocat/hello-world",
            "description": "My first repository",
            "private": false,
            "stars_count": 0,
            "owner": {
                "username": "octocat",
                "name": "Octocat"
            }
        }
    ],
    "users": [
        {
            "id": 1,
            "username": "octocat",
            "name": "Octocat"
        }
    ],
    "issues": [
        {
            "number": 1,
            "title": "Say hello",
            "state": "open",
            "repository": "octocat/hello-world",
            "created_at": "2026-09-01T12:00:00+00:00"
        }
    ]
}

This example shows an unfiltered search across all three groups. Search returns lean objects as shown, rather than full API resources. Repositories are sorted by stars then name; users by username; open issues by newest ID.

REST endpoints / v1

OAuth and OpenID Connect

Register clients under Settings → Applications. Use authorization codes with S256 PKCE, an exact HTTPS callback, state, and an OIDC nonce. Consent selects repositories explicitly. Access tokens last one hour; refresh tokens rotate and last 30 days, with an absolute 90-day connection lifetime.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/.well-known/openid-configuration"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/jwks"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/authorize"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/token"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/userinfo"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/userinfo"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/oauth/revoke"

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/oauth/consent/repositories"

Scopes: openid, profile, email, repositories:read, webhooks:manage. OAuth supports /api/v1/user (profile), selected repository listing/details/branches and Git HTTPS clone/fetch (repositories:read), and connection-owned push webhooks (webhooks:manage plus repositories:read and current administrator rights). Other API actions and pushes are refused. Use a Git credential helper with username oauth2 and the access token as password. Reauthorize to change selected repositories or scopes. Suspension, security changes, permission loss and revocation are enforced on subsequent access and queued webhook delivery. The hosting backend must validate state and OIDC tokens, verify X-Webhook-Signature over the raw payload, deduplicate X-Webhook-Delivery and serialize deployment promotion.

REST endpoints / v1

Deployment webhooks

Manage signed push hooks. OAuth clients can manage only hooks belonging to their exact connection; manually created hooks and other connections are isolated.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/webhooks"

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/webhooks"

curl -X PATCH -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/webhooks/{webhook}"

curl -X DELETE -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     "https://git.bvdl.io/api/v1/repositories/octocat/hello-world/webhooks/{webhook}"

{
    "data": {
        "id": 1,
        "url": "https://hosting.example/webhooks/git",
        "events": [
            "push"
        ],
        "active": true,
        "has_secret": true
    }
}

Push payloads include repository.id, ref, branch, before, after and pusher. Match the configured full branch ref and deploy the after commit. Verify X-Webhook-Signature (sha256= plus HMAC-SHA256 of the raw body) in constant time, and deduplicate X-Webhook-Delivery across retries. Branch deletion is a separate event and is not included in push-only subscriptions.

Additional endpoints / api

Organizations

Organization reads are available on the unversioned API only. Both require a token and use the unversioned response format.

curl -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     https://git.bvdl.io/api/orgs/bvdl

{
    "data": {
        "id": 1,
        "name": "BVDL",
        "slug": "bvdl",
        "description": null,
        "avatar_url": null,
        "created_at": "2026-09-01T12:00:00+00:00",
        "member_count": 2,
        "repo_count": 3
    }
}

IDs and counts are integers; name and slug are strings; description and avatar_url are nullable strings. avatar_url is currently null; organizations use generated initials. List items add role instead of member_count and repo_count.

Additional endpoints / api

Contribution graph

Returns daily indexed commit counts. A username or public repository can be queried anonymously. With neither selector, a token is required and the graph belongs to the token holder. Private repositories require read permission; unknown or unreadable targets return 404.

curl -H "Accept: application/json" \
     "https://git.bvdl.io/api/contributions/graph?username=octocat&weeks=1"

{
    "weeks": [
        [
            {
                "date": "2026-08-30",
                "count": 0
            },
            {
                "date": "2026-08-31",
                "count": 2
            },
            {
                "date": "2026-09-01",
                "count": 1
            },
            {
                "date": "2026-09-02",
                "count": 0
            },
            {
                "date": "2026-09-03",
                "count": 0
            },
            {
                "date": "2026-09-04",
                "count": 0
            },
            {
                "date": "2026-09-05",
                "count": 0
            }
        ]
    ]
}

weeks contains arrays of seven days, Sunday first, oldest week first through the current week. date is YYYY-MM-DD; count is an integer (zero on quiet or future days). There is no data or meta wrapper. Validation and missing-token errors use the unversioned nested shape; an invalid supplied token is rejected by authentication as {"error":"Unauthenticated."}.

Additional endpoints / api

Unversioned API

The original endpoints remain available at /api. Every endpoint in the table below requires a token, including public repository reads. Use the documented paths and shapes for your selected API version; switching only the prefix is not sufficient.

All list endpoints accept page and per_page with the same defaults and caps as v1, but omit meta.last_page. Stop when page × per_page ≥ total. Single resources still use a data wrapper.

{
    "data": [],
    "meta": {
        "total": 0,
        "page": 1,
        "per_page": 30
    }
}

{
    "error": {
        "message": "The title field is required.",
        "code": "validation_failed",
        "fields": {
            "title": [
                "The title field is required."
            ]
        }
    }
}

Other errors use error.message and error.code, with codes such as unauthenticated, forbidden, not_found, method_not_allowed or http_error. Rate-limit errors use the standard unversioned HTTP-error envelope, with no v1 retry_after body field.

Resource differences

Unversioned repository objects contain id, name, full_name, owner, visibility, private, default_branch, description, fork, pushed_at and created_at. Owner objects contain only id, username and name.

Issue and pull request fields match v1 except that nested users include only id, username and name, and issue milestones omit due_date. There is no unversioned issue update route. These routes do not expose v1 release, status, search, star or watch operations.

curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -d '{"name":"hello-world","visibility":"public"}' \
     https://git.bvdl.io/api/repositories