API Bearer Auth vs WP Sync for Notion – Notion to WordPress

The API Bearer Auth plugin enables authentication for the REST API by using JWT access an refresh tokens. After the user logs in, the access and refresh tokens are returned and can be used for the next requests. Issued tokens can be revoked from within the users admin screen. See below for the endpoints. Note that after activating this plugin, all REST API endpoints will need to be authenticated, unless the endpoint is whitelisted in the api_bearer_auth_unauthenticated_urls filter (see FAQ for how to use this filter). JWT Access tokens can be formatted as JWT tokens. For this to work, you first have to create a secret and add it to the wp-config.php file. If you don’t do this, access tokens will work also, but are just random strings. To create a random secret key, you can do for example: base64_encode(openssl_random_pseudo_bytes(64)); And then add the result to wp-config: define('API_BEARER_JWT_SECRET', 'mysecretkey'); If you have problems, you can verify your JWT tokens at: https://jwt.io/ Revoke tokens This plugin adds a column to the users table in de admin where you can see when a token expires. You can also revoke tokens by selection the “Revoke API tokens” from the bulk actions select box. API endpoints Note that all endpoints expect JSON in the POST body. Login Endpoint: POST /api-bearer-auth/v1/login Request body: Note: client_name is optional. But if you use it, make sure to use it as well for the refresh call! {"username": "my_username", "password": "my_password", "client_name": "my_app"} Response: { "wp_user": { "data": { "ID": 1, "user_login": "your_user_login", // other default WordPress user fields } }, "access_token": "your_access_token", "expires_in": 86400, // number of seconds "refresh_token": "your_refresh_token" } Make sure to save the access and refresh token! Refresh access token Endpoint: POST /api-bearer-auth/v1/tokens/refresh Request body: Note: client_name is optional. But if you did use it for the login call, make sure to use it here as well! {"token": "your_refresh_token", "client_name": "my_app"} Response success: { "access_token": "your_new_access_token", "expires_in": 86400 } Response when sending a wrong refresh token is a 401: { "code": "api_api_bearer_auth_error_invalid_token", "message": "Invalid token.", "data": { "status": 401 } } Do a request After you have the access token, you can make requests to authenticated endpoints with an Authorization header like this: Authorization: Bearer Note that Apache sometimes strips out the Authorization header. If this is the case, make sure to add this to the .htaccess file: RewriteCond %{HTTP:Authorization} ^(.*) # Don't know why, but some need the line below instead of the RewriteRule line # SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0 RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1] If you are not logged in or you send an invalid access token, you get a 401 response: { "code": "api_bearer_auth_not_logged_in", "message": "You are not logged in.", "data": { "status": 401 } } Important update Update immediately if you’re using a version below 20200807. Before this version all access tokens were updated when calling the refresh callback. If you are affected by this the fastest solution is to execute this query: update wp_user_tokens set access_token_valid = NOW(); This will invalidate all access tokens. This means that all users need to refresh their access token and will get a new access token and a unique one this time. A big thank to @harchvertelol for reporting this and suggesting the fix as well!

With our Notion to WordPress integration, WP Sync for Notion, you can publish content from Notion directly to your WordPress website and keep your pages in sync without Zapier or Make. The free version allows you to synchronize Notion pages to WordPress with their content and structure preserved. For advanced use cases, Notion WP Sync Pro+ unlocks powerful features such as database synchronization, field mapping, Custom Post Types, Advanced Custom Fields (ACF) support, and SEO integrations — ideal for professional and content-driven websites. Learn more and compare features with the Notion WP Sync Pro+ version. Features Connect Notion pages Sync Notion pages to WordPress Keep page content and supported blocks in sync Manual or automatic synchronization Connect Notion databases (Pro+ only) Sync structured Notion databases to WordPress Map Notion database properties to WordPress fields Create content from databases instead of static pages Set up and publish unlimited connections Database synchronization and property mapping are available in the Pro+ version. Display Notion content in WordPress Publish content as Posts or Pages Display content in Custom Post Types (Pro+) Assign Post Status and Author (Pro+) Advanced Custom Fields (ACF) support (Pro+) These features make Pro+ ideal for headless CMS and editorial workflows. See Pro+ features. Keep your Notion design or customize it Supports most Notion blocks (text, lists, tables, images, columns…) Display content via Gutenberg block Use shortcodes with Elementor, Divi or any page builder (Pro+) Dedicated “Notion Content” Custom Post Type (Pro+ only) Advanced synchronization & automation Manual or automatic synchronization Webhook-triggered synchronization (Pro+) Control sync behavior (add / update / delete) Designed for large-scale content imports (Pro+) Advanced automation and scalability are available in the Pro+ version. How to unleash your plugin’s full potential? WP Sync for Notion works great for syncing pages, but the Pro+ version unlocks its full power for professional use cases. With Pro+, you can: * Sync Notion databases instead of only pages * Map database properties to WordPress fields * Use Custom Post Types and Advanced Custom Fields * Improve SEO with Yoast and upcoming SEO integrations * Handle large imports and complex content structures Compare Free and Pro+ features on the official comparison page. External services This plugin connects to the Notion API to synchronize content into WordPress. Service endpoint: https://api.notion.com What is sent and when: When a connection is created, edited, or tested: the Notion integration token (API key) and the requested page or database ID are sent to the Notion API to retrieve metadata. On each manual or scheduled sync: the Notion integration token, the requested page/database IDs, and any configured query parameters (filters, pagination cursors) are sent to the Notion API. The API returns the page or database content (titles, properties, blocks) which is then stored in WordPress. Notion Terms of Service: https://www.notion.so/notion/Terms-and-Privacy-28ffdd083dc3473e9c2da6ec011b58ac Notion Privacy Policy: https://www.notion.so/notion/Privacy-Policy-3468d120cf614d4c9014c09f6adc9091 Troubleshooting If you don’t see your pages, make sure they are shared with your Notion integration. If needed, logs are available via FTP in the following folder: /wp-content/uploads/notionwpsync-logs Support Open a ticket via the WordPress support forum