# API update release date question for trailing / bug fix

**URL:** <http://forum.companieshouse.gov.uk/t/api-update-release-date-question-for-trailing-bug-fix/8472>\
**Category:** API Question\
**Created:** [September 17, 2024, 12:17pm UTC](http://forum.companieshouse.gov.uk/t/api-update-release-date-question-for-trailing-bug-fix/8472 "2024-09-17T12:17:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tommy](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/t/b5a626/32.png) [@tommy](http://forum.companieshouse.gov.uk/u/tommy)\
**Post date:** [September 17, 2024, 12:17pm UTC](http://forum.companieshouse.gov.uk/t/api-update-release-date-question-for-trailing-bug-fix/8472/1 "2024-09-17T12:17:46Z")

</div>

So my company does bi-weekly releases every Tuesday. We have done one today(17/09/2024), with the last being on the 03/09/2024.

We had one bug appear today where if you do a request as such:  
[https://api.company-information.service.gov.uk/company/123122312/](https://api.company-information.service.gov.uk/company/123122312/)

Companies house returns a 500 status code. The fix is to remove the trailing / so  
[https://api.company-information.service.gov.uk/company/123122312](https://api.company-information.service.gov.uk/company/123122312)

This is fine, and an oversight by us however we are trying to ascertain when exactly this change occurred from Companies House. Looking at the API changes category I can’t find anything in the last 2 weeks (as I assume this is a minor bug). Would someone be able to provide us with a better estimate of when this update occurred in the last 2 weeks?

---

<div class="post-metadata">

**Author:** ![manderson](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/m/e47774/32.png) [@manderson](http://forum.companieshouse.gov.uk/u/manderson)\
**Post date:** [September 17, 2024, 2:14pm UTC](http://forum.companieshouse.gov.uk/t/api-update-release-date-question-for-trailing-bug-fix/8472/2 "2024-09-17T14:14:00Z")

</div>

Looks like trailing ‘/’ works ok on some endpoints (psc, charges) , whilst breaking others (company, officers)
