API request¶
The current public rendering route is:
The query combines access control, map selection, and output settings. Parameter names are normalized to lowercase by the TypeScript service, but examples use the canonical lowercase spelling.
Request lifecycle¶
- Validate the API key.
- Detect a capabilities request, when applicable.
- Resolve a stored style alias or use the supplied style URL.
- Validate BBOX, dimensions, DPI, style URL, and attribution option.
- Queue the render.
- Load the style and referenced remote assets.
- Render and post-process the image.
- Return the image and remove the temporary file.
The current Express queue admits one active request per process. Integrations should expect render latency, use a suitable client timeout, and avoid immediate retry storms.
URL encoding¶
Always encode query values individually. A style URL may itself contain ?, &, =, or a provider key. Concatenating strings by hand can truncate or reinterpret it.
const url = new URL("https://api.wmsvt.com/api/v1.0.2/queued-wms");
url.search = new URLSearchParams({
key: process.env.WMSVT_API_KEY,
styleurl: process.env.STYLE_URL,
bbox: "238138.09,6238073.60,264358.09,6264293.63",
width: "1200",
height: "800",
dpi: "96"
});
const response = await fetch(url);
if (!response.ok) throw new Error(await response.text());
const image = Buffer.from(await response.arrayBuffer());
Keep this code on a trusted server. Putting a long-lived key in browser JavaScript makes it public.
Capabilities¶
The TypeScript service contains GetCapabilities handling when service=WMS and request=GetCapabilities are present, after API-key validation. Treat this as a product-specific compatibility surface until the advertised WMS version, schema validity, and production endpoint have been tested together.