Dribbble shot

GET https://api.api.sh/dribbble/v1/shot
1 credit / call content & communities try it in the playground →

One Dribbble shot: title, description, posted date, likes, views, saves, comments, tags, main image, every media item (images and videos with sizes), animated/video/case-study flags and the designer (username, name, avatar, id, team flag). Also the colour palette (hex), attachment count, tag links and whether the designer is available for hire. include adds sections read from further pages: comments (the first page of comments with text, likes, age and author, and comments_pages), more_by (more shots by the designer) and similar (similar shots); each adds a page read.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
id string Shot id (or pass url). Example: 27010663
url string A dribbble.com /shots/ link, instead of id.
include string Extra sections, comma-separated: comments, more_by, similar. Each one reads one more page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/dribbble/v1/shot?id=27010663" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.