Create the application context

post

https://{hostname}/appsec/v1/fai-configurations/{faiConfigId}/versions/{version}/application-context

This creates the application context for a configuration version. There's one context per version, so if the version already has one, this returns a 409 error. To create or replace the context in one call, use the Update the application context operation instead. The version must still be editable. The Location header of the response gives you the URL of the context.

Path Params

faiConfigId

string

required

^[0-9]+$

Identifier for the FAI configuration.

version

integer

required

Version number of the FAI configuration.

Query Params

accountSwitchKey

string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params

Request body for creating or updating the application context for a Firewall for AI configuration version.

languages

array of strings

Array of allowed language codes for user interactions with the LLM application. Languages are specified with ISO 639-3 three-letter language codes. Run the List languages operation to get the full list of available language codes the platform supports. If not specified or empty, no language restrictions are applied.

languages

systemPrompt

string

required

length between 1 and 8192

The system prompt that defines the LLM application's intended behavior, role, and operational scope.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

URL

Loading…

Response

Choose an example:

application/json

application/problem+json

201The response provides the new application context.

400Bad request. The request isn't valid, for example an id that isn't a number, a missing or out-of-range field, a value that isn't allowed, or rule settings that conflict. The detail names the field, the value sent, and what to change.

401Unauthorized.

403Forbidden. You don't have the access this operation needs, or your account isn't entitled to a feature the request uses, such as a rule, the MODIFY action, or languages. The detail says which access or entitlement to ask for.

404Not found. A resource in the URL doesn't exist: the configuration, version, custom PII type, application, access key, or activation. The detail names the missing id and where to find valid ones.

500Internal server error. Something failed on Akamai's side. Try again later. If it keeps happening, contact Akamai support with the instance value.