Ana içeriğe geç

AI Prompt-Decorator Presets API

Endpoints

Authentication

All endpoints require authentication using a Personal API Access Token.

Permissions

  • Admin Only - All endpoints require admin privileges (sysAdmin user or a user with the ADMIN role). Presets are a platform-level catalog; a project-scoped AI_DEVELOPMENT token is not sufficient.

Preset Fields

FieldTypeRequiredDescription
namestringYesUnique preset name within the visible scope
contentstringYesThe instruction text injected into the request's message list
rolestringNoRole tag of the injected message: system (default), user or assistant
positionstringNoPREPEND (default) or APPEND — where the block lands relative to the client's own messages
categorystringNoOptional grouping label shown in the catalog
descriptionstringNoOptional description shown in the catalog
enabledbooleanNoWhether the preset is active (defaults to true)
projectIdstringread-onlyScope the preset belongs to (admin for global)
builtInbooleanread-onlytrue for Mongock-seeded rows (read-only), false for user-created

Blank role / position values normalize to system / PREPEND; any other value is rejected. builtIn is server-owned and ignored in request bodies — a client cannot forge a built-in preset.

Import Semantics

Importing a preset into a Prompt Decorator policy copies its values into a new, independent block. The block keeps no reference back to the catalog entry, so editing or deleting a preset afterwards never changes a policy that already imported it, and no redeploy is implied by any endpoint on this page.

Project-Scoped Surface

Besides the admin/global endpoints above (/apiops/settings/ai-prompt-decorator-presets/...), the same preset family is also exposed under a project-scoped path, so a project's own AI_DEVELOPMENT token can read the effective catalog and manage its own custom presets without needing platform ADMIN privileges:

GET /apiops/projects/{projectName}/ai-prompt-decorator-presets/
GET /apiops/projects/{projectName}/ai-prompt-decorator-presets/{presetName}/
POST /apiops/projects/{projectName}/ai-prompt-decorator-presets/{presetName}/
PUT /apiops/projects/{projectName}/ai-prompt-decorator-presets/{presetName}/
DELETE /apiops/projects/{projectName}/ai-prompt-decorator-presets/{presetName}/

Same 5-endpoint shape, request/response bodies and field surface as the admin endpoints documented on this page — only the base path, scope resolution and permission differ:

Admin surface (/apiops/settings/...)Project surface (/apiops/projects/{projectName}/...)
Scope resolutionOptional ?projectId= query parameter (default admin/global scope){projectName} path segment, resolved to the caller's own project — never a query parameter
PermissionSystem admin (sysAdmin user or ADMIN role)AI_DEVELOPMENT + VIEW (read) / MANAGE (write) in the project
Read visibilityPresets in the resolved scope onlyUnion of built-in presets ∪ admin-shared custom presets ∪ this project's own custom presets
Write visibilityAny non-built-in preset in the resolved scopeOnly presets this project owns. A name that only resolves to a built-in or admin-shared preset is treated as not existing for this project: POST creates a new project-owned preset (and fails on the name collision), while PUT/DELETE report the preset as not found
Built-in presetsRead-onlyRead-only