Apply multiple settings to a data field in a single transaction

Accepts a map of setting-type to setting DTO. Semantics:

  • Key absent from payload: setting is not touched.
  • Key present with non-null value: upsert (create or update) the setting.
  • Key present with explicit null value: delete the setting from the database.

All changes are applied atomically. If any setting fails validation or applicability checks, the entire transaction rolls back and the response contains per-setting error details.

Supported setting types:

  • datetime-strategy: Controls how datetime values with timezone offsets are stored. Applicable only to DATETIME fields.
  • collection-field: Marks a STRING scalar field as containing delimited collection data.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

Unique identifier of the entity

uuid
required

Unique identifier of the data field

Body Params
collection-field
object

Request to configure a STRING field as a collection.

datetime-strategy
object

Request to set user-provided datetime strategy setting for a field. Use UTC_ONLY when you want consistent UTC storage regardless of input timezone. Use DYNAMIC_OFFSET when timezone information is important and should be maintained.

Responses

404

Entity or field not found

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json