> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.3.x/symfony-ux/contact-picker.md).

# Contact Picker

This controller uses the Contacts Picker API\
to let users select one or more contacts directly from their device’s native address book.\
It emits events for availability, contact selection, and errors.

**Usage**

```twig
<div {{ stimulus_controller('@pwa/contact') }}>
  <button data-action="@pwa/contact#select">Select contact</button>
  <pre id="contacts-output">No contacts selected yet.</pre>
</div>

<script type="module">
  const el = document.querySelector('[data-controller="pwa__contacts"]');
  const out = document.getElementById('contacts-output');

  el.addEventListener('contacts:unavailable', () => {
    out.textContent = 'The Contacts Picker API is not available on this device.';
  });

  el.addEventListener('contacts:selection', (e) => {
    const { contacts } = e.detail;
    out.textContent = JSON.stringify(contacts, null, 2);
  });

  el.addEventListener('contacts:error', (e) => {
    out.textContent = `Error: ${e.detail.exception.message}`;
  });
</script>
```

### Parameters

None

### Actions

`select`: Opens the native contact picker. This action accepts the parameter `multiple` (boolean) to allow multiple contact selection.

### Targets

None

### Events

`unavailable`: The API is not supported on the current browser or platform.

`error`: The user cancels the picker or an exception occurs.

`selection`: The user successfully selects one or more contacts. Contains a list of contact objects.&#x20;

Each contact object may include:

* `name`  (string\[]|null)
* `email`  (string\[]|null)
* `tel`  (string\[]|null)
* `address`  (string\[]|null)
* `icon` (a blob if supported)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://pwa.spomky-labs.com/1.3.x/symfony-ux/contact-picker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.