Notion

PASS consensus from 3 PASS.

The quickstart covers PAT creation and a parentless POST /v1/pages request on one page. The quickstart runs token creation to a created page in two steps, and the POST /v1/pages example needs no parent and no properties object because the markdown field supplies the title. One clear path from PAT creation in the Developer portal through env-var setup to a curl or SDK request that creates a workspace-private page.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The page gives exact per-connection and listed size limits, but omits numeric shared-workspace and child-depth limits. Per-connection rates are exact by plan (600/min for Business and Enterprise, 180/min for all other plans) and the size limits are a complete table, but the per-workspace limit that can independently reject a compliant client is never given a number for any plan. Per-connection rate limits are exact by plan and size limits have exact character, element, and byte counts in a clear table.

PASS consensus from 3 PASS.

The response reason identifies the limit, and the retry sequence covers Retry-After, retry, backoff with jitter, and a retry cap. The page names the field that identifies which limit was hit, defines Retry-After as an integer number of seconds, gives a four-step recovery procedure with backoff, jitter and a retry cap, and ships working implementations in JavaScript, Python, Go and Java. Complete four-step recovery path documented with Retry-After header, rate_limit_reason to identify which limit was hit, exponential backoff, and retry limits.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The page completes setup and offers a correct SDK helper, but its manual snippets re-serialize parsed JSON before hashing. Subscription creation, the verification_token handshake and signature checking are all documented on one page, but the same page contradicts itself: the SDK tip warns that re-serialized JSON fails verification while the hand-rolled sample immediately below signs JSON.stringify(body) over a parsed object. Full end-to-end path: create subscription, receive verification_token, echo it back, compute HMAC-SHA256 on subsequent events to verify X-Notion-Signature, with sample validation code.

PASS consensus from 3 PASS.

The quickstart names @notionhq/client and gives REST and SDK create-page examples with matching icon and markdown bodies. The quickstart shows the curl, raw HTTP and @notionhq/client forms as tabs of one example, so notion.pages.create({ icon, markdown }) is visibly the same request body as the POST /v1/pages reference, which documents markdown as a body parameter. The Quickstart provides matching curl and JavaScript SDK examples using the same API parameters (icon, markdown). The SDK's notion.pages.create() maps to POST /v1/pages shown in the curl form.