> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/dribbble/profiles-handle-articles>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/dribbble/profiles-handle-articles.mdx>

---

# Dribbble Profile Articles API

The article cards a Dribbble profile has published, as JSON.

`GET /v1/dribbble/profiles/{handle}/articles` returns `data.articles`, the article cards a profile has published. Each card has `title`, `path`, `url`, `blurb`, `publishedAt`, `authorName` and `imageUrl`.

The `path` points at the story on Dribbble. A profile without the Articles tab returns found with an empty list. The list is not page numbered; every article card is returned in one response.

## Request

- **Endpoint:** `GET /v1/dribbble/profiles/{handle}/articles`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by handle
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/dribbble/profiles/handle/articles)
- **Platform page:** [/platforms/dribbble](https://www.socialfetch.dev/platforms/dribbble)

## FAQ

### Are these Dribbble stories?

Yes. Each article card links to a story path, and you can pass that path to GET /v1/dribbble/stories/{slug} to read the body, author, category and view count.

### Why is the articles list empty?

The profile has no Articles tab or has published no articles. A found response with an empty array is the normal answer; a missing profile is not_found with a null lookup.

### Is there paging on the article cards?

No. The route returns the cards on the Articles tab in one response. Use the story route for full article bodies.

### How many credits does a profile articles lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.