PeoplePerHour API · unofficial, by Cotlet

Create your own PeoplePerHour API

PeoplePerHour: no public API or developer docs found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your PeoplePerHour account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in PeoplePerHour session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by PeoplePerHour. PeoplePerHour is a trademark of its owner. If PeoplePerHour's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/new-projects" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"category": "Logo design", "min_budget": 300}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/new-projects";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ category: "Logo design", min_budget: 300 }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/new-projects",
    headers={"Authorization": f"Bearer {key}"},
    json={"category": "Logo design", "min_budget": 300},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "posted": "08:40",
      "title": "Logo for a coffee roaster",
      "budget": "450",
      "proposals": 7
    },
    {
      "posted": "10:15",
      "title": "Rebrand for a dental clinic",
      "budget": "800",
      "proposals": 12
    }
  ]
}

01 Build

How do you build a PeoplePerHour endpoint with Cotlet?

  1. Sign in to PeoplePerHour in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List today's new projects in this category with the title, budget and number of proposals so far."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a category or a budget, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in PeoplePerHour session.

02 Endpoints

Example endpoints you could build for PeoplePerHour

Cotlet ships no fixed list of PeoplePerHour endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/new-projects

    New projects

    Title, budget and proposals so far for each new project in a category

  • POST /api/v1/custom/waiting-messages

    Messages waiting

    Buyers waiting for your reply, with the time of their last message

  • POST /api/v1/custom/proposals-status

    Proposal status

    Your recent proposals and whether the buyer answered

  • POST /api/v1/custom/earnings

    Earnings

    Earned, held and withdrawn amounts for a period

  • POST /api/v1/custom/save-search writes

    Save a search

    A saved project search for the category and budget you name

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/new-projects" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"category": "Logo design", "min_budget": 300}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "posted": "08:40",
      "title": "Logo for a coffee roaster",
      "budget": "450",
      "proposals": 7
    },
    {
      "posted": "10:15",
      "title": "Rebrand for a dental clinic",
      "budget": "800",
      "proposals": 12
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your PeoplePerHour endpoints for?

  • Schedule Cotlet endpoint Slack or SMS

    Project alerts in n8n or Make.

    New projects that match your skills, sent to Slack or your phone every hour.

  • Schedule endpoint Google Sheets

    A pipeline in a sheet.

    Proposals sent and answered, pulled into Google Sheets each week.

  • Schedule endpoint earnings

    Books for your accountant.

    Monthly earnings pulled into your bookkeeping sheet.

  • AI agent endpoint new projects

    Your own proposal assistant.

    An AI agent that reads new briefs before it drafts proposals for you.

04 Access

What can an endpoint see and change?

An endpoint works in your own PeoplePerHour session, so it can read and change only what your PeoplePerHour login can. You choose what each endpoint does when you build it.

An endpoint that changes something, such as saving a search, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does PeoplePerHour have an official API?

PeoplePerHour: no API, developer docs or API keys found on peopleperhour.com (checked 20 Nov 2026). Transactions can be exported from Payments. The full picture with sources: Does PeoplePerHour have an API or MCP server?

Want ChatGPT or Claude to work in PeoplePerHour instead of code? See the PeoplePerHour MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

PeoplePerHour API with Cotlet: questions

Is this an official PeoplePerHour API?

No. Cotlet is independent and not affiliated with PeoplePerHour. The endpoints you build run in your own signed-in PeoplePerHour account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when PeoplePerHour changes its screens?

An endpoint works while PeoplePerHour works the way it did when you built it. If PeoplePerHour changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first PeoplePerHour endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.