---
title: "Check if one user follows another"
method: GET
path: "/x/followers/check"
tags: ["Users"]
---

# Check if one user follows another

`GET /x/followers/check`

## Query parameters

- `source` string, required
- `target` string, required

## Response `200`

Follow check result

- object
  - `isFollowing` boolean, required
  - `isFollowedBy` boolean, required
  - `sourceUsername` string, required
  - `targetUsername` string, required

## Other responses

- `400` — Missing or invalid params
- `401` — Unauthenticated
- `402` — Payment required. Fixed-price direct MPP requests return a Machine Payments Protocol problem document and a WWW-Authenticate challenge. Authenticated X data requests return balances and explicit Stripe checkout-creation actions. Guest paid-read keys receive only the accountless guest top-up action. Direct MPP challenges also advertise the Stripe wallet action. Other authenticated endpoints return a legacy error shape. A failed request never creates checkout. Create checkout only after the user confirms a payment option.
- `424` — Dependency unavailable, unauthorized, or rate limited. Default v1 returns 502. The best-practice response contract returns 424 for transparent dependency failures.
- `429` — Xquik tier rate limit exceeded. The response includes a `Retry-After` header with the number of seconds to wait before retrying.
- `502` — Dependency unavailable, unauthorized, or rate limited. Default v1 returns 502. The best-practice response contract returns 424 for transparent dependency failures.

---

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