/bringatrailer/members

POST /api/bringatrailer/members

Price: 1 credit

Get one Bring a Trailer member profile by username or URL: display name, member-since month, location, total likes, Local Partner flag, and counts of listings, live listings, auction wins, bids, comments, comments of note, editorials and success stories.

How to use it

Fetch a Bring a Trailer member's public profile by the username from their /member/ URL, such as a listing's seller_alias or a comment author's alias. Use bringatrailer/members/listings, /bids and /comments for the rows behind the counts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• member string required — Username from a bringatrailer.com/member/<username>/ URL, or the URL itself (examples: "bonnevillejoe", "https://bringatrailer.com/member/bonnevillejoe/"; minLength: 1)

Response

• @type string (default: "BringatrailerMember")
• alias string required
• user_id string nullable
• name string nullable
• url string required
• member_since string nullable
• location string nullable
• like_count integer nullable
• is_local_partner boolean nullable
• listing_count integer nullable
• live_listing_count integer nullable
• won_auction_count integer nullable
• bid_count integer nullable
• comment_count integer nullable
• comment_of_note_count integer nullable
• editorial_count integer nullable
• success_story_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 Bring a Trailer member exists at this username. 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 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 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 Wait at least 30 seconds, then retry.

Response 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.