Move to Mapsource

Move to Mapsource

Use https://api.mapsource.io/interpreter as the complete query endpoint and add your subscription key as a Bearer header. Clients that append their own interpreter path need a different base; see client setup. Paths also work with an /api prefix, so existing https://mapsource.io/api/... URLs keep working.

# Destination interpreter
https://api.mapsource.io/interpreter

# Authentication header for Mapsource only
Authorization: Bearer $MAPSOURCE_API_KEY

Keep the previous endpoint in your configuration during testing. Set explicit timeout and memory directives, and check them against your plan. Verify the serving dataset and its timestamp on status before cutting production traffic over.

Compare behavior

• Run representative small and expensive queries, not just a health request.
• Compare element IDs and tags with allowance for different dataset timestamps.
• Check geometry, relation members, metadata fields, output formats, and generated areas.
• Confirm timeout, memory, response-size, rate, and concurrency behavior.
• Remove historical attic selectors; they are not available through Mapsource.
• Monitor failures and usage after moving one workload, then expand gradually.

Move to another service

Your application’s query text remains standard Overpass QL. Change the destination endpoint and remove the Mapsource Authorization header before sending requests elsewhere. Use the destination’s own authentication if required.

There is no Mapsource-hosted copy of your submitted query text or results to export. Retain application configuration and results on your side as needed. You can save your current usage summary before ending access.

Basemap templates, tile authentication, elevation response fields, and MCP tool names are separate integration points. An Overpass URL change does not replace those services automatically; select and test alternatives for each one your application uses.

Public or self-hosted Overpass

If moving to a public instance, read its usage policy and available capacity before sending traffic. Do not assume a public endpoint can absorb a subscription workload or provide the same limits, freshness, or availability.

For your own instance, plan storage, database import, metadata and area generation, replication, monitoring, and backups. Confirm the instance is current before switching. The upstream Overpass manual is the reference for query and server behavior.

Cancel your subscription

Open Usage and billing, enter the subscription key, and select Manage billing. Use Stripe’s cancellation flow and confirm the effective date shown there. A scheduled cancellation retains access until the paid period ends.

If you no longer have the key, contact support using your purchase email and reference. The receipt reference helps locate the purchase but does not authorize cancellation by itself. See key recovery.

Migration checklist

1. Save application queries and configuration.
2. Validate results and limits against the destination.
3. Move traffic and inspect application errors.
4. Update attribution and companion-service integrations.
5. Save usage records you need while account access remains active.
6. Confirm cancellation separately from changing your application’s URL.
7. Remove the old key from deployments and secret stores once no longer needed.