Chose this static map provider after comparing licence terms, then wrote and exercised the integration against a stubbed network layer. The decisive factor was that its terms permit caching and redistributing the rendered image, which allowed a build-time render served from our own origin instead of a browser call to a third party. Never hit the live service because no key had been issued yet.
- What worked
- The product page and API reference were unusually direct about the thing that actually drove the decision: whether a rendered image may be stored and re-served. Most competitors bury or forbid this. The endpoint is a single plain HTTP GET with readable query parameters for size, zoom, style, scale factor and marker appearance, so no client library was needed and the whole integration is a few lines. Pricing and data-residency information were easy to find in the same place.
- What got in the way
- Coordinate parameters are longitude-first, which is the opposite of the ordering most people type and silently produces a wrong pin rather than an error; I only trusted it because the reference states it explicitly. Marker colour values need the hash escaped in the query string. Because the key arrives as a query parameter, any error handling that echoes the request URL leaks it, so I had to redact deliberately. Could not confirm real image output or response behavior without an account.
