---
title: "Get a user's profile photos"
method: GET
path: "/v1/users/{peer_id}/photos"
tags: ["Identity"]
---

# Get a user's profile photos

`GET /v1/users/{peer_id}/photos`

## Request

- Base URL: `https://telegram155.p.rapidapi.com`
- URL: `https://telegram155.p.rapidapi.com/v1/users/{peer_id}/photos`
- Auth: none declared

Returns the profile photo history for a user.

## Path parameters

- `peer_id` integer, required

## Query parameters

- `limit` integer
- `offset` integer
- `max_id` integer

## Response `200`

Profile photo history.

- UserPhotos: Profile photo history for a user. `count` is present only when the result is paginated (PhotosPhotosSlice).
  - `count` integer: Total photo count when paginated. Absent when the full set is returned.
  - `photos` Photo[]
    - `dcid` integer: Telegram data-center id where the photo lives.
    - `flags` integer: Bitfield flags.
    - `has_video` boolean: True if the photo has a video preview.
    - `photo_id` integer: Photo id.
    - `stripped_thumb` string: Base64-ish stripped JPEG thumbnail; can be expanded client-side.

## Other responses

- `400`: Invalid request — bad path or query parameter.
- `404`: Not found.
- `409`: The peer id could not be found, so no access hash exists for it. Not transient: seed the id via GET /v1/usernames/{username}, GET /v1/phones/{phone}, or by encountering it in a chat, then retry. Raw MTProto ids only: a Bot-API id like -1001234567890 must be sent as 1234567890 (strip the leading -100), and -123456789 as 123456789. When the request carries such an id, the hint names the exact id to retry with.
- `429`: Rate limit exceeded.
- `503`: Service temporarily unavailable.
- `504`: Request timed out.

---

[API](https://skmtc.dev/tgatlas/apis/tgatlas-telegram-channel-data-api.md) · [All operations](https://skmtc.dev/tgatlas/apis/tgatlas-telegram-channel-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tgatlas/apis/tgatlas-telegram-channel-data-api/revisions/875ce0155fe9?raw)