Opik Pairing API
Pairing sessions for the `opik connect` and `opik endpoint` CLI commands
Pairing sessions for the `opik connect` and `opik endpoint` CLI commands
openapi: 3.1.0
info:
title: Opik REST Pairing API
description: "The Opik REST API is currently in beta and subject to change. If you have any questions or feedback about the APIs, please reach out on GitHub: https://github.com/comet-ml/opik.\n\nAll of the methods listed in this documentation are used by either the SDK or the UI to interact with the Opik server. As a result,\nthe methods have been optimized for these use-cases in mind. If you are looking for a method that is not listed above, please create\nand issue on GitHub or raise a PR!\n\nOpik includes two main deployment options that results in slightly different API usage:\n\n- **Self-hosted Opik instance:** You will simply need to specify the URL as `http://localhost:5173/api/<endpoint_path>` or similar. This is the default option for the docs.\n- **Opik Cloud:** You will need to specify the Opik API Key and Opik Workspace in the header. The format of the header should be:\n\n ```\n {\n \"Comet-Workspace\": \"your-workspace-name\",\n \"authorization\": \"your-api-key\"\n }\n ```\n\n The full payload would therefore look like:\n \n ```\n curl -X GET 'https://www.comet.com/opik/api/v1/private/projects' \\\n -H 'Accept: application/json' \\\n -H 'Comet-Workspace: <your-workspace-name>' \\\n -H 'authorization: <your-api-key>'\n ```\n\n Do take note here that the authorization header value does not include the `Bearer ` prefix. To switch to using the Opik Cloud in the documentation, you can\n click on the edit button displayed when hovering over the `Base URL` displayed on the right hand side of the docs.\n"
contact:
name: Github Repository
url: https://github.com/comet-ml/opik
license:
name: Apache 2.0
url: http://www.apache.org/licenses/LICENSE-2.0.html
version: 1.0.0
servers:
- url: http://localhost:5173/api
description: Local server
- url: https://www.comet.com/opik/api
description: Opik Cloud
tags:
- name: Pairing
description: Pairing sessions for the `opik connect` and `opik endpoint` CLI commands
paths:
/v1/private/pairing/sessions/{sessionId}/activate:
post:
tags:
- Pairing
summary: Activate a pairing session
description: Verify the activation HMAC and flip the runner row to CONNECTED
operationId: activatePairingSession
parameters:
- name: sessionId
in: path
required: true
schema:
type: string
format: uuid
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ActivateRequest'
responses:
'201':
description: Session activated
headers:
Location:
description: URI of the runner
style: simple
'403':
description: Invalid HMAC
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'404':
description: Session not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'409':
description: Session already activated
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'422':
description: Unprocessable entity
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'429':
description: Too many requests
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
/v1/private/pairing/sessions:
post:
tags:
- Pairing
summary: Create a pairing session
description: Register a short-lived pairing session that a local daemon will later activate via HMAC
operationId: createPairingSession
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/CreateSessionRequest'
responses:
'201':
description: Session created
content:
application/json:
schema:
$ref: '#/components/schemas/CreateSessionResponse'
'400':
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'404':
description: Project not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'422':
description: Unprocessable entity
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'429':
description: Too many requests
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
components:
schemas:
ErrorMessage:
type: object
properties:
code:
type: integer
format: int32
message:
type: string
details:
type: string
CreateSessionRequest:
required:
- activation_key
- project_id
- type
type: object
properties:
project_id:
type: string
format: uuid
activation_key:
maxLength: 44
minLength: 43
type: string
ttl_seconds:
maximum: 600
minimum: 60
type: integer
format: int32
type:
type: string
enum:
- connect
- endpoint
CreateSessionResponse:
type: object
properties:
session_id:
type: string
format: uuid
runner_id:
type: string
format: uuid
ActivateRequest:
required:
- hmac
- runner_name
type: object
properties:
runner_name:
maxLength: 128
minLength: 0
type: string
hmac:
maxLength: 44
minLength: 43
type: string