Files

Rasmus Langvad d0546926a9 Merged in fix/3697-prettier-configs (pull request #3396 )

fix(SW-3691): Setup one prettier config for whole repo

* Setup prettierrc in root and remove other configs


Approved-by: Joakim Jäderberg
Approved-by: Linus Flood

2026-01-07 12:45:50 +00:00

index.tsx

Merged in fix/3697-prettier-configs (pull request #3396 )

2026-01-07 12:45:50 +00:00

ReadMe.md

Merged in feat/sw-3240-move-staticmap-to-design-system (pull request #2654 )

2025-08-14 12:22:19 +00:00

utils.ts

Merged in fix/3697-prettier-configs (pull request #3396 )

2026-01-07 12:45:50 +00:00

ReadMe.md

Google Map Static API

About

The Google Maps Static API lets you embed a Google Maps image on your web page. The Google Maps Static API service creates your map based on URL parameters sent through a standard HTTP request and returns the map as an image you can display on your web page. Due to regulations from Google we are not allowed to store and serve copies of images generated using the Google Maps Static API. All web pages that require static images must link the src attribute of an HTML img tag or as a background-image using CSS.

API Key Restrictions

You can restrict your API key on websites, IP addresses, Android apps and iOS apps. For now (12/8-24) the API key is restricted by IP address, hence the request will only work at Scandic HQ network. This will be changed to a referrer website in the future. Read more about API key restrictions

Digital Signature

Requests exceeding 25,000 requests per day require an API key and a digital signature. However, it is strongly recommended by Google to use both an API key and digital signature, regardless of the usage.

The digital signature is set on the Google Maps Platform. For dynamically generated requests, the signature is handled through server side signing appending the signature as base64 on the request url. Read more about digital signature

Generating new API keys

Regenerating an API key creates a new key that has all the old key's restrictions. This process also starts a 24-hour timer after which the old API key is deleted. During this time window, both the old and new key are accepted, giving you a chance to migrate your apps to use the new key. However, after this time period elapses, any apps still using the old API key stop working.

Caution: Only regenerate an API key if you absolutely must to avoid unauthorized use. This process can shut down legitimate traffic and prevent your apps from functioning properly. Read more about regenerating keys

Version history

Description	Version	Date	Author
Create ReadMe file.	1.0.0	12/8-24	Fredrik Thorsson