Update a List of Option Localizations

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.zerionsoftware.com/doc/iformbuilder-v81/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "iFormBuilder V81 MCP server": {
    "url": "https://apidocs.zerionsoftware.com/doc/iformbuilder-v81/mcp"
  }
}

Close
PUT /profiles/{profile_id}/optionlists/{optionlist_id}/options/{option_id}/localizations

Headers

  • Authorization string

    e.g. Bearer {access_token}

Path parameters

  • profile_id string Required

    id of the profile

  • optionlist_id number Required

    id of the optionlist

  • option_id number Required

    id of the option

Query parameters

  • fields string

    extra information of each option localization on the list

  • limit number

    maximum count of the option localization list

  • offset number

    skip that many option localization before beginning to return

  • validate_grammar string

    returns an error for incorrect field grammar when set to true

  • all_fields boolean

    will show all fields for each option localization

  • exclude string

    will exclude specified fields

application/json

Body

  • language_code string
  • label string

Responses

  • 200 application/json

    OK

    Hide response attribute Show response attribute object
    • language_code string Required

      the updated language code

  • 207 application/json

    Multi-Status - some items succeeded and some failed. The body is an array in request order (a list request body, even with one item, always answers a list); a failed item carries error_message instead of language_code and was not written.

    Hide response attributes Show response attributes object
    • language_code string

      present when the item succeeded

    • error_message string

      present when the item failed

  • 400 application/json

    Bad Request - every item of a list request body failed. The body has the same shape as 207, with error_message on each item; nothing was written. A single-object request body that fails answers the standard error object instead.

    One of:
    Hide attribute Show attribute object
    • error_message string Required
PUT /profiles/{profile_id}/optionlists/{optionlist_id}/options/{option_id}/localizations
curl \
 --request PUT 'https://api.iformbuilder.com/exzact/api/v81/[servername]/profiles/self/optionlists/{optionlist_id}/options/{option_id}/localizations' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer {access_token}" \
 --data '[
  {
    "language_code": "zh-hans",
    "label": "失败"
  },
  {
    "language_code": "zh-hant",
    "label": "失敗"
  }
]'
Request example
[
  {
    "language_code": "zh-hans",
    "label": "失败"
  },
  {
    "language_code": "zh-hant",
    "label": "失敗"
  }
]
Response examples (200)
[
  {
    "language_code": "zh-hans"
  },
  {
    "language_code": "zh-hant"
  }
]
Response examples (207)
[
  {
    "language_code": "es"
  },
  {
    "error_message": "Parameter 'language_code' is invalid"
  }
]
Response examples (400)
[
  {
    "error_message": "Parameter 'language_code' is invalid"
  }
]
{
  "error_message": "Parameter 'language_code' is invalid"
}