/dribbble/users

POST /api/dribbble/users

Price: 5 credits

Get a Dribbble designer/agency profile by username or URL

How to use it

Get a Dribbble designer or agency profile by username (alias) or profile URL. Returns display name, headline, avatar, bio, location, member-since, team flag, available-for-work flag, contact email, website, follower/following/tag counts, skills, languages, expertise badges, social links, and team members.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "DribbbleUser")
• alias string required
• name string nullable
• headline string nullable
• image string nullable
• bio string nullable
• location string nullable
• member_since string nullable
• is_team boolean (default: false)
• is_pro boolean (default: false)
• is_available_for_work boolean (default: false)
• email string nullable
• website_url string nullable
• follower_count integer nullable
• following_count integer nullable
• tag_count integer nullable
• skills array (default: [])
• languages array (default: [])
• expertise array (default: [])
• social_links array (default: [])
  • @type string (default: "DribbbleSocialLink")
  • network string nullable
  • url string nullable
• members array (default: [])
  • @type string (default: "DribbbleUserBrief")
  • id integer nullable
  • alias string nullable
  • name string nullable
  • image string nullable
  • is_team boolean (default: false)
  • is_pro boolean (default: false)
  • is_available_for_work boolean (default: false)
  • url string nullable
  • team object nullable (see schema DribbbleUserBrief)
• 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 — Profile 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.