---
title: "Resolve a handle to a numeric X ID"
method: POST
path: "/x/users/resolve"
tags: ["Leads"]
---

# Resolve a handle to a numeric X ID

`POST /x/users/resolve`

## Request

- Base URL: `https://app.pumpgtm.com/api/v1`
- URL: `https://app.pumpgtm.com/api/v1/x/users/resolve`
- Auth: HTTP bearer

One exact public handle lookup through the public X data provider. No email-to-X enrichment or fuzzy identity matching. An unverified or unavailable profile returns HTTP 503 with status unknown and user null. No official X fallback.

## Headers

- `X-PumpGTM-Client` string, uuid
- `X-PumpGTM-User` string

## Request body

- object
  - `username` string, required: Public X handle, with optional @. Case-insensitive.

## Response `200`

Successful response. Read outcome fields; success does not imply delivery.

- object
  - `status` 'resolved', required
  - `user` object, required
    - `xUserId` string, required: Numeric X user ID as a string. Never convert it to a JavaScript number.
    - `username` string, required
    - `name` string, required
    - `checkedAt` string, required
    - `evidence` 'public_profile', required
  - `provider` 'twitterapi', required
  - `sendsMessages` unknown, required

## Other responses

- `400`: Invalid input; for partner keys also user_header_required when the account requires X-PumpGTM-User
- `401`: Missing, invalid or revoked key
- `403`: Workspace mismatch, channel or feature disabled; for partner keys also enterprise_required and user_disabled
- `404`: Resource unavailable in this workspace
- `409`: Revision, identity or state conflict: { error, message } and nothing changed
- `429`: Rate limit; respect Retry-After when provided
- `500`: internal_error: an unexpected failure on our side; retry, then contact PumpGTM
- `503`: Dependency unavailable; identity may be unknown

## Changes

- **2026-10-12** `06d2e4d0e84b`: 8 info
  - the response property `error` became required for the status `400`
  - the response property `error` became required for the status `401`
  - the response property `error` became required for the status `403`
  - the response property `error` became required for the status `404`
  - …4 more
- **2026-10-12** `08c80059d483`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/pumpgtm/apis/pumpgtm-api/changes/x/users/resolve/post.md)

---

[API](https://skmtc.dev/pumpgtm/apis/pumpgtm-api.md) - [All operations](https://skmtc.dev/pumpgtm/apis/pumpgtm-api/llms.txt) - [OpenAPI document](https://skmtc.dev/pumpgtm/apis/pumpgtm-api/revisions/06d2e4d0e84b?raw)
