Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Relace Repo API

The Repo API from Relace — 5 operation(s) for repo.

Relace Repo API is one of 2 APIs that Relace publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 5 paths, and defines 16 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against 5 base URLs: https://compact.endpoint.relace.run, https://instantapply.endpoint.relace.run, https://ranker.endpoint.relace.run, https://embeddings.endpoint.relace.run, https://api.relace.run.

6 operations 5 paths 16 schemas 1 DELETE1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://api.relace.run
Authentication
HTTP Bearer
License
MIT
Resource Areas
1

Authentication & Security 1

Relace Repo API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Relace API key Authorization header using the Bearer scheme.

Paths & Operations 6

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

Repo 6
POST
/v1/repo
Create a new repository
body → 201400401
GET
/v1/repo
List all repositories
5 params → 200401
DELETE
/v1/repo/{repo_id}
Delete a repository
1 param → 204401404
POST
/v1/repo/{repo_id}/update
Update repository content
1 param body → 200400401404
POST
/v1/repo/{repo_id}/retrieve
Retrieve relevant files from repository using semantic search
1 param body → 200400401404
POST
/v1/repo/{repo_id}/search
Search for specific text patterns in repository files
1 param body → 200400401404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are RetrieveRequest (6 properties), GitSource (5 properties), FilesDiffSource (3 properties), RetrieveResponse (3 properties). Each schema is shown below with its type and property counts.

Error401
object
1 property
FileSource
object
2 properties 2 required
Error400
object
1 property
GitSource
object
5 properties 2 required
CreateRepoResponse
object
1 property 1 required
RetrieveRequest
object
6 properties 1 required
SearchResponse
object
1 property 1 required
SearchRequest
object
1 property 1 required
CreateRepoRequest
object
2 properties
UpdateRepoResponse
object
1 property 1 required
FilesDiffSource
object
3 properties 3 required
UpdateRepoRequest
object
1 property 1 required
FilesOverwriteSource
object
3 properties 3 required
Error404
object
1 property
ListReposResponse
object
2 properties 1 required
RetrieveResponse
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relace-repo-api-openapi.yml Raw ↑

Other APIs Relace publishes across the network.

Relace Code API