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

lakeFS refs API

The refs API from lakeFS — 3 operation(s) for refs.

lakeFS refs API is one of 17 APIs that lakeFS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Refs. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, /api/v1.

4 operations 3 paths 11 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
/api/v1
Authentication
HTTP Basic, HTTP Bearer, API Key, API Key, API Key
License
Resource Areas
1

Authentication & Security 5

lakeFS refs API declares 5 security schemes for authenticating requests. It accepts HTTP basic authentication (basic_auth). It accepts HTTP bearer tokens (JWT) (jwt_token). An API key is passed in the cookie as internal_auth_session (cookie_auth). An API key is passed in the cookie as oidc_auth_session (oidc_auth). An API key is passed in the cookie as saml_auth_session (saml_auth). By default, every request must be authenticated.

Paths & Operations 4

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

refs 4
GET
/repositories/{repository}/refs/{ref}/commits
get commit log from ref. If both objects and prefixes are empty, return all commits.
logCommits 10 params → 200400401404429default
POST
/repositories/{repository}/refs/{sourceRef}/merge/{destinationBranch}
merge references
mergeIntoBranch 3 params body → 200400401403404409412429
GET
/repositories/{repository}/refs/{sourceRef}/merge/{destinationBranch}
find the merge base for 2 references
findMergeBase 3 params → 200400401404429default
GET
/repositories/{repository}/refs/{leftRef}/diff/{rightRef}
diff references
diffRefs 9 params → 200400401404429default

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Commit (9 properties), Merge (6 properties), Diff (5 properties), DiffObjectStat (4 properties). Each schema is shown below with its type and property counts.

Commit
object
9 properties 6 required
Diff
object
5 properties 3 required
ObjectUserMetadata
object
Error
object
1 property 1 required
FindMergeBaseResult
object
3 properties 3 required
CommitList
object
2 properties 2 required
Merge
object
6 properties
Pagination
object
4 properties 4 required
DiffObjectStat
object
4 properties 3 required
MergeResult
object
1 property 1 required
DiffList
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lakefs-refs-api-openapi.yml Raw ↑

Other APIs lakeFS publishes across the network.

lakeFS actions API
lakeFS auth API
lakeFS branches API
lakeFS commits API
lakeFS config API
lakeFS experimental API
lakeFS external API
lakeFS healthCheck API
lakeFS import API
lakeFS internal API
lakeFS metadata API
lakeFS objects API
Where this information came from

This is an independent, third-party profile of lakeFS refs 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.