> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Publish the revision served by a READY release service (expected-head CAS)
> Promotes the service's revision to the project's published head only when the artifact is sealed, the service is ready, and the current head still equals `expectedHead`. Requires publish rights (owner or listed editor). A lost race answers 200 with `ok:false, code:HEAD_CONFLICT` and the current head.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/agentspace/{projectId}/deployments/{serviceId}/publish
openapi: 3.0.0
info:
title: Pria Runtime API
version: 2.0.110
description: >-
Pria API Documentation Praxis's developer platform is a core part of our
mission to empower organizations to grow better. Our APIs are designed to
enable teams of any shape or size to build robust integrations that help
them customize and get the most value out of Pria. All Pria APIs are built
using REST conventions and designed to have a predictable URL structure.
They use many standard HTTP features, including methods (POST,
GET, PUT, DELETE) and error response codes.
All API calls are
made under https://hiimpria.ai/api and all responses return standard JSON.
In these docs, you'll find lists of all available endpoints for a given API,
along with interactive code blocks for building requests. For walkthroughs
of basic usage for these APIs, check out the API guides.
servers:
- url: https://pria.praxislxp.com
description: Pria API Server
security: []
tags:
- name: Authentication
description: User authentication, registration, and password management (/api/auth)
- name: OAuth
description: OAuth authentication providers - Google, GitHub, SSO (/api/auth/oauth)
- name: User
description: User profile management and account operations (/api/user)
- name: User Institutions
description: User institution memberships and switching (/api/user/institution)
- name: User Tools
description: Available tools for authenticated users (/api/user/tools)
- name: Institutions
description: Institution settings and configuration (/api/user/institution)
- name: Conversation
description: AI conversation and Q&A endpoints (/api/ai)
- name: Realtime
description: Real-time voice AI and WebRTC sessions (/api/ai/rt)
- name: Assistant
description: AI assistant configuration and management (/api/user/assistant)
- name: History
description: Conversation history and favorites (/api/user/history)
- name: RAG
description: >-
Document upload, embedding, and retrieval-augmented generation
(/api/user/files, /api/user/rag)
- name: Setting
description: Instance variables and settings management (/api/user/setting)
- name: Branding
description: Digital twin branding and customization (/api/agent/branding)
- name: Agent
description: Agent engagement and session management (/api/agent)
- name: SDK Launch
description: >-
SDK launch token signing and verification for secure iframe embedding
(/api/auth/sdk-sign, /api/auth/sdk-verify)
- name: Testing
description: Health checks, diagnostics, and test endpoints (/api/test)
- name: Admin Accounts
description: Account management for super admins (/api/admin/account)
- name: Admin Institutions
description: Institution management for admins (/api/admin/institution)
- name: Admin Users
description: User management for admins (/api/admin/user)
- name: Admin Entitlements
description: >-
User-institution relationships and permissions
(/api/admin/userInstitution)
- name: Admin Sessions
description: Session management for admins (/api/admin/session)
- name: Admin Histories
description: Conversation history management and analytics (/api/admin/history)
- name: Admin Assistants
description: AI assistant management for admins (/api/admin/assistant)
- name: Admin Questions
description: Institution question and prompt management (/api/admin/question)
- name: Admin Tools
description: Tool configuration management (/api/admin/tool)
- name: Admin AI Models
description: AI model configuration (/api/admin/aimodel)
- name: Admin MCP Servers
description: Model Context Protocol server management (/api/admin/mcpserver)
- name: Admin Feedbacks
description: User feedback management (/api/admin/feedback)
- name: Admin Uploads
description: Upload management (/api/admin/upload)
- name: Admin Charts
description: Analytics and visualization chart management (/api/admin/chart)
- name: Audio Notes
description: Capture and ingest spoken notes into the personal vault
- name: Memory
description: User-facing memory parameters (personal + shared instance memory).
- name: My Data
description: >-
GDPR controls — personal-scope counts, async ZIP-by-email export, and
scoped soft-delete. Every endpoint pins `user = req.user._id` AND
`institution: null`; institution-scoped data is governed by the
institution's own retention policy and never reached from here.
- name: Questions
description: >-
User-facing read of the onboarding question bank used by the "create a
digital twin" wizard.
- name: Transcription
description: >-
One-shot speech-to-text for in-place dictation. Audio blob in, transcript
out — no Upload / History / RAG embeddings are persisted. Use
`/audio-notes` for anything durable.
paths:
/api/user/agentspace/{projectId}/deployments/{serviceId}/publish:
post:
tags:
- Agentspace
summary: >-
Publish the revision served by a READY release service (expected-head
CAS)
description: >
Promotes the service's revision to the project's published head only
when the artifact is sealed, the service is ready, and the current head
still equals `expectedHead`. Requires publish rights (owner or listed
editor). A lost race answers 200 with `ok:false, code:HEAD_CONFLICT` and
the current head.
parameters:
- in: path
name: projectId
required: true
schema:
type: string
- in: path
name: serviceId
required: true
schema:
type: string
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- expectedHead
properties:
expectedHead:
$ref: '#/components/schemas/AppExpectedHead'
responses:
'200':
description: Outcome
content:
application/json:
schema:
$ref: '#/components/schemas/AppDeploymentOutcome'
'400':
description: Unknown body field or malformed expectedHead
'404':
$ref: '#/components/responses/AppDeploymentNotFound'
security:
- apiKeyAuth: []
components:
schemas:
AppExpectedHead:
type: object
description: >-
The published head the caller observed. The CAS wins only if it still
matches (revisionId + generation).
required:
- revisionId
- generation
properties:
revisionId:
type: string
example: ''
generation:
type: integer
example: 0
AppDeploymentOutcome:
type: object
description: >
Typed operational outcome. `ok:false` carries a closed `code`
(HEAD_CONFLICT with `current`, ARTIFACT_NOT_SEALED, SERVICE_NOT_READY,
NOT_A_PRIOR_HEAD, SERVING_PUBLISHED_HEAD, STALE_GENERATION with
`currentGeneration`, GUEST_UNAVAILABLE, GUEST_STOP_FAILED); a lost CAS
is reported, never retried blindly.
properties:
success:
type: boolean
example: true
ok:
type: boolean
code:
type: string
nullable: true
action:
type: string
enum:
- publish
- rollback
nullable: true
publishedHead:
$ref: '#/components/schemas/AppPublishedHead'
current:
$ref: '#/components/schemas/AppPublishedHead'
url:
type: string
nullable: true
description: >-
exact public site URL of the new head (null when the content origin
is unconfigured)
AppPublishedHead:
type: object
properties:
revisionId:
type: string
description: empty when nothing is published
generation:
type: integer
publishedAt:
type: string
format: date-time
nullable: true
responses:
AppDeploymentNotFound:
description: >-
Unknown/foreign project, no edit access, or unknown/foreign service —
deliberately indistinguishable.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: not-found
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````