Access token that a third-party service can use to authenticate with Notion

A unique random code that Notion generates to authenticate with your service, generated when a user initiates the OAuth flow

The 'redirect_uri' that was provided in the OAuth Domain & URI section of the integration's Authorization settings

block_id

Set to true to delete a block. Set to false to restore a block.

Supply cursor for next page when available.

start_cursor

page_size

The ID of the existing block that the new block should be appended after

Child content to append to a container block as an array of block objects

Return subsequent page results after provided cursor

A UUID identifier for a discussion thread. Either this or a parent object is required (not both)

A page parent. Either this or a discussion_id is required (not both)

This API is used for creating new database, parent is always a page and has `page_id`.

To create the database `properties` is required,

API also support `title`, `description`, `icon`, `cover`


Property schema of database. The keys are the names of properties as they appear in Notion and the values are property schema objects.

Title of database as it appears in Notion. An array of rich text objects.

This API is used for updating `title`, `description` and `properties` of the database, new property can be added, existing property can be updated or removed.


To update the row, use the page update API.

database_id

An array of rich text objects that represents the description of the database that is displayed in the Notion UI. If omitted then the database description remains unchanged.

The properties of a database to be changed in the request in the form of a JSON object. If updating an existing property then the keys are the names or IDs of the properties as they appear in Notion and the values are property schema objects. If adding a new property then the key is the name of the new database property and the value is a property schema object.

An array of rich text objects that represents the title of the database that is displayed in the Notion UI. If omitted then the database title remains unchanged.

This API only retrieve a database info such as title, description and it's properties (column details), doesn't return the row data.


To retrieve the rows (data) of the database, use the database query api

Retrieve database detail and it's properties

This API is used for retrieving the rows (data) of the database, using `database_id` and query filter to match the records.

Filter response by specific page property IDs.

filter_properties

When supplied limits which pages are returned based on the filter conditions.

The number of items from the full list desired in the response. Maximum - 100

When supplied orders the results based on the provided sort criteria.

When supplied returns a page of results starting after the cursor provided. If not supplied this endpoint will return the first page of results.

Fetch rows of the Notion database using query

Create new page inside a page or a database.

**Note**: Notion API doesn't allow creating a root level page inside a workspace. Page can only be created inside another page or database.

### Create a page where parent is also a page:

When a new page is created inside a page, only `title` property is required.

### Create a page where parent is a database:

Whereas when a new page is created inside a database, page properties are interited from the database properties.

While creating a new page, other fields like `icon`, `cover` or `children` can also be used.

`icon` field is used for setting icon in a page, either we can set emoji or add our own image.

`cover` field is used for setting cover in page. 

`children` field is used for adding content inside the page, represented using array of block objects.

___

This API can take 10 different variation of payload for creating a page.

Page content for the new page as an array of block objects

Property values of this page. The keys are the names or IDs of the property and the values are property values

Create a new page inside page or a database

This API only updates the page properties, icon and cover.

The properties can only be update if the page belongs to database.

Archieve or unarchive the page using `archived:true` or `archived:false`

To update page **content**, use the blocks object endpoints.

page_id

Whether the page is archived (deleted). Set to true to archive a page. Set to false to un-archive (restore) a page.

Update page properties including cover and icon

This API retrieve the page properties and other information. 

If the page belongs to database, it will return all the properties linked to the parent database.

If the page belongs to other page, only title property will be returned.

To retrieve the page content use blocks API, where `block_id` will be the `page_id`

Limit response to specific page property values

Retrieve a page properties and other information

property_id

When supplied filters the results based on the provided criteria.

The number of items from the full list desired in the response. Maximum - 100.

When supplied limits which pages are returned by comparing the query to the page title.

When supplied sorts the results based on the provided criteria. Limitation

If supplied this endpoint will return a page of results starting after the cursor provided. If not supplied this endpoint will return the first page of results.

user_id

Filter response by specific page property IDs

Notion

Pre-configured, Predictable, Single Interface, Ready-to-use, Opinionated & Managed API Explorer & Server - LowCodeAPI

Pre-configured, Predictable, Single Interface, Ready-to-use, Opinionated & Managed API Explorer & Server. Bring your API credentials, configure and access your 3rd party APIs. Using LowCodeAPI securely manage all integrations in one place.

LowCodeAPI

Featured

OpenAI

Google Sheets

Google Docs

Gmail

gmail

Unsplash

UnsplashAPI

Name.com

Name.com API

Cal API

Trello

Trello API

Telegram

Telegram API

The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.