# Settings

## Name a widget

To change name of a widget, send a **PATCH** request on `/widgets/{id}`.

```json
PATCH https://api.didomi.io/widgets/{id}?organization_id=YOUR_ORG_ID

{
  "name": "YOUR_TITLE"
}
```

## Make a widget Headless

To make a widget headless, send a **PATCH** request on `/widgets/{id}`

*Note that the widget format has to be `embeddable` for a Headless widgets to work.*

```json
PATCH https://api.didomi.io/widgets/{id}?organization_id=YOUR_ORG_ID

{
  "headless": true
}
```

## Set Meta Tags

To set the meta tags, send a **PATCH** request on `/widgets/{id}` and specify the following properties.

| Property  | Description                                                                                                                                      |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `favicon` | Icon displayed in the address bar of a browser. You need to add an URL to display a favicon in your hosted widget.                               |
| `title`   | Title displayed in the address bar of a browser. You can edit the translations enabled in your widget to overwrite our default content provided. |

```json
PATCH https://api.didomi.io/widgets/{id}?organization_id=YOUR_ORG_ID

{
    "meta_tags": {
        "favicon": "String",
        "title": {
            "en": "String",
            "fr": "String"
        }
    }
}
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.didomi.io/api-and-platform/widgets/privacy-widgets/edit-a-widget/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.