Create New Users

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
POST /profiles/{profile_id}/users

Headers

  • Authorization string

    e.g. Bearer {access_token}

Path parameters

  • profile_id string Required

    id of the profile

application/json

Body

  • username string Required
  • password string Required

    At least 8 characters (the minimum is configurable per server). Servers with password complexity enabled also require an uppercase letter, a lowercase letter, a number, and one of !@#$%^&*()-_=+~`,.. Servers that enforce password history reject a previously used password. ZIM-integrated servers also enforce ZIM's policy: at least 8 characters with an uppercase letter, a lowercase letter, and a number. A user whose password fails validation is not created. Its error_message is Parameter 'Password' is invalid (ZIM's own error text on ZIM-integrated servers). The response is 400 if every user in the request fails, otherwise 207.

  • first_name string
  • last_name string
  • email string Required
  • role string

    must match "server", "company" or "basic"

    Defaults to basic when omitted. Only a Server Admin can create a server user. Every can_* flag defaults to false when omitted. The company and server roles still grant their preset permissions whatever the flags say.

  • can_form_edit boolean
  • can_thunderplug_sync boolean
  • can_assign boolean

    Record Assignment. Company Admins and Server Admins always have it; set it to give it to a basic user. On ZIM-integrated servers a grant made here survives detaching the ZIM Record Assignment policy.

  • can_edit_records boolean

    Edit Records. Lets the user edit records on forms they can view. On ZIM-integrated servers the user's ZIM policies grant or revoke this permission, and replace a value sent here at the user's next sign-in.

  • can_delete_records boolean

    Delete Records. Lets the user delete records on forms they can view. On ZIM-integrated servers the user's ZIM policies grant or revoke this permission, and replace a value sent here at the user's next sign-in.

  • can_manage_templates boolean

    Manage Document Templates. Lets the user create, edit and delete document templates. On ZIM-integrated servers the user's ZIM policies grant or revoke this permission, and replace a value sent here at the user's next sign-in.

  • can_generate_documents boolean

    Generate Documents. Lets the user generate documents from document templates. On ZIM-integrated servers the user's ZIM policies grant or revoke this permission, and replace a value sent here at the user's next sign-in.

Responses

  • 201 application/json

    Created

    Hide response attribute Show response attribute object
    • id number Required

      the created user id

  • 400

    Bad Request

POST /profiles/{profile_id}/users
curl \
 --request POST 'https://api.iformbuilder.com/exzact/api/v81/[servername]/profiles/self/users' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer {access_token}" \
 --data '{
  "username": "demo_user",
  "password": "Testing123!",
  "email": "support@iformbuilder.com"
}'
Request examples
{
  "username": "demo_user",
  "password": "Testing123!",
  "email": "support@iformbuilder.com"
}
[
  {
    "username": "inspector_1",
    "password": "Testing123!",
    "email": "inspector1@company.com",
    "role": "basic"
  },
  {
    "username": "inspector_2",
    "password": "Testing123!",
    "email": "inspector2@company.com",
    "role": "basic"
  }
]
Response examples (201)
{
  "id": 161236
}
[
  {
    "id": 161239
  },
  {
    "id": 161242
  }
]