Publish Form as ArcGIS Feature Layer

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

Standard setup for AI tools providing an mcp.json file

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

Close
POST /profiles/{profile_id}/pages/{page_id}/arcgis/publish

Publishes the form as a new hosted feature service in the connected account and links the form to its layer 0. The service has feature_id, latitude and longitude, then one field per element; labels, dividers, subforms, image labels and the Esri widget are left out. Text becomes a string of the element's size, number a double, toggle an integer, range a double with a range domain, and select types a string with a coded-value domain from the option list.

With with_existing_data: true every record with a location in MODIFIED_LOCATION becomes a feature; records without one are skipped. The temporary CSV item is deleted once ArcGIS finishes publishing.

The form is linked only once ArcGIS reports the publish job finished. A job still running after the server's two-minute wait stays processing while the server keeps checking it in the background, whether or not anyone polls: it links the form and turns complete when the job completes, or turns failed and leaves the form unlinked when the job fails. A job still running 30 minutes after the wait turns failed. Whatever the outcome, the temporary CSV item is deleted. When the server does not queue background work, each GET checks the job instead.

A new publish that replaces a stale processing one first finishes that one, so its CSV item is deleted too.

The request answers 202 with a request_id before the publish runs, because a publish can take minutes: poll GET on this path for complete (with feature_layer_url) or failed (with the ArcGIS error). When the server queues background work the answer is pending and the task service starts the job; otherwise it is processing and the job runs on the API server after the response is sent. One publish per form runs at a time.

Authorization

Internal API clients only, the user must be a SERVER or COMPANY user, and the user must be able to modify the page.

Headers

  • Authorization string

    e.g. Bearer {access_token}

Path parameters

  • profile_id string Required

    id of the profile

  • page_id number Required

    id of the page

application/json

Body

  • with_existing_data boolean

    Default value is false.

Responses

  • 202 application/json

    Accepted - pending when queued, processing when the API server runs it after this response; poll the status.

    Hide response attributes Show response attributes object
    • status string Required

      Values are none, pending, processing, complete, or failed.

    • request_id string
    • updated_at string(date-time)
    • stale boolean

      always present in the GET status body (not in the POST 202). True when pending or processing and updated_at is 30 minutes old or more - the publish was never picked up, or died mid-run and could not be settled as failed yet, and no longer blocks a new publish. False otherwise, including none.

    • feature_layer_url string

      present when complete

    • error string

      present when failed

  • 400 application/json

    Bad Request - with_existing_data is not a boolean.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 403 application/json

    Forbidden - not an internal client, a BASIC user, or no modify permission on the page.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 404 application/json

    Not Found - the page is not in the profile.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 409 application/json

    Conflict - the profile has no ArcGIS connection, or a publish is already running for the form.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

POST /profiles/{profile_id}/pages/{page_id}/arcgis/publish
curl \
 --request POST 'https://api.iformbuilder.com/exzact/api/v80/[servername]/profiles/self/pages/{page_id}/arcgis/publish' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer {access_token}" \
 --data '{
  "with_existing_data": false
}'
Request examples
# Headers
Authorization: Bearer {access_token}

# Payload
{
  "with_existing_data": false
}
Response examples (202)
{
  "status": "pending",
  "request_id": "9f2c4e1a7b3d5f60"
}
Response examples (400)
{
  "error_message": "string"
}
Response examples (403)
{
  "error_message": "string"
}
Response examples (404)
{
  "error_message": "string"
}
Response examples (409)
{
  "error_message": "string"
}