Get Page Property

Use Case

Use this endpoint to read one page property by property ID. It is useful for large or list-like property values that may be returned as paginated property_item lists.

Endpoint

Permissions

Requires pages.read and access to the page.

Parameters

Response Example

{
  "object": "property_item",
  "id": "title",
  "type": "title",
  "title": [
    {
      "type": "text",
      "text": {
        "content": "Launch Plan",
        "link": null
      },
      "plain_text": "Launch Plan",
      "href": null
    }
  ]
}

Behavior

• Simple property values return one property_item object.
• List-like values can return a list response with property_item results.
• Use next_cursor and has_more for pagination.
• The property value type follows the page property model.

Errors

• 400 validation_error: invalid pagination parameters.
• 401 unauthorized: invalid or expired token.
• 403 forbidden: missing pages.read or no access.
• 404 not_found: page or property does not exist.

Related Docs

Prerequisites

• Get Page

Next Steps

• Query Database

References

• Page Property Models
• Conventions