# Consistent HTTP 500 Errors on Graph API (/images and /map\_features) Endpoints Since Nov 7

**URL:** <https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077>\
**Category:** Uncategorized\
**Created:** [November 11, 2025, 9:33pm UTC](https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077 "2025-11-11T21:33:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![knikel](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@knikel](https://forum.mapillary.com/u/knikel)\
**Post date:** [November 13, 2025, 4:11pm UTC](https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077/3 "2025-11-13T16:11:49Z")

</div>

@farhadsalemi1 : Albeit a bit cryptic, this error indicates a generic timeout. Likely there was too much data in the given bbox and serving it is causing a timeout. Very densely captured areas might timeout sometimes despite relatively small bounding boxes. As an alternative you might want to consider [GitHub - mapillary/mapillary-python-sdk: A Python 3 library built on the Mapillary API v4 to facilitate retrieving and working with Mapillary data.](https://github.com/mapillary/mapillary-python-sdk), especially for crawling larger areas. Hope this helps until we find a good middle ground between the timeout and bbox size values.

You can use it as such (assuming you pip installed it):

```python
"""
Getting image coordinates from a nearby set of coordinates
"""

import mapillary.interface as mly
import json

mly.set_access_token("FIXME")
data = mly.map_feature_points_in_bbox(bbox={
    'west': -110.247350,
    'south': 31.426442,
    'east': -110.238745,
    'north': 31.430443
})

file_name = "get_map_features_in_bbox_controller.json"
with open(file_name, mode="w") as f:
    json.dump(data, f, indent=4)

```

---

_[View the full topic](https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077)._