Skip to content

Company read only

HTTP 403company_read_only

When the API answers 403 company_read_only, and how to fix it.

Version v1.1, updated

The type field of every company_read_only response links to this page.

On this page

The company account is read only. Reads keep working, but no write is accepted until the account allows changes again.

At a glance

  • Status: 403 Forbidden

  • Code: company_read_only

  • Retry: Not until the account allows changes again.

Causes and fixes

Likely cause

How to fix it

The company account is read only.

A company administrator contacts BIRP support about the account.

Keep the writes you could not send, with their idempotency keys, and send them again once the account allows changes.

Example

403 company_read_onlyJSON
{
  "code": "company_read_only",
  "detail": "The company account is read only: data can be read but not changed.",
  "instance": "/v1/categories",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 403,
  "title": "Company read only",
  "type": "https://birp.io/developers/errors/company_read_only"
}

Related

  • company-suspended
  • company-inactive
  • handling-errors