/dribbble/users/search

POST /api/dribbble/users/search

Price: 20 credits

Search Dribbble designers and agencies

How to use it

Search the Dribbble designer directory by keyword and filter by category, location, minimum rating, project budget, PRO status, availability, and agencies-only. Returns designer cards with alias, name, avatar, PRO flag, rating, review and completed-project counts, number of services, starting price, location, and skills.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text search keyword (examples: "logo designer")
• category array nullable — Filter by design category (one of: "Branding", "Web Design", "Illustration", "Product Design", "Mobile", "Animation", "Typography", "Print")
• location string nullable — Filter by the designer's location (examples: "United States")
• minimum_rating integer nullable — Minimum designer review rating (one of: 1, 2, 3, 4)
• budget_min integer nullable — Minimum fixed project budget (USD) (min: 0)
• budget_max integer nullable — Maximum fixed project budget (USD) (min: 0)
• pro_only boolean — Only PRO designers (default: false)
• available_for_work boolean — Only designers available for work (default: false)
• responds_quickly boolean — Only designers that respond quickly (default: false)
• agencies_only boolean — Only design agencies/teams (default: false)
• count integer required — Max result count (min: 1)

Response

• @type string (default: "DribbbleDesignerCard")
• id integer required
• alias string nullable
• name string nullable
• image string nullable
• is_pro boolean (default: false)
• rating number nullable
• review_count integer nullable
• projects_completed_count integer nullable
• service_count integer nullable
• starting_price number nullable
• location string nullable
• response_time string nullable
• skills array (default: [])
• 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 — The entity was not found, or a precondition failed 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.