---
title: "Troubleshooting API access and permission errors"
slug: "troubleshooting-api-access-and-permission-errors"
updated: 2026-07-27T04:33:25Z
published: 2026-07-27T04:33:25Z
canonical: "docs.document360.com/troubleshooting-api-access-and-permission-errors"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting API access and permission errors

### 400 error – API access is disabled

**Error message:** *"400 error – API access is disabled. Please contact your project administrator."*

**When it occurs:** When attempting to use the public API and public API access has been deactivated in the project settings.

**How to fix it:**

1. Navigate to **Settings** (⚙️) > **AI settings** > **Eddy AI settings** in the Knowledge base portal.
2. Under the **AI search suite** section, ensure that the **Public API** checkbox is selected.  

![Eddy AI settings page showing options for AI writer and assistive search features.](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Screenshot-Public_API_settings.png)
3. If the issue persists, contact the Document360 support team.

---

### 403 error when posting via API endpoint

**When it occurs:** When attempting a POST request through the API endpoint and receiving a 403 response.

**Why it happens:** The API token being used does not have the required permissions to make POST requests.

**How to fix it:** Review the permissions assigned to your API token. Ensure it has write and POST permissions enabled. Update the token settings and retry.

> A 403 error when updating content via the API can also occur if you attempt to modify spec-generated content (endpoint articles generated from an OpenAPI/Swagger file). Spec-generated content cannot be retrieved or updated through regular content API endpoints, regardless of your API token's permissions. To update this type of content, update your API specification file and resync the documentation instead. See [Managing API references](/help/docs/manage-api-references) for details. If the content you are updating is a regular knowledge base article (not generated from a spec), verify your API token's permissions as described above.