Returns the effective access of the user who owns the bearer token to one page, with subform inheritance applied. It answers the same question as the record endpoints' permission checks, so a client can decide whether to offer a form or subform without walking the subform tree itself.
The user is always the token's user. self is a literal path segment; there is no form of this endpoint that takes a user id.
Fields
can_viewistruewhen the user holds view permission on the page through any assignment path (direct, user group, page group, or user group to page group), or inherits it from a form the page is a subform of. This is the page-level part of the check behindGET .../records/{record_id}; record assignments are not considered.can_collectis the same with collect permission. It is the page-level part of the check behindPOST .../records. It does not report edit or delete rights a BASIC user holds through view permission plus theEDIT_RECORDorDEL_RECORDrole (the second path in thePUTandDELETE .../recordschecks), socan_collect: falsedoes not mean the user cannot edit or delete records on the page.
Inheritance
Subforms are never assigned directly, so a subform's access comes from its parent forms. The walk goes up through subform elements in the same profile, at most 10 levels. A form shared into the profile does not pass its access down to its subforms.
can_collect: true through inheritance is a page-level answer. A record write is still checked against the parent form of each record it touches, so where one subform is used by two forms, a user assigned to only one of them may still get 403 writing records that belong to the other.
COMPANY and SERVER users
Users with company or server scope get true for both fields on any page they can reach in the profile, as the record endpoints treat them.
HTTP status
200the page exists in the profile; both fields may befalse401no valid bearer token403another profile'sprofile_idand the caller is not a SERVER user404unknown profile, invalidpage_id, or the page is not in the profile429the endpoint rate limit was reached
Rate limiting and freshness
The rate limit is per server per endpoint (apiEndpointLimits), shared by every caller on the server. A backend that calls this endpoint for many users, such as a portal BFF gating each form route, should use an internal client or ask for a raised limit rather than spend the shared budget.
Reads may come from a read replica, so a just-changed assignment can take a few seconds to show.
Responses
-
OK
-
Unauthorized - missing or invalid bearer token.
-
Forbidden -
profile_idis not the caller's own profile (only SERVER users may name another profile). -
Not Found - the profile does not exist,
page_idis not a positive integer, or the page neither belongs to nor is shared intoprofile_id. -
Too Many Requests - the per-server limit for this endpoint (
apiEndpointLimits) was reached.
curl \
--request GET 'https://api.iformbuilder.com/exzact/api/v81/[servername]/profiles/self/users/self/page_access/{page_id}' \
--header "Authorization: Bearer {access_token}"
{
"page_id": 790777,
"can_view": true,
"can_collect": false
}
{
"error_message": "API rate limit exceeded"
}