# /behance/users/search

`POST /api/behance/users/search`

Price: 5 credits

Search Behance creatives (people)

## How to use it

Search Behance creatives (people) by keyword, order the results, and filter by creative field, availability, and location. Returns creative cards with alias, display name, location, avatar, follower/appreciation/view counts, and availability.

## 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: "branding"; minLength: 1)
- `sort` (string) — Result ordering (default: "Recommended"; one of: "Recommended", "Most Followed", "Curated", "Most Appreciated", "Most Viewed", "Most Recent")
- `creative_field` (string, nullable) — Filter by creative field (one of: "3D Art", "3D Modeling", "3D Motion", "Advertising", "Advertising Photography", "Animation", "App Design", "Apparel", "AR/VR", "Architecture", "Architecture Concept", "Architecture Photography", "Architecture Visualization", "Art Direction", "Automotive Design", "Beauty Photography", "Branding", "Calligraphy", "CGI", "Character Design", "Cinematography", "Collage", "Coloring", "Comic", "Concept Art", "Copywriting", "Costume Design", "Crafts", "Creative Direction", "Culinary Arts", "Digital Art", "Digital Painting", "Directing", "Drawing", "Editing", "Editorial Design", "Education", "Environmental Graphics", "Exhibition Design", "Fashion", "Fashion Design", "Fashion Illustration", "Fashion Photography", "Fashion Retouching", "Fashion Styling", "Film", "Fine Arts", "Flower Arrangement", "Food Photography", "Food Styling", "Furniture Design", "Game Design", "GIF Animation", "Graffiti", "Graphic Design", "Icon Design", "Illustration", "Industrial Design", "Infographic", "Information Architecture", "Interaction Design", "Interior Design", "Jewelry Design", "Label Design", "Landscape Design", "Lettering", "Logo Design", "Makeup", "Makeup Arts", "Model Test Photography", "Modeling", "Motion Graphics", "Music", "Music Packaging", "Packaging", "Painting", "Paperworks", "Pattern Design", "Performing Arts", "Photography", "Photography Styling", "Photojournalism", "Poster Design", "Product Design", "Product Photography", "Programming", "Projection Mapping", "Props Design", "Retouching", "Sculpting", "Set Design", "Shoe Design", "Sketching", "Sound Design", "Storyboarding", "Street Art", "Styleframing", "Surface Design", "T-Shirt Design", "Textile Design", "Toy Design", "Type Design", "Typography", "UI/UX", "Visual Effects", "Visualization", "Web Design", "Window Design", "Woodworking", "Writing")
- `availability` (string, nullable) — Filter by what the creative is available for (one of: "Freelance", "Full-time")
- `country` (string, nullable) — Filter by country (ISO code) (examples: "US")
- `state` (string, nullable) — Filter by state/region
- `city` (string, nullable) — Filter by city
- `count` (integer, required) — Max result count (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "BehanceUserBrief")
- `id` (integer, required)
- `alias` (string, nullable)
- `display_name` (string, nullable)
- `first_name` (string, nullable)
- `url` (string, nullable)
- `image` (string, nullable)
- `is_creator_pro` (boolean) (default: false)
- `is_featured_freelancer` (boolean) (default: false)
- `is_available_freelance` (boolean) (default: false)
- `is_available_full_time` (boolean) (default: false)
- `is_verified_on_linkedin` (boolean) (default: false)
- `location` (string, nullable)
- `city` (string, nullable)
- `state` (string, nullable)
- `country` (string, nullable)
- `company` (string, nullable)
- `follower_count` (integer, nullable)
- `appreciation_count` (integer, nullable)
- `view_count` (integer, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.