/behance/users/following

POST /api/behance/users/following

Price: 5 credits

Get the creatives a Behance user follows

How to use it

Get the creatives a Behance user follows, by alias or URL. 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)
• user string required — Behance user alias (profile handle) or profile URL (examples: "ramotion", "https://www.behance.net/ramotion"; minLength: 1)
• count integer required — Max result count (min: 1)

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 — 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 — Profile not found. Verify the alias or profile 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.