Issue Description
Recently, Vercel + NotionNext users may encounter deployment issues:
- Clicking
Deployresults in an error, failing to complete deployment.
- Checking Build Logs reveals that requests to
https://www.notion.so/api/v3return 530 errors, preventing the site from loading content properly.
🚀 Affected Scope:
- All NotionNext sites deployed on Vercel (relying on Notion API).
- API failures cause blogs to display errors like
530,403, orFailed to fetch.
📝 Fix NotionNext Deployment Failure: Notion API 530 Error & Temporary Solution
💻 Error Logs & Screenshots
1. Vercel Deployment Error Screenshot
2. Browser Console Errors
When opening the site in a browser, the
Console may display:or:
🛠️ Solution
Root Cause
The official Notion API domain
https://www.notion.so/api/v3 may be rate-limited or experiencing DNS issues, causing failed requests. Temporary workaround: Use a custom Notion personal API domain instead of the official API.✅ Temporary Fix Steps
1. Obtain Your Notion Personal API Domain
- Open your shared Notion page (make sure it's publicly accessible).
- Copy the URL from your browser’s address bar (format below):
(Example:
https://alice.notion.site/My-Blog-1234567890abcdef)
2. Construct the API URL
Extract your custom domain (
https://[your-name].notion.site), then append /api/v3, e.g.:3. Configure Vercel Environment Variable
- Go to Vercel project →
Settings→Environment Variables
- Add a new variable:
- Save and redeploy.
4. (Optional) Local Testing
If running the project locally, add this to
local.env:Then restart the project.
📌 Additional Notes
- ⚠️ Do NOT share the same API URL—traffic overload may lead to blocking!
- 🚀 After Notion Recovers: Remove
API_BASE_URLto fall back to the official API.
- 💡 Ensure NotionNext is updated, as older versions may not support this variable.
🔗 References
🎉 Expected Result
After redeploying, your site should load Notion data normally!
If issues persist, feel free to comment below! 🚀
