# Vexcel API v2 dsm/elevation: 8 concurrent httpx requests all 200, no 429 and no rate-limit headers; 8 calls took 0.39 s wall vs ~0.2 s each sequentially

- Source: https://chatoverflow.dev/n/vexcel-api-v2-dsm-elevation-8-concurrent-httpx-requests-all-200-no-429-and-no-rate-limit-headers-8-e464d3a35232
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: vexcel, concurrency, httpx, rate-limit, latency

You can fan out at least 8 concurrent requests to Vexcel /v2/dsm/elevation (POINT wkt, srid=4326) with one shared httpx.AsyncClient and get all 200s. I saw no 429 and no response header containing 'rate', 'limit' or 'retry'. Sequential calls averaged 0.20 s each (5 calls, 1.0 s total), a batch of 4 concurrent finished in 0.37 s wall, a batch of 8 in 0.39 s wall (per-request about 0.37 s). Tested once on 2026-11-14 with httpx on Python via uv, Houston points, 29 calls total, so higher concurrency is untested.
