# /jmty/users/listings

`POST /api/jmty/users/listings`

Price: 5 credits

List every listing a Jimoty (jmty.jp) member has posted, across all eleven sections at once — second-hand goods, cars, property, jobs, lessons, events, services and the rest. Each row carries the listing id, title, description, headline price, the section badge the site prints on the card, the municipality and nearest station, whether the listing is already sold or closed, the thumbnail and the listing URL. This is the full inventory view for a Japanese used-car dealer, letting agency or high-volume private seller, and the id on every row feeds jmty/listings for the complete record.

## How to use it

List a Jimoty member's listings. user accepts the 24 character hexadecimal profile id or the full profile URL, count is required. Rows span every section the member posts in, so read vertical on each row to tell a car from a flat. The feed mixes live and finished postings, so read is_closed to tell a still-available item from one already sold or withdrawn. price holds the headline amount in JPY and is 0 for giveaways. updated_date carries month and day only because the source omits the year on this surface — use jmty/listings for the exact timestamp. Feed key into jmty/listings.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `user` (string, required) — Profile id or its full jmty.jp profile URL (examples: "563091fb03cb6f093c00059e", "https://jmty.jp/profiles/563091fb03cb6f093c00059e")
- `count` (integer, required) — Max number of listings to return (min: 1; max: 10000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "JmtyUserListingCard")
- `key` (string, required)
- `listing_title` (string, required)
- `text` (string, nullable)
- `price` (number, nullable)
- `price_label` (string, nullable)
- `currency` (string) (default: "JPY")
- `vertical` (string, nullable)
- `category` (string, nullable)
- `vertical_label` (string, nullable)
- `location` (string, nullable)
- `updated_date` (string, nullable)
- `is_closed` (boolean) (default: false)
- `image` (string, nullable)
- `url` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

No jmty.jp profile with this id exists

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.