/dribbble/shots

POST /api/dribbble/shots

Price: 5 credits

Get a Dribbble shot by id or URL

How to use it

Get full details of a Dribbble shot (design) by its numeric id or shot URL. Returns title, description, all image and video frames, color palette, tags, view/like/save/comment counts, dimensions, animated/video/multi-shot flags, the author (with team), and the post date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• shot string required — Dribbble shot id or shot URL (examples: "27570377", "https://dribbble.com/shots/27570377-UI-UX-for-a-Analytics-Product-Trise"; minLength: 1)

Response

• @type string (default: "DribbbleShot")
• id integer required
• shot_title string nullable
• description string nullable
• url string nullable
• image string nullable
• media array (default: [])
  • @type string (default: "DribbbleShotMedia")
  • url string required
  • media_type string nullable
  • width integer nullable
  • height integer nullable
• colors array (default: [])
• tags array (default: [])
• view_count integer nullable
• like_count integer nullable
• save_count integer nullable
• comment_count integer nullable
• width integer nullable
• height integer nullable
• is_video boolean (default: false)
• is_animated boolean (default: false)
• is_multi_shot boolean (default: false)
• is_case_study boolean (default: false)
• created_at integer nullable
• author object nullable
  • @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)

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 — Shot not found. Verify the shot id or 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.