---
title: "Apple Maps"
description: "Searches places and reads place details"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Apple Maps

<p>Searches places and reads place details</p>

<details data-command-index><summary>What you can do (5)</summary>
<h2>What you can do</h2>
<p>Available commands: 5 (5 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/apple-maps#command-maps-apple-search">Search places</a> — <code>maps.apple.search</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/apple-maps#command-maps-apple-place">Place details</a> — <code>maps.apple.place</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/apple-maps#command-maps-apple-directions">Directions and travel estimates</a> — <code>maps.apple.directions</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/apple-maps#command-maps-apple-geocode">Resolve an address</a> — <code>maps.apple.geocode</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/apple-maps#command-maps-apple-reverse-geocode">Resolve supplied coordinates</a> — <code>maps.apple.reverse-geocode</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Apple Maps, then enter the issued values in the connection form below.</p>
<ol>
<li>In Apple Developer Certificates, Identifiers &amp; Profiles, create a Maps identifier and a Maps-enabled private key. Download the .p8 file and record the Key ID and your Team ID. Use the official guide for the required account role and membership.</li>
</ol>
<p><a href="https://developer.apple.com/help/account/capabilities/create-a-maps-identifier-and-private-key/">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Key ID</td>
<td>Required</td>
</tr>
<tr>
<td>Team ID</td>
<td>Required</td>
</tr>
<tr>
<td>Private key (.p8)</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": "coffee shops in Singapore",
    "languageCode": "en-US",
    "countryCode": "SG"
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-maps-apple-search">
<summary><span>Search places — <code>maps.<wbr>apple.<wbr>search</code></span></summary>
<p>Run <strong>Search places</strong> with Apple Maps. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps?command=maps.apple.search">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>string</td>
<td>Required</td>
<td>Search criteria</td>
<td><code>maxLength: 1000</code></td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td>Optional</td>
<td>Language code</td>
<td><code>maxLength: 1000</code></td>
</tr>
<tr>
<td><code>countryCode</code></td>
<td>string</td>
<td>Optional</td>
<td>Country code</td>
<td><code>maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/apple-maps/commands/maps.apple.search">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": "coffee shops in Singapore",
  "languageCode": "en-US",
  "countryCode": "SG"
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-maps-apple-place">
<summary><span>Place details — <code>maps.<wbr>apple.<wbr>place</code></span></summary>
<p>Run <strong>Place details</strong> with Apple Maps. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps?command=maps.apple.place">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>placeId</code></td>
<td>string</td>
<td>Required</td>
<td>Place ID</td>
<td><code>maxLength: 1000</code></td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td>Optional</td>
<td>Language code</td>
<td><code>maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/apple-maps/commands/maps.apple.place">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "placeId": "PLACE_ID",
  "languageCode": "en-US"
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-maps-apple-directions">
<summary><span>Directions and travel estimates — <code>maps.<wbr>apple.<wbr>directions</code></span></summary>
<p>Run <strong>Directions and travel estimates</strong> with Apple Maps. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps?command=maps.apple.directions">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>origin</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>origin.latitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -90; maximum: 90</code></td>
</tr>
<tr>
<td><code>origin.longitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -180; maximum: 180</code></td>
</tr>
<tr>
<td><code>destination</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>destination.latitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -90; maximum: 90</code></td>
</tr>
<tr>
<td><code>destination.longitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -180; maximum: 180</code></td>
</tr>
<tr>
<td><code>transportType</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>enum: [&quot;Automobile&quot;,&quot;Walking&quot;,&quot;Cycling&quot;]</code></td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td>Required</td>
<td>Language code</td>
<td><code>minLength: 1; maxLength: 6; pattern: &quot;^[a-z]{2,3}(-[A-Z]{2})?$&quot;</code></td>
</tr>
<tr>
<td><code>requestsAlternateRoutes</code></td>
<td>boolean</td>
<td>Required</td>
<td>Return alternative routes</td>
<td></td>
</tr>
<tr>
<td><code>avoid</code></td>
<td>array</td>
<td>Required</td>
<td></td>
<td><code>maxItems: 1; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>avoid[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;Tolls&quot;]</code></td>
</tr>
<tr>
<td><code>departureDate</code></td>
<td>string</td>
<td>Optional</td>
<td>UTC departure time</td>
<td><code>minLength: 1; maxLength: 20; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>arrivalDate</code></td>
<td>string</td>
<td>Optional</td>
<td>UTC arrival time</td>
<td><code>minLength: 1; maxLength: 20; format: &quot;date-time&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/apple-maps/commands/maps.apple.directions">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "origin": {
    "latitude": 37.7857,
    "longitude": -122.4011
  },
  "destination": {
    "latitude": 37.7754,
    "longitude": -122.3932
  },
  "transportType": "Walking",
  "languageCode": "en-US",
  "requestsAlternateRoutes": false,
  "avoid": []
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-maps-apple-geocode">
<summary><span>Resolve an address — <code>maps.<wbr>apple.<wbr>geocode</code></span></summary>
<p>Run <strong>Resolve an address</strong> with Apple Maps. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps?command=maps.apple.geocode">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>address</code></td>
<td>string</td>
<td>Required</td>
<td>Explicit address</td>
<td><code>minLength: 1; maxLength: 500</code></td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td>Required</td>
<td>Language code</td>
<td><code>minLength: 1; maxLength: 6; pattern: &quot;^[a-z]{2,3}(-[A-Z]{2})?$&quot;</code></td>
</tr>
<tr>
<td><code>countryCode</code></td>
<td>string</td>
<td>Required</td>
<td>Country filter, empty when unspecified</td>
<td><code>maxLength: 2; pattern: &quot;^([A-Z]{2})?$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/apple-maps/commands/maps.apple.geocode">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "address": "1 Apple Park Way, Cupertino, CA",
  "languageCode": "en-US",
  "countryCode": "US"
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-maps-apple-reverse-geocode">
<summary><span>Resolve supplied coordinates — <code>maps.<wbr>apple.<wbr>reverse-<wbr>geocode</code></span></summary>
<p>Run <strong>Resolve supplied coordinates</strong> with Apple Maps. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/apple-maps?command=maps.apple.reverse-geocode">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>coordinate</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>coordinate.latitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -90; maximum: 90</code></td>
</tr>
<tr>
<td><code>coordinate.longitude</code></td>
<td>number</td>
<td>Required</td>
<td></td>
<td><code>minimum: -180; maximum: 180</code></td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td>Required</td>
<td>Language code</td>
<td><code>minLength: 1; maxLength: 6; pattern: &quot;^[a-z]{2,3}(-[A-Z]{2})?$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/apple-maps/commands/maps.apple.reverse-geocode">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "coordinate": {
    "latitude": 37.3302,
    "longitude": -122.010642
  },
  "languageCode": "en-US"
}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developer.apple.com/documentation/applemapsserverapi">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/apple-maps/index.mdx