---
title: "POST /v2/social/assets/recent-buyers"
method: POST
path: "/v2/social/assets/recent-buyers"
tags: ["Social Activity"]
---

# POST /v2/social/assets/recent-buyers

`POST /v2/social/assets/recent-buyers`

## Request

- Base URL: `https://api.arbital.xyz` (the document declares no server; this is the origin it was published from)
- URL: `https://api.arbital.xyz/v2/social/assets/recent-buyers`
- Auth: HTTP bearer

Returns each tracked Fomo or pump.fun trader profile's latest observed buy in the last seven days for the requested assets. Entries are public trade observations, not current holdings or portfolio PnL. Counts cover matching current, unretracted trades for the requested assets; unrelated activity does not truncate coverage. Very expensive reads fail explicitly with 503 rather than returning partial counts as zero.

## Request body

- SocialAssetRecentBuyersRequest
  - `assets` object[], required
    - `address` string, required
    - `chainId` 'solana:mainnet-beta' | 'eip155:1' | 'eip155:56' | 'eip155:143' | 'eip155:4663' | 'eip155:5042' | 'eip155:8453' | 'eip155:42161', required
  - `limit` integer

## Response `200`

Recent buyers and their latest observed entry trades

- SocialAssetRecentBuyersResponse
  - `items` object[], required
    - `assetRef` object, required
      - `address` string, required
      - `chainId` string, required
    - `recentBuyerCount` integer, required
    - `recentBuyers` object[], required
      - `avatarUrl` string, nullable, required
      - `displayName` string, nullable, required
      - `entry` object, required
        - `amountAtomic` string, required
        - `boughtAtMs` string, required
        - `decimals` integer, required
        - `entryPriceUsd` string, required
        - `transactionSignature` string, required
        - `usdNotional` string, required
      - `handle` string, nullable, required
      - `platformSubjectId` string, required
      - `relationship` 'recent_buyer', required

## Other responses

- `400`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `401`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `413`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `503`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.

---

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