notion-api 0.3.12

An unofficial wrapper for Notion's API, aiming to simplify the dynamic nature of interacting with Notion.

notion-api

         

   

Disclaimer: This is an unofficial package and has no affiliation with Notion.so

A few useful links:

API Reference

Notion API Changelog

Notion.so Releases

Notion Platform Roadmap

A wrapper for Notion's API, aiming to simplify the dynamic nature of interacting with Notion.

This project is still a work in progress, and features will continue to change. Below are a few examples of the current functionality.

Install

pip install -U notion-api

Usage

import dotenv

import notion

dotenv.load_dotenv()  # client will check for env variable 'NOTION_TOKEN'.

homepage = notion.Page('773b08ff38b44521b44b115827e850f2')
parent_db = notion.Database(homepage.parent_id)

# or assign through `token` parameter.
homepage = notion.Page('773b08ff38b44521b44b115827e850f2', token="secret_n2m52d1***")


# __get_item__ searchs for page property values if indexing a Page..
homepage['dependencies']
# {
#     "id": "WYYq",
#     "type": "relation",
#     "relation": [
#         {
#             "id": "7bcbc8e6-e237-434b-bd0d-6b56e044200b"
#         }
#     ],
#     "has_more": false
# }

# ..and searchs for property objects if indexing a Database.
parent_db['dependencies']
# {
#     "id": "WYYq",
#     "name": "dependencies",
#     "type": "relation",
#     "relation": {
#         "database_id": "f5984a7e-2257-4ab0-9d0a-23ea12324031",
#         "type": "dual_property",
#         "dual_property": {
#             "synced_property_name": "blocked",
#             "synced_property_id": "wx%7DQ"
#         }
#     }
# }

homepage.last_edited.date() # out: 01/15/2023
homepage.title = "New Page Title"

---

Creating Pages/Databases/Blocks

The current version of the Notion api does not allow pages to be created to the parent workspace. Create objects by passing an existing Page/Database instance as an arg to the create classmethods.

new_database = notion.Database.create(
    homepage, database_title="A new database", name_column="name"
) 
# name column refers to the column containing pages/page titles. 
# Defaults to "Name" if None (all strings in Notion API are case-sensitive).

new_page = notion.Page.create(new_database, page_title="A new database row")

Blocks can be created with notion.api.blocktypefactory.BlockFactory by appending to an exisiting Block or Page. The new block is always returned as a notion.api.notionblock.Block instance.

from notion import properties as prop

# `new_synced_block` refers to the original synced block in the Notion UI.
original_synced_block = notion.BlockFactory.new_synced_block(homepage)

# Adding content to the synced block
notion.BlockFactory.paragraph(
    original_synced_block, [prop.RichText("This is a synced block.")]
)
# Referencing the synced block in a new page.
notion.BlockFactory.reference_synced_block(new_page, original_synced_block.id)

Example Workflows

Appending blocks to a page as a reminder.

def in_block_reminder(page: notion.Page, message: str, user_name: str) -> None:
    mentionblock = notion.BlockFactory.paragraph(
        page,
        [
            prop.Mention.user(
                notion.Workspace().retrieve_user(user_name=user_name),
                annotations=prop.Annotations(
                    code=True, bold=True, color=prop.BlockColor.purple
                ),
            ),
            prop.RichText(" - "),
            prop.Mention.date(
                datetime.now().astimezone(target_page.tz).isoformat(),
                annotations=prop.Annotations(
                    code=True, bold=True, color=prop.BlockColor.purple_background
                ),
            ),
            prop.RichText(":"),
        ],
    )
    # First method returned the newly created block that we append to here:
    notion.BlockFactory.paragraph(mentionblock, [prop.RichText(message)])
    notion.BlockFactory.divider(page)

>>> my_page = notion.Page("0b9eccfa890e4c3390175ee10c664a35")
>>> in_block_reminder(page=my_page, message="message here", user_name="Your Name")

Cloud Function on GCP: Create daily pages & set related property values.

import os
from datetime import datetime

import functions_framework
import notion

# Set NOTION_TOKEN and database ID's as env variables.

