Description
Disclaimer: Apple Maps, MapKit JS, and the Apple logo are trademarks of Apple Inc. Apple Maps may not be available in all countries or regions.
This plugin integrates Apple’s MapKit JS into an “Apple Maps” block in the WordPress block editor (Gutenberg). You will need an Apple Developer Program account, Maps Identifier, and Private Key to configure this plugin and connect to the MapKit JS API in order for the block to function. Note that the Apple Developer Program has an annual fee of 99 USD, in local currency where available. Prices may vary by region and are listed in local currency during the enrollment process. Fee waivers are available for the Apple Developer Program for eligible organizations.
Configuration
In order to start using the Apple Maps block, you will need to sign up for the Apple Developer Program and create your Maps identifiers, keys, and tokens. Follow the steps below to generate the Private Key, Key ID, and Team ID that you will need to configure the plugin and gain access to the MapKit JS API for the Apple Maps block.
Create an Apple Developer account
- If you don’t already have an Apple ID, then please create an Apple ID as it is required in order to enroll in the Apple Developer Program in the next step.
- Enroll in the Apple Developer Program as either an individual or organization. Note that its possible to have an existing Apple Developer account but not be enrolled in the Apple Developer Program, so please be sure to complete the enrollment process in this step.
- Sign the Apple Developer Program License Agreement in the Agreements, Tax, and Banking section of App Store Connect.
Create a Maps Identifier and Private Key
- Create a Maps ID and a MapKit JS Private Key.
- Copy the Private Key, paste it into the respective plugin setup field, and ensure the key includes the
-----BEGIN PRIVATE KEY-----and-----END PRIVATE KEY-----lines. - Open the Key you created in Step 1, copy the
Key IDvalue, and paste it into the respective plugin setup field. - Open the Identifier you created in Step 1, copy the
App ID Prefixvalue (notice the value is appended with(Team ID)), and paste it into the respective plugin setup field. - Click the
Confirm MapKit Credentialsbutton in the plugin setup to gain access to the block options and begin customizing your Apple Maps block!
Screenshots
Block settings 
Block marker settings 
Block initial install view showing MapKit JS credential fields 
Block settings page showing MapKit JS credential fields
Blocks
This plugin provides 1 block.
- Apple Maps Add an Apple Map to your site.
Installation
- Install the plugin via the plugin installer, either by searching for it or uploading a .ZIP file.
- Activate the plugin.
- Follow the instructions to configure your accesss to the MapKit JS API.
- Use Apple Maps for WordPress!
FAQ
-
I’m seeing validation errors when trying to authenticate my MapKit JS credentials, what am I doing wrong?
-
If you have WordPress installed in a subdirectory, then there is a known issue specifically related to this setup where the WordPress Admin URL is different from the site URL. We’re working on a minor release to resolve this issue.
-
I want to update my MapKit JS credentials, what’s the best way to do this?
-
Our recommendation on updating the Apple Maps block settings focuses on ensuring the best experience for your site users. Specifically we recommend the following approach to ensure that existing Apple Maps on your site continue to be displayed during your MapKit JS credential transition.
- Create a new MapKit JS Private Key, Key ID, and/or Team ID.
- Update the Apple Maps block settings with the newly created Private Key, Key ID, and/or Team ID.
- Delete your old MapKit JS Private Key, Key ID, and/or Team ID.
-
Are there any MapKit JS rate limits?
-
There is a free daily limit of 250,000 map views and 25,000 service calls per the Apple Developer Program membership. For additional MapKit JS capacity needs you will need to contact Apple directly.
-
Can I see how many map views and service requests are made to my MapKit JS Private Key?
-
Yes, you can track your MapKit JS useage on the MapKit JS Developer Dashboard. You can also monitor map initializations and service requests in realtime, or see up to a year of activity by day, week, month, or year via the MapKit JS Dashboard.
Reviews
Contributors & Developers
“Block for Apple Maps” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Block for Apple Maps” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.5 – 2025-07-14
-
Note that this release bumps the WordPress minimum version from 6.4 to 6.6.
-
Changed: Bump WordPress “tested up to” version 6.8 (props @sudip-md, @mehidi258, @jeffpaul, @dkotter, @peterwilsoncc, @Rishabh-fueled via #229, #230, #237, #238).
- Changed: Bump WordPress minimum supported version to 6.6 (props @sudip-md, @mehidi258, @jeffpaul, @dkotter, @peterwilsoncc, @Rishabh-fueled via #229, #230, #238).
- Fixed: Block crash when no Apple Maps credentials are configured (props @elvismdev, @peterwilsoncc via #233).
- Security: Bump
bracesfrom 3.0.2 to 3.0.3,expressfrom 4.18.2 to 4.19.2,webpackfrom 5.89.0 to 5.94.0 andwebpack-dev-middlewarefrom 5.3.3 to 5.3.4 (props @dependabot, @faisal-alvi via #224). - Security: Bump
@wordpress/scriptsfrom 27.9.0 to 30.6.0,body-parserfrom 1.20.2 to 1.20.3,expressfrom 4.19.2 to 4.21.1,wsfrom 7.5.9 to 8.18.0,sendfrom 0.18.0 to 0.19.0 andserve-staticfrom 1.15.0 to 1.16.2 (props @dependabot, @peterwilsoncc via #231). - Security: Bump
@wordpress/e2e-test-utils-playwrightfrom 1.13.0 to 1.18.0,serialize-javascriptfrom 6.0.1 to 6.0.2,mochafrom 10.2.0 to 11.1.0 and removescookie(props @dependabot, @peterwilsoncc via #234). - Security: Bump
axiosfrom 1.7.4 to 1.9.0 andhttp-proxy-middlewarefrom 2.0.6 to 2.0.9 (props @dependabot, @peterwilsoncc via #241).
1.1.4 – 2024-08-22
-
Note that this release bumps the WordPress minimum version from 5.8 to 6.4.
-
Changed: Update the
apiVersionof the Apple Maps Block to Version 3 (props @fabiankaegy, @wadebekker, @dkotter via #211). - Changed: Bump WordPress “tested up to” version to 6.6 (props @QAharshalkadu, @sudip-md, @jeffpaul, @dkotter via #212, #218).
- Changed: Bump minimum WordPress version from 5.8 to 6.4 (props @QAharshalkadu, @sudip-md, @jeffpaul, @dkotter via #212, #218).
- Fixed: Load the Apple MapKit script in the editor iframe to ensure the Apple Maps block works correctly (props @fabiankaegy, @wadebekker, @dkotter via #211).
- Security: Bump
postcssfrom 8.4.23 to 8.4.32 (props @dependabot, @faisal-alvi via #194). - Security: Bump
@babel/traversefrom 7.21.5 to 7.23.7 (props @dependabot, @peterwilsoncc via #200). - Security: Bump
axiosfrom 0.25.0 to 1.7.4,@wordpress/scriptsfrom 24.6.0 to 27.5.0,expressfrom 4.18.2 to 4.19.2,follow-redirectsfrom 1.15.3 to 1.15.6 andwebpack-dev-middlewarefrom 5.3.3 to 5.3.4 (props @dependabot, @Sidsector9 via #209, #219). - Security: Bump
bracesfrom 3.0.2 to 3.0.3 andwsfrom 7.5.9 to 7.5.10 (props @dependabot, @iamdharmesh via #215). - Developer: Support for the WordPress.org plugin preview (props @dkotter, @jeffpaul via #196).
Earlier versions
For the changelog of earlier versions, please refer to the changelog on github.com.