> 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/web-share.md).

# Web Share

## Introduction to the Web Share API

The Web Share API is a modern web technology that allows web applications to leverage the native share functionality of the user's device. By utilizing this API, developers can enhance the user experience by providing an easy and seamless way for users to share content directly from their web applications.

### Parameters

None

### Actions

`share` : This method requires a parameter `data` that contains at least one element of:

* `title`: The title of the data to be shared
* `url`: an URL to be shared
* `text`: a text to be shared
* `files`: a list of file URLs to be shared

{% hint style="info" %}
The `title` may be ignored by the client.
{% endhint %}

{% hint style="warning" %}
The list contains URLs that the client will download before sharing. **Ensure the files are small and shareable**. Refer to the list at [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share#shareable_file_types) for acceptable file types.
{% endhint %}

### Targets

None

### Events

`pwa--web-share:success`&#x20;

`pwa--web-share:error`&#x20;


---

# 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/web-share.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.
