---
title: "Create wallpaper"
method: POST
path: "/v1/enterprise/{enterprise_id}/wallpaper/"
tags: ["esper_cloud_api_Wallpapers"]
---

# Create wallpaper

`POST /v1/enterprise/{enterprise_id}/wallpaper/`

Uploads a new wallpaper image to the enterprise. The image is submitted as a multipart/form-data request and, once uploaded, can be referenced by wallpaper_id in Windows blueprint homescreen and lock screen settings. There is no dedicated wallpaper library in the console. Wallpapers are only visible by previewing their associated blueprint.

**Request body (multipart/form-data)**

image_file (required) — The image file to upload

orientation (required) — Orientation of the image (e.g., landscape)

**Common Use Cases**

Adding a new branded wallpaper before assigning it to a blueprint

Programmatically uploading wallpapers as part of an enterprise onboarding or branding 

**Workflow**

Replacing an outdated wallpaper by uploading a new version and updating blueprint references to point to the new wallpaper_id

**Best Practices**

Store the wallpaper_id UUID from the response — it is required to reference the wallpaper in a blueprint homescreen and lock screen settings

Since wallpapers are not browsable in the Console, use GET /v1/enterprise/{enterprise_id}/wallpaper/ to audit what has been uploaded and avoid creating duplicates

Specify orientation accurately at upload time — this metadata cannot be changed after upload; upload a new image if the orientation needs to be corrected

Verify a wallpaper is not referenced in any active blueprint before deleting it, as there is no Console warning to flag active references

## Path parameters

- `enterprise_id` string, required

## Response `201`

Successful Operation

- EsperCloudApiWallpaper
  - `id` string, uuid
  - `enterprise` string, uuid
  - `image_file` string, url
  - `thumbnail` string, url
  - `orientation` string
  - `is_active` boolean
  - `created_on` string, date-time
  - `updated_on` string, date-time

## Other responses

- `400` — Bad request
- `401` — Authorization information is missing or invalid.
- `403` — Forbidden, no permission to perform this action.
- `415` — Unsupported media type.
- `500` — Internal server error

---

[API](https://skmtc.net/esper/apis/esper-api-reference.md) · [All operations](https://skmtc.net/esper/apis/esper-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/esper/esper-api-reference/revisions/e1f64cbb488e/schema)