# 403 Forbidden Error

**URL:** <http://forum.companieshouse.gov.uk/t/403-forbidden-error/8052>\
**Category:** API Issues\
**Created:** [June 13, 2024, 10:09am UTC](http://forum.companieshouse.gov.uk/t/403-forbidden-error/8052 "2024-06-13T10:09:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/b/97f17d/32.png) [@brian](http://forum.companieshouse.gov.uk/u/brian)\
**Post date:** [June 13, 2024, 10:09am UTC](http://forum.companieshouse.gov.uk/t/403-forbidden-error/8052/1 "2024-06-13T10:09:11Z")

</div>

Hi there

Since 2018, we have an application that accesses the Companies House API to pull data. It stopped working earlier this week, although nothing has changed at our end.

We keep getting:

403 Forbidden

Can you advise, if there are problems with the API service at the moment, and also confirm that our application is not being blocked.

Thanks

Brian

---

<div class="post-metadata">

**Author:** ![lisa.fairbairn](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/l/dec6dc/32.png) [@lisa.fairbairn](http://forum.companieshouse.gov.uk/u/lisa.fairbairn)\
**Post date:** [June 13, 2024, 12:40pm UTC](http://forum.companieshouse.gov.uk/t/403-forbidden-error/8052/2 "2024-06-13T12:40:30Z")

</div>

We’ve also been getting 403 forbidden intermittently over the last week.

We’ve inspected the response logs and `200` responses have a server header with the value `CompaniesHouse` but the `403` responses have a server header with the value `awselb/2.0`

Nothing has changed at our end.

---

<div class="post-metadata">

**Author:** ![brian](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/b/97f17d/32.png) [@brian](http://forum.companieshouse.gov.uk/u/brian)\
**Post date:** [June 13, 2024, 1:52pm UTC](http://forum.companieshouse.gov.uk/t/403-forbidden-error/8052/3 "2024-06-13T13:52:14Z")

</div>

Interestingly, since I reported this earlier today, it started working for us, and we have not had any more 403 errors.
