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 import API

The import API from lakeFS — 1 operation(s) for import.

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

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

This API exposes 3 operations across 1 path, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

3 operations 1 paths 7 schemas 1 DELETE1 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 import 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 3

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

import 3
GET
/repositories/{repository}/branches/{branch}/import
get import status
importStatus 3 params → 200400401404429default
POST
/repositories/{repository}/branches/{branch}/import
import data from object store
importStart 2 params body → 202400401403404429default
DELETE
/repositories/{repository}/branches/{branch}/import
cancel ongoing import
importCancel 3 params → 204400401403404409429default

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Commit (9 properties), ImportStatus (6 properties), CommitCreation (5 properties), ImportCreation (3 properties). Each schema is shown below with its type and property counts.

ImportLocation
object
3 properties 3 required
Commit
object
9 properties 6 required
ImportStatus
object
6 properties 2 required
CommitCreation
object
5 properties 1 required
ImportCreation
object
3 properties 2 required
Error
object
1 property 1 required
ImportCreationResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lakefs-import-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 internal API
lakeFS metadata API
lakeFS objects API
lakeFS pulls API
Where this information came from

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