---
title: Get custom text
description: The custom text editors wrote for one language, in one namespace, several or all of them, to merge over the messages your application bundles.
api: GET /umbraco/delivery/api/v1/app-translations/overrides
playground: simple
seo:
  image: /og/endpoints/overrides.png
---

Returns only the messages an editor changed. Merge them over your application's own messages, as the [Delivery API guide](/delivery-api) shows.

- **`locale`** · query · `string` · required

  The Umbraco language code. It has to match exactly: `da` finds nothing on a site that stores `da-DK`.

- **`namespace`** · query · `string`

  The [namespace](/sources#namespaces). Repeat it, as in `namespace=checkout&namespace=website`, for several namespaces, or leave it out for every namespace. Up to 20 at once.

- **`format`** · query · `string`

  The [message syntax](/delivery-api#message-syntax) your application reads: `icu` or `i18next`. Leave it out to get the messages in whatever syntax they are written in.

- **`Api-Key`** · header · `string`

  The [delivery key](/delivery-api#access), when one is configured. A bearer token in `Authorization` works too.

- **`If-None-Match`** · header · `string`

  The ETag of a response you already have. Umbraco answers `304` until something changes.

## Response

A JSON object of messages, nested the way your application's own files are. With one `namespace`, the namespace's messages sit at the top level. With several, or none, each namespace is a top-level key holding its own messages, as [one namespace, several, or all of them](/delivery-api#one-namespace-several-or-all-of-them) shows. `{}` when the locale or namespace has none.

| Status | Meaning |
| --- | --- |
| `200` | The messages. |
| `304` | Nothing changed since the ETag you sent. |
| `400` | `locale` is missing, `format` is not `icu` or `i18next`, the request names more than 20 namespaces, or `namespace` has a comma in it and no namespace has that name. |
| `401` | A key is configured, and the request did not send it. |
| `409` | The response would hold messages in a syntax `format` does not read, or, without `format`, both ICU and i18next messages. Or two sources supply the same key. |

```json 200
{
  "greeting": "Hej {name}, godt at se dig igen!"
}
```