---
title: Icons & websites
description: App and CMS branding — icon_url and website_url for UI and landings.
---

# Icons & websites

In admin, each **application** and **CMS site** can store a public icon and a website URL. Use them in “About”, product lists, landing footers, etc.

## Admin

- **Application** → **Overview** → **Branding** (name, description, icon, website)
- **CMS site** → **Overview** → **Site branding**

Paste an icon URL or upload a file (PNG / WebP / SVG) — a public URL is stored.

| Field | Purpose |
| --- | --- |
| `icon_url` | Logo / icon |
| `website_url` | Marketing or product website |

## Application (SDK / HTTP)

Requires the application `X-Public-Key`.

```http
GET /v1/applications/YOUR_APP_CODE/branding
X-Public-Key: YOUR_PUBLIC_KEY
```

Response:

```json
{
  "data": {
    "code": "YOUR_APP_CODE",
    "name": "…",
    "description": "…",
    "icon_url": "https://…",
    "website_url": "https://…"
  }
}
```

```ts
const { data } = await platform.getApplicationBranding();
// data.icon_url, data.website_url, data.name
```

Flutter: `getApplicationBranding()`.

## CMS site

Fields are already on the site root response (no separate endpoint):

```http
GET /v1/sites/YOUR_SITE_CODE
X-Public-Key: YOUR_CMS_SITE_KEY
```

or (site linked to an application):

```http
GET /v1/applications/YOUR_APP_CODE/sites/YOUR_SITE_CODE
X-Public-Key: YOUR_PUBLIC_KEY
```

```ts
const { data: site } = await platform.getCmsSite("YOUR_SITE_CODE");
// site.icon_url, site.website_url
```

The Platform does **not** render UI — it only returns URLs; the client renders `<img>` / links.