customer-engagement
context
facts

Update fact definition

Replaces the name and description of the fact with the given id. The new name must still be unique within the account. The value type cannot be changed after creation.

put/context/1/facts/{id}

Request

  • Base URL
    https://api.infobip.com (the document declares no server; this is the origin it was published from)
  • Auth
    • OAuth 2
      Client credentials
      Token URL: https://api.infobip.com/auth/1/oauth2/token
    • or API key in header Authorization
    • or API key in header Authorization
    • or HTTP basic

Path parameters

idstring uuid required

Surrogate identifier of a specific fact definition.

Example:0197a1c8-4a2b-7ef1-8b7c-3f0d2c9d3a11

Request body

namestring required

New fact name. Must be unique within the account.

descriptionstring required

New human-readable description of the fact.

Example request

{
  "name": "preferred_language",
  "description": "ISO 639-1 code of the customer's preferred communication language."
}

Response

OK - the updated fact definition

idstring uuid required

Surrogate identifier of this fact definition.

namestring required

Fact name, unique within the account.

descriptionstring required

Human-readable description of the fact.

valueType'STRING' | 'NUMBER' | 'BOOLEAN' | 'DATE' required

Supported value types for a fact definition.

createdAtstring date-time required

Timestamp (UTC, ISO-8601) when the fact definition was created.

updatedAtstring date-time required

Timestamp (UTC, ISO-8601) when the fact definition was last updated.

Example response

{
  "id": "0197a1c8-4a2b-7ef1-8b7c-3f0d2c9d3a11",
  "name": "preferred_language",
  "description": "Customer's preferred communication language.",
  "valueType": "STRING",
  "createdAt": "2026-09-15T10:12:33.421Z",
  "updatedAt": "2026-09-15T10:12:33.421Z"
}

Changes

No recorded changes to this operation across all 1 revision of this API.