> **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/behance/profiles-username-projects>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/behance/profiles-username-projects.mdx>

---

# Behance Profile Projects API

A profile's latest projects as compact rows: identity, summary, cover image and publish date.

`GET /v1/behance/profiles/{username}/projects` returns `data.lookupStatus`, `data.username`, `data.displayName`, `data.projects` and `data.hasMore`. Each project carries `id`, `name`, `url`, `slug`, `summary`, `coverUrl`, `publishedAt` and `nameLossy`.

The list stops at 12 items and exposes no next page. `hasMore` is `false` when fewer than 12 items came back and `null` when the list hit its cap. A name that could not be carried losslessly is repaired from the profile when possible; when it cannot be, `nameLossy` is `true` and the name is returned unchanged. A summary containing `?`, which can stand in for a character that could not be carried, is returned as `null`, never as damaged text. Even one damaged character drops the whole summary, so a genuine question mark is treated the same way; clean summaries are unchanged. A team handle returns its latest projects as `found` rows. A missing handle returns `not_found`, with `projects: []`. Empty is a real result for an account with no projects.

## Request

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

## FAQ

### Does this work for a team?

Yes. A team handle returns its latest projects as found rows, still capped at 12. A missing handle returns lookupStatus: not_found with projects: [].

### How many projects can I get?

At most 12, because that is the list's cap. hasMore is false when fewer than 12 items came back and null when the cap was hit. There is no next page, so there is no cursor to follow.

### What fields does each project have?

Each row carries id, name, url, slug, summary, coverUrl, publishedAt and nameLossy. summary and coverUrl can be null when they are not available. Use the project route with the id for covers, owners, source files and flags.

### What does nameLossy mean?

Some list text cannot carry `?` or non-Latin characters. Names are repaired from the profile when the same project is there. If that is not possible, nameLossy is true and the name is returned unchanged, so you can decide whether to use it. A summary containing `?` is null, even when only one character was affected; a clean summary is unchanged.

### Does an empty project list mean the account is missing?

No. Check lookupStatus first. A found account with no projects returns projects: [] and hasMore: false. Only not_found means the handle does not resolve. A team handle returns found rows.

### How many credits does this 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.