Retrieve a List of Page Statuses

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
GET /profiles/{profile_id}/page_status

Returns the record count and the date and location of the last record change for every form in the profile that the caller may view, in one call. Each item is the row GET .../pages/{page_id}/page_status returns for that form.

Fields and filters

Standard list grammar. Default fields are page_id, profile_id, row_count, last_modified_date and last_modified_location; id is also available. Filter on the form with fields=page_id(="790777") or a range such as fields=page_id(>"790000"). The default order is id descending.

limit defaults to and is capped at 100. Total-Count is the number of matching rows before limit and offset.

Row count

row_count is returned as stored. A negative value means the count is unknown; the stored value is not recomputed by this endpoint.

Which forms are listed

Only forms that belong to the profile or are shared into it, the same set GET .../pages/{page_id}/page_status answers for. A form with no status row is not listed.

  • Internal clients, COMPANY and SERVER users, and BASIC users with the form role see every such form.
  • BASIC users with the Record Assignment policy and no form role see the forms assigned to them for view or collect, directly, through a user group, through a page group, or through both.
  • Any other BASIC user gets 403.

HTTP status

  • 200 the list, possibly empty
  • 401 no valid bearer token
  • 403 another profile's profile_id and the caller is not a SERVER user, or a BASIC user with neither role
  • 404 unknown profile
  • 429 the endpoint rate limit was reached; this route shares the per-endpoint budget with the other page status routes

Reads may come from a read replica, so a just-written status can take a few seconds to show.

Headers

  • Authorization string

    e.g. Bearer {access_token}

Path parameters

  • profile_id string Required

    id of the profile

Query parameters

  • fields string

    fields to return and filters, e.g. page_id(="790777")

  • limit number

    maximum count of the page status list

  • offset number

    skip that many page statuses before beginning to return

Responses

  • 200 application/json

    OK

    Hide headers attribute Show headers attribute
    • Total-Count string

      number of rows that match the filter, ignoring limit and offset

    Hide response attributes Show response attributes object
    • id number

      id of the status row; returned only when asked for in fields

    • page_id number Required

      id of the form

    • profile_id number Required

      id of the profile the status is kept for

    • row_count number Required

      number of records on the form; negative when the count is unknown

    • last_modified_date string | null Required

      date of the last record change, RFC 3339 in UTC

    • last_modified_location string | null Required

      location of the last record change

  • 400 application/json

    Bad Request - limit or offset is not an integer.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 401

    Unauthorized - missing or invalid bearer token.

  • 403

    Forbidden - profile_id is not the caller's own profile (only SERVER users may name another profile), or the caller is a BASIC user with neither the form role nor the Record Assignment policy.

  • 404

    Not Found - the profile does not exist.

  • 429 application/json

    Too Many Requests - the per-server limit for this endpoint (apiEndpointLimits) was reached.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

GET /profiles/{profile_id}/page_status
curl \
 --request GET 'https://api.iformbuilder.com/exzact/api/v80/[servername]/profiles/self/page_status' \
 --header "Authorization: Bearer {access_token}"
Response examples (200)
[
  {
    "page_id": 790777,
    "profile_id": 123456,
    "row_count": 152,
    "last_modified_date": "2026-11-02T14:31:07+00:00",
    "last_modified_location": "40.7128,-74.0060"
  },
  {
    "page_id": 790765,
    "profile_id": 123456,
    "row_count": 0,
    "last_modified_date": "2026-10-15T09:12:44+00:00",
    "last_modified_location": ""
  }
]
Response examples (400)
{
  "error_message": "'limit' must be an integer"
}
Response examples (429)
{
  "error_message": "API rate limit exceeded"
}