# Document metadata 500 error

**URL:** <http://forum.companieshouse.gov.uk/t/document-metadata-500-error/1909>\
**Category:** Uncategorized\
**Created:** [July 10, 2018, 7:01pm UTC](http://forum.companieshouse.gov.uk/t/document-metadata-500-error/1909 "2018-07-10T19:01:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![voracityemail](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/v/b77776/32.png) [@voracityemail](http://forum.companieshouse.gov.uk/u/voracityemail)\
**Post date:** [July 11, 2018, 2:18pm UTC](http://forum.companieshouse.gov.uk/t/document-metadata-500-error/1909/5 "2018-07-11T14:18:48Z")

</div>

> the endpoint as HTTP {not https}

Indeed you’re right, the documentation for both document endpoints says “http” (e.g. at [https://developer.companieshouse.gov.uk/document/docs/document/id/fetchDocumentMeta.html](https://developer.companieshouse.gov.uk/document/docs/document/id/fetchDocumentMeta.html)). I had just assumed https everywhere because the rest of the API states this and [the guidelines](https://developer.companieshouse.gov.uk/api/docs/index/gettingStarted/developerGuidelines.html) do:

> The API can only be accessed over TLS. We recommend using TLS 1.2.

Unfortunately the documentation has not been corrected / updated since it was created (AFAIK) and has some “features” of its own (as of last cursory look a month or so ago). I was surprised that http worked since this rather waters down the “security” of having an API key e.g. you’re sending this in the clear.

Don’t have time to investigate what’s happening with Python / Postman ATM plus I don’t use either. Do post if you find the solution as that’s always helpful.

---

_[View the full topic](http://forum.companieshouse.gov.uk/t/document-metadata-500-error/1909)._
