Skip to main content

Agent Profile APIs

Version: aju17f20mq

Use the reference below for request and response fields and operation-specific requirements.

Overview

Manage agent profiles, their versions and reusable prompt fragments. Select profiles on the conversation API using activeProfileId at creation or setActiveProfileId when sending.

Authentication​

Use an authorized backend sk_… key in X-API-Key; these configuration operations do not need an end-user identity. A console JWT belongs to the separate console surface. See Authentication.

Scoping​

Tenant context comes from the authenticated request. Client-supplied X-Tenant-Id, X-User-Id or X-Project-Id do not grant authority. The current public integration uses the default project. Do not rely on project headers for separate project, test/live or customer isolation on this API.

A profile version pins that profile record. Current fragment resolution can use the latest fragment set; a profile version alone is not a complete record of the prompt or configuration used by a turn.

Related guide: Create and version agent profiles

JSON conventions​

Requests accept snake_case or camelCase field names; responses use camelCase. Ordinary default-valued scalars and empty repeated fields can be omitted. Explicitly present optional scalars, map values and well-known JSON types follow their own presence rules: an explicit false, 0 or empty value is not universally equivalent to absence. Decode each field according to its schema. 64-bit integers use JSON strings; preserve their precision. Unknown request fields are generally discarded before validation, so a typo can silently change behavior. This is not a guarantee that arbitrary fields or future client contracts are supported. See API conventions.

Profiles​

Create, read, update, and delete agent profiles.

Versions​

Read a profile's immutable version history and the fragment set behind a version.

Prompt Fragments​

Reusable template blocks shared across profiles.

Import​

Bulk-convert an existing prompt library into profiles and fragments.

Server 1​

Travila API

https://api.travila.ai

X-API-Key​

Authorized tenant backend secret key (sk_…). No end-user identity is needed for these configuration operations. Keep the key out of client apps; authorization and provisioning still apply.

Authentication credentials

SettingValue
Security scheme typeapiKey
header parameter nameX-API-Key

Operations​

Document ID: DOC-API-agent-profiles-overview. Section identities and revisions.

SectionStable reference
OverviewDOC-API-agent-profiles-overview#overview
AuthenticationDOC-API-agent-profiles-overview#authentication
ScopingDOC-API-agent-profiles-overview#scoping
JSON conventionsDOC-API-agent-profiles-overview#json-conventions
ProfilesDOC-API-agent-profiles-overview#reference-group-1
VersionsDOC-API-agent-profiles-overview#reference-group-2
Prompt FragmentsDOC-API-agent-profiles-overview#reference-group-3
ImportDOC-API-agent-profiles-overview#reference-group-4
Server 1DOC-API-agent-profiles-overview#reference-server-1
X-API-KeyDOC-API-agent-profiles-overview#authentication-apiKeyAuth