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-v60/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "iFormBuilder V60 MCP server": {
    "url": "https://apidocs.zerionsoftware.com/doc/iformbuilder-v60/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

    Minimum 8 characters. Servers with password complexity enabled also require an uppercase letter, a lowercase letter, a number, and one of !@#$%^&*()-_=+~`,. Servers that keep password history also reject a previously used password. A failing password returns 400 with error_message "Parameter 'password' is invalid". When a list of users is sent, the error is set on that user's item only; the other users in the request are still saved. ZIM-integrated servers also apply ZIM's own password policy and return 400 with ZIM's error description as the message.

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

    must match "server", "company" or "basic". Defaults to basic when omitted. Only a caller with the server role can set server. Other callers get 403. Each can_* flag defaults to false when omitted. The company and server roles always include can_edit_records and can_delete_records.

  • can_form_edit boolean
  • can_thunderplug_sync boolean
  • can_edit_records boolean

    Can edit records

  • can_delete_records boolean

    Can delete records

  • can_manage_templates boolean

    Can create and edit document templates

  • can_generate_documents boolean

    Can generate documents

Responses

  • 201 application/json

    Created

    Hide response attribute Show response attribute object
    • id number Required

      the created user id

POST /profiles/{profile_id}/users
curl \
 --request POST 'https://servername.iformbuilder.com/exzact/api/v60/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
  }
]