@functions_framework.http
def main(request) -> str:
    # Setup databases.
    DATABASE_A1 = notion.Database(os.environ["DATABASE_A1_ID"])
    DATABASE_B1 = notion.Database(os.environ["DATABASE_B1_ID"])
    DATABASE_B2 = notion.Database(os.environ["DATABASE_B2_ID"])

    date = str(datetime.today().astimezone(DATABASE_A.tz).date())

    # Create a page in main database.
    page_A1 = notion.Page.create(DATABASE_A1, page_title=date)

    # Create a page in a 2nd database and relate it to main.
    page_B1 = notion.Page.create(DATABASE_B1, page_title=date)
    page_A1.set_related("related-B1", [page_B1.id])

    # Create a page in a 3rd database and relate it to the 2nd.
    page_B2 = notion.Page.create(DATABASE_B2, page_title=date)
    page_B1.set_related("related-B2", [page_B2.id])

    return "Done"

---

Add, Set, & Delete - Page property values / Database property objects

The first argument for all database column methods is the name of the property,
If it does not exist, then a new property object is created.
If it already exists, then the method will overwrite it.

If the name passed already exists, but it's a different column type than the method used - then the API will overwrite this and change the property object to the new column type.
The original parameters will be saved if you decide to switch back (i.e. if you change a formula column to a select column, upon changing it back to a formula column, the original formula expression will still be there).

new_database.formula_column("page id", expression="id()")

new_database.delete_property("url")

new_database.multiselect_column(
    "new options column",
    options=[
        prop.Option("option-a", prop.PropertyColor.red),
        prop.Option("option-b", prop.PropertyColor.green),
        prop.Option("option-c", prop.PropertyColor.blue),
    ],
)

# if an option does not already exist, a new one will be created with a random color.
# this is not true for `status` column types, which can only be edited via UI.

new_page.set_multiselect("options", ["option-a", "option-b"])

---

Database Queries

A single notion.query.propfilter.PropertyFilter is equivalent to filtering one property type in Notion. To build filters equivalent to Notion's 'advanced filters', use notion.query.compound.CompoundFilter.

from datetime import datetime
from datetime import timedelta

from notion import query

TODAY = datetime.combine(datetime.today(), datetime.min.time())
TOMORROW = TODAY + timedelta(1)

query_filter = query.CompoundFilter()._and(
    query.PropertyFilter.date("date", "created_time", "on_or_after", TODAY.isoformat()),
    query.PropertyFilter.date("date", "created_time", "before", TOMORROW.isoformat()),
    query.CompoundFilter()._or(
        query.PropertyFilter.text("name", "title", "contains", "your page title"),
        query.PropertyFilter.text("name", "title", "contains", "your other page title"),
    ),
)

query_sort = query.SortFilter(
    [
        query.PropertyValueSort.ascending("your property name"),
        query.EntryTimestampSort.created_time_descending(),
    ]
)

query_result = new_database.query(
    filter=query_filter,
    sort=query_sort,
    page_size=5,
    filter_property_values=["name", "options"],
)

---

Exceptions & Validating Responses

# Errors in Notion requests return an object with the keys: 'object', 'status', 'code', and 'message'

homepage._patch_properties(payload={'an_incorrect_key':'value'})
# Example error object for line above..
# {
#   'object': 'error', 
#   'status': 400, 
#   'code': 'validation_error', 
#   'message': 'body failed validation: body.an_incorrect_key should be not present, instead was `"value"`.'
# }

Traceback (most recent call last):
File "c:\path\to\file\_.py", line 6, in <module>
    homepage._patch_properties(payload={'an_incorrect_key':'value'})
File "c:\...\notion\exceptions\validate.py", line 48, in validate_response
    raise NotionValidationError(message)
notion.exceptions.errors.NotionValidationError: body failed validation: body.an_incorrect_key should be not present, instead was `"value"`.
Error 400: The request body does not match the schema for the expected parameters.

A common error to look out for is notion.exceptions.errors.NotionObjectNotFound

This error is often raised because your bot has not been added as a connection to the page.

By default, a bot will have access to the children of any Parent object it has access too.

Certain errors are returned with a long list of possible causes for failing validation, In these cases, the error is often the outlier in the list - for example:

---