Sign in
integrations

Connect Notion with an internal integration token

Connect a Notion workspace using a customer-created internal integration token (no OAuth).

post/v1/integrations/notion/connect

Request body

access_tokenstring required

Notion internal integration token (ntn_… or secret_…)

store_namestring nullable

Ingestion store name. A store that already exists is shared: every data source connected to it ingests into it, except another installation of the same account, which would ingest every item again. Without it, the account's default store, numbered past a store another installation of the account feeds. Rejected with 422 when the connect refreshes an existing installation and names a store other than its own.

new_storeboolean

Ingest into a store created for this connection: the connect fails with 409 when store_name names a store that already exists, and without store_name the default name is numbered past existing stores. Rejected with 422 when the connect refreshes an existing installation, which keeps its store.

Response

The connected Notion installation

Changes

Changed in 4 of the 30 revisions of this API.55

  • 9c6c72afde2d1See the full diff
    • ○

      added the new optional request property

      new-optional-request-property

  • b12f43c90ba32See the full diff
    • ●

      added the new bucket_unavailable_error enum value to the / response property for the response status

      response-property-enum-value-added

    • ●

      added the new bucket_unavailable_error enum value to the / response property for the response status

      response-property-enum-value-added

  • 957bf8ec8df82See the full diff
    • ●

      added the new store_frozen_error enum value to the / response property for the response status

      response-property-enum-value-added

    • ●

      added the new store_frozen_error enum value to the / response property for the response status

      response-property-enum-value-added

  • adde8ecfa74f14See the full diff
    • ●

      removed the optional property from the response with the status

      response-optional-property-removed

    • ○

      added the non-success response with the status

      response-non-success-status-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog