Import 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-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 /integrations/arcgis/imports

Creates a form in the caller's profile from a feature layer and links the form to that layer. The form gets an Esri widget, then one element per layer field:

Layer field Element
coded-value domain pick list, with a new option list
range domain range
esriFieldTypeDate date-time
esriFieldTypeDateOnly date
double, single, integer, small and big integer number
anything else text, sized to the field's length

The object id field is not imported. Global id, geometry, blob and raster fields become optional text elements; records never send them to the layer. Required (nullable: false) and read-only (editable: false) carry over. A field whose name has characters an element name cannot hold, is reserved, starts with a digit or collides with another is renamed and listed in renamed_fields; the form keeps the layer field name, and records send a renamed element to that field. If any step fails, the half-created form and its option lists are removed.

Authorization

Internal API clients only, and the user must be a SERVER or COMPANY user.

Headers

  • Authorization string

    e.g. Bearer {access_token}

application/json

Body Required

  • feature_layer_url string Required

    https URL ending in /FeatureServer/{layer_id}; a query string is dropped

Responses

  • 201 application/json

    Created

    Hide response attributes Show response attributes object
    • id integer
    • name string
    • label string
    • feature_layer_url string
    • element_count integer

      elements created from layer fields, the Esri widget not counted

    • renamed_fields array[object]
      Hide renamed_fields attributes Show renamed_fields attributes object
      • field string
      • element string
  • 400 application/json

    Bad Request - feature_layer_url is not an https FeatureServer layer URL, is on a host the connection may not reach, cannot be read with the account, or is not a feature layer; or the form could not be created (for example the profile's form limit).

    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, or a BASIC user.

    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.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 502 application/json

    Bad Gateway - ArcGIS could not be reached or answered with an error.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

POST /integrations/arcgis/imports
curl \
 --request POST 'https://api.iformbuilder.com/exzact/api/v81/[servername]/integrations/arcgis/imports' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer {access_token}" \
 --data '{
  "feature_layer_url": "https://services7.arcgis.com/AbC123/arcgis/rest/services/street_trees/FeatureServer/0"
}'
Request examples
# Headers
Authorization: Bearer {access_token}

# Payload
{
  "feature_layer_url": "https://services7.arcgis.com/AbC123/arcgis/rest/services/street_trees/FeatureServer/0"
}
Response examples (201)
{
  "id": 42,
  "name": "string",
  "label": "string",
  "feature_layer_url": "string",
  "element_count": 42,
  "renamed_fields": [
    {
      "field": "string",
      "element": "string"
    }
  ]
}
Response examples (400)
{
  "error_message": "string"
}
Response examples (403)
{
  "error_message": "string"
}
Response examples (409)
{
  "error_message": "string"
}
Response examples (502)
{
  "error_message": "string"
}