Fix Notion ‘API Request Failed’ on Specific Database Property Type

When you try to update or view a Notion database property, the error API Request Failed appears. This error often targets a specific property type such as a Relation, Rollup, Formula, or Select field. The root cause is usually a corrupted property configuration, a broken relation between databases, or an incompatible formula that causes the Notion API to time out or reject the request. This article explains why the error occurs only on certain property types and provides step-by-step fixes to resolve it.

Why the API Request Failed Error Targets Specific Property Types

Notion stores each database property as a separate object in its internal data model. When a property becomes corrupted, the API call to read or write that property fails. The corruption can happen in several ways:

Corrupted Relation or Rollup Properties

A Relation property links two databases. If the target database is deleted, renamed, or moved to a different workspace, the relation breaks. Notion’s API cannot resolve the link and returns an error. Rollup properties inherit data from a relation; if the relation is broken, the rollup also fails.

Formula Properties with Invalid Expressions

A Formula property uses Notion’s formula language. If you write an expression that references a deleted property, uses an incorrect function name, or creates a circular reference, the API cannot evaluate the formula. The error appears only when the formula is calculated, not when other properties are loaded.

Select and Multi-Select Properties with Duplicate Options

If you import or sync data that creates duplicate option names in a Select or Multi-Select property, Notion can become confused. The API sees two options with the same name but different IDs and cannot process the column. This is rare but happens when using third-party integrations like Zapier or Make.

Steps to Fix the API Request Failed Error on a Specific Property

Before you start, back up your database. Export the entire database as CSV or Markdown. Go to the top-right menu of the database, select Export, and save the file to your computer.

Method 1: Duplicate the Database

1. Open the database page
   Navigate to the database that shows the error. Click the three-dot menu at the top-right corner of the page.
2. Select Duplicate
   From the menu, choose Duplicate. Notion creates a copy of the entire database in the same workspace.
3. Test the duplicate database
   Open the duplicated database and try to view or edit the property that previously failed. If the error no longer appears, the original database had a corrupted property configuration. Delete the original database and use the duplicate.

Method 2: Delete and Recreate the Problematic Property

1. Identify the failing property
   Scroll through the database properties until you find the one that triggers the API Request Failed error. Note the property name and type.
2. Delete the property
   Click the property header, then select Delete property. Confirm the deletion. All data in that column is removed.
3. Recreate the property
   Click the + Add a property button at the rightmost column of the database. Select the same property type (Text, Select, Relation, etc.). Name it exactly as before if you want to keep consistency.
4. Re-enter data if needed
   If you deleted a property with important data, you must re-enter it manually or paste it from your backup CSV.

Method 3: Fix a Broken Relation Property

1. Check the linked database
   Click the Relation property header. Look at the linked database name. If the name appears in gray or shows a broken link icon, the target database is missing.
2. Restore or reconnect the linked database
   If the target database was deleted, restore it from the Notion trash (click the workspace name, then Trash). If it was moved, move it back to the original workspace location. If it still exists, click Edit property and select the correct database from the list.
3. Refresh the Rollup property
   If the error is on a Rollup property, after fixing the Relation, click the Rollup header, select Edit property, and re-select the relation and the property to roll up. The API request should now succeed.

Method 4: Simplify a Formula Property

1. Open the formula editor
   Click the Formula property header, then select Edit property. The formula editor appears.
2. Test the formula in parts
   Copy the formula to a text editor. Delete the entire formula from Notion and save. The API error should stop. Then rebuild the formula piece by piece, saving after each addition. When the error returns, you have found the problematic expression.
3. Replace problematic functions
   Common functions that cause errors include prop() referencing a deleted property, format() with a date that doesn’t exist, or concat() with a very long string. Replace or remove the offending function.

If Notion Still Shows the API Request Failed Error

The error appears on every property in the database

If the error is not limited to one property, the entire database may be corrupted. Duplicate the database as described in Method 1. If duplication also fails, export the database as CSV, create a new blank database, and import the CSV. You lose database-specific features like Relations and Rollups, but you preserve the data.

The error appears only in a specific view

A broken view filter or sort can trigger the error. Click the view name at the top of the database, select Edit view, and remove all filters and sorts. If the error disappears, re-add filters one at a time until you find the problematic one. Delete that filter and create a new one.

The error appears after a third-party integration syncs data

Integrations like Zapier, Make, or Notion API scripts can introduce malformed data. Go to Settings & Members > Connections and disconnect the integration. Then manually correct the data in the affected property. Reconnect the integration only after the error is resolved.

Notion Property Types and Their Common Failure Points Compared

Property Type	Common Failure Cause	Best Fix Method
Relation	Target database deleted or moved	Restore target or reconnect relation
Rollup	Broken relation or missing source property	Fix relation then re-create rollup
Formula	Invalid expression or circular reference	Simplify formula step by step
Select / Multi-Select	Duplicate option names from imports	Delete and re-add options manually
Text / Number / Date	Rarely causes API errors alone	Duplicate database if error persists

The table shows that Relation and Rollup properties are the most common sources of the API Request Failed error. Formula properties are next. Simple text and number properties rarely cause API failures.

Now you can identify which property type triggers the error and apply the correct fix. Start by duplicating the database to preserve your data. Then delete and recreate the broken property. For Relation properties, verify that the linked database still exists. For Formula properties, rebuild the expression piece by piece. If the error persists, disconnect any third-party integrations that sync data into that property.