PeoplePerHour freelance projects

GET https://api.api.sh/peopleperhour/v1/jobs
1 credit / call jobs & b2b try it in the playground →

Open freelance projects on PeoplePerHour by category, subcategory or skill, with the site's filters (experience level, fixed or hourly pricing, urgent, no proposals yet, pre-funded, featured, opportunity, remote or on-site) and sort orders. Each project has the title, category, budget with currency and a USD estimate, pricing, proposals count, flags, dates, description and the client's country and member-since date (clients are private people; no names). facets gives counts per category, subcategory and filter. 20 per page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
category string Category slug, optionally with a subcategory: technology-programming, design, writing-translation, digital-marketing, business, video-photo-image, marketing-branding-sales, social-media, music-audio, artificial-intelligence (e.g. technology-programming/website-development). Example: technology-programming
skill string A skill page instead of a category (e.g. python, wordpress, logo-design).
experience string Experience levels, comma separated: entry, intermediate, expert.
pricing fixed_price | hourly Pricing.
type string Project types, comma separated: urgent, no_proposals, prefunded, featured, opportunity.
location remote | onsite Remote or on-site projects.
sort relevance | popularity | latest | ending | budget Sort order.
page string Results page (1-based). Pass next_page back; it is null on the last page.

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

Example

curl "https://api.api.sh/peopleperhour/v1/jobs?category=technology-programming" \
  -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.