/artstation/users

POST /api/artstation/users

Price: 1 credit

Get ArtStation artist profile by username or URL

How to use it

Get an ArtStation artist's full profile by username or profile URL. Returns display name, headline, bio summary, location, PRO status, follower/following/project counts, availability, skills, software, social and freelance links, work experience, production credits (film/TV/game), avatar, and cover image.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — ArtStation username or profile URL (examples: "tully", "https://www.artstation.com/tully"; minLength: 1)

Response

• @type string (default: "ArtstationUser")
• id integer required
• alias string nullable
• full_name string nullable
• headline string nullable
• summary string nullable
• city string nullable
• country string nullable
• is_pro boolean (default: false)
• is_staff boolean (default: false)
• is_studio_account boolean (default: false)
• is_school_account boolean (default: false)
• follower_count integer nullable
• following_count integer nullable
• project_count integer nullable
• community_project_count integer nullable
• liked_project_count integer nullable
• collection_count integer nullable
• availability string nullable
• available_full_time boolean (default: false)
• available_freelance boolean (default: false)
• available_contract boolean (default: false)
• image string nullable
• cover string nullable
• website_url string nullable
• demo_reel_url string nullable
• skills array (default: [])
• software array (default: [])
• social_links array (default: [])
  • @type string (default: "ArtstationSocialLink")
  • network string nullable
  • url string nullable
• freelance_links array (default: [])
  • @type string (default: "ArtstationSocialLink")
  • network string nullable
  • url string nullable
• experience array (default: [])
  • @type string (default: "ArtstationExperience")
  • role string nullable
  • company string nullable
  • description string nullable
  • location string nullable
  • start_date string nullable
  • end_date string nullable
  • is_current boolean (default: false)
• productions array (default: [])
  • @type string (default: "ArtstationProduction")
  • role string nullable
  • company string nullable
  • production_title string nullable
  • production_type string nullable
  • release_year integer nullable
• url string 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 — Artist not found. Verify the username or profile URL. 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.