# Parse a text out of base64 or base64url or URL or HTML encoding

`POST /v1/convert/string/from/{codec}`

Decodes a base64, base64url, url_component, url or html entity encoded text back into UTF-8.

## Parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| codec | one of: base64, base64url, url_component, url, html | yes |  |

## Request body

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| text | string | yes | The text to decode |
| charset | string | no | How bytes become characters for base64 and URL encodings, for example utf-8 or iso-8859-1 (default `"utf-8"`) |

## Example request

A request body that works, as JSON.

```json
{
  "text": "TGljZW5zZSBBZ3JlZW1lbnQ="
}
```

## Response

The fields inside `data` of a successful response.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| text | string | yes | The result |

## Example response

A real answer from the operation, as JSON. The fields in the table above are inside `data`.

```json
{
  "data": {
    "text": "License Agreement"
  },
  "errors": null,
  "meta": {
    "request_id": "ecde2501-b58d-4b17-bf9f-98bd356b9613",
    "timestamp": "2026-10-27T07:19:42.051373Z",
    "version": "2026-03-26"
  },
  "pagination": null
}
```

## Responses

| Status | When it happens |
| --- | --- |
| 200 | Successful Response |
| 400 | The body respects the operation schema, but the use case rejected it. Each problem is one ApiError entry |
| 413 | The request is larger than the request size limit of the API allows |
| 422 | The body does not respect the operation schema. Each problem is one ApiError entry with the code validation_error |
| 500 | Something failed inside the server and was not an input problem. The same envelope, errors may be empty |

---
Source: https://skillfulsardine.com/developers/api/decode-text/