Docs menu

Upwork API endpoint

Upwork search API

Searches Upwork's public job listings by free-text keyword, returning job summaries (title, budget, experience level, duration, posted date, description snippet, skill tags).

GETapiKey5 credits/requestUpworkupwork.searchResponseDoc/upwork/search

Endpoint facts

Method: GET
API path: /upwork/search
Auth: apiKey
Credits: 5 credits/request
Charged on: Successful 2xx responses only
Platform: Upwork
Execution: Managed browser rendering where the target needs it
Response schema: #/definitions/upwork.searchResponseDoc

Upwork Scraper API Try Upwork search API in Playground Upwork API documentation

How this endpoint behaves

Query parameters:

q (required) — free-text job search keyword.
page (optional) — 1-based result page. Defaults to 1.

Notable response behavior:

id is Upwork's own opaque job identifier (the digits after ~ in the job's URL) — pass it directly as the id path parameter to GET /upwork/job/{id} for full job detail.
budget_type is hourly or fixed, inferred from the search card's own budget label text; it is omitted when the label doesn't match either pattern.
duration and experience_level are omitted when Upwork doesn't render them for a given posting (e.g. some fixed-price jobs omit duration).
A genuine zero-result search (Upwork's own "There are no results that match your search" page) returns jobs: [] with a 200, distinct from a parser-drift or blocked-page failure, which returns an error instead.

Live monitoring

Monitored request: GET /upwork/search?q=python+developer
Checks passed, 7 days to 14 Oct 2026: 99.9%
Median response time: 22.35 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /upwork/search?q=python+developer
Items in jobs: 10
Fields filled in every checked item: 9
Fields empty in some or all items: 1

Field	Filled in, of 10 checked	Values in the sample
id	10
title	10
url	10	upwork.com
description	10	median 1,630 characters
posted_at	10
budget_type	10
budget_text	10
experience_level	10
skills	10	median 5 entries
duration	5

Request parameters

Parameter	Type	Required	Default	Description	Example
q	string	Yes		Free-text job search keyword	python developer
page	integer	No	1	1-based result page. Defaults to 1.	2
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/upwork/search?q=python+developer&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "query": "python developer",
    "page": 1,
    "jobs": [
      {
        "id": "2085006288356888767",
        "title": "Python full stack developer, python automation",
        "url": "https://www.upwork.com/jobs/span-class-highlight-Python-span-full-stack-developer_~022085006288356888767/",
        "description": "We are seeking a python full stack developer to join our team...",
        "posted_at": "Posted 2 days ago",
        "budget_type": "hourly",
        "budget_text": "Hourly: $60.00 - $75.00",
        "experience_level": "Expert",
        "duration": "1 to 3 months, 30+ hrs/week",
        "skills": [
          "Python",
          "Django",
          "Flask"
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/upwork.searchResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	upwork.SearchResponse	No
data.jobs	array	No
data.jobs[].budget_text	string	No
data.jobs[].budget_type	string	No		"hourly" or "fixed"
data.jobs[].description	string	No
data.jobs[].duration	string	No
data.jobs[].experience_level	string	No
data.jobs[].id	string	No		ID is Upwork's own opaque job identifier (the digits after "~" in the job's URL), suitable for Service.Job.
data.jobs[].posted_at	string	No
data.jobs[].skills	array	No
data.jobs[].title	string	No
data.jobs[].url	string	No
data.page	integer	No
data.query	string	No
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/upwork/search?q=python+developer&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More Upwork endpoint docs Upwork Scraper API Upwork freelancer API documentation Upwork job API documentation

Open in Playground Back to group

Docs menu

Upwork API endpoint

Upwork search API

Searches Upwork's public job listings by free-text keyword, returning job summaries (title, budget, experience level, duration, posted date, description snippet, skill tags).

GETapiKey5 credits/requestUpworkupwork.searchResponseDoc/upwork/search

Endpoint facts

Method: GET
API path: /upwork/search
Auth: apiKey
Credits: 5 credits/request
Charged on: Successful 2xx responses only
Platform: Upwork
Execution: Managed browser rendering where the target needs it
Response schema: #/definitions/upwork.searchResponseDoc

Upwork Scraper API Try Upwork search API in Playground Upwork API documentation

How this endpoint behaves

Query parameters:

q (required) — free-text job search keyword.
page (optional) — 1-based result page. Defaults to 1.

Notable response behavior:

id is Upwork's own opaque job identifier (the digits after ~ in the job's URL) — pass it directly as the id path parameter to GET /upwork/job/{id} for full job detail.
budget_type is hourly or fixed, inferred from the search card's own budget label text; it is omitted when the label doesn't match either pattern.
duration and experience_level are omitted when Upwork doesn't render them for a given posting (e.g. some fixed-price jobs omit duration).
A genuine zero-result search (Upwork's own "There are no results that match your search" page) returns jobs: [] with a 200, distinct from a parser-drift or blocked-page failure, which returns an error instead.

Live monitoring

Monitored request: GET /upwork/search?q=python+developer
Checks passed, 7 days to 14 Oct 2026: 99.9%
Median response time: 22.35 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /upwork/search?q=python+developer
Items in jobs: 10
Fields filled in every checked item: 9
Fields empty in some or all items: 1

Field	Filled in, of 10 checked	Values in the sample
id	10
title	10
url	10	upwork.com
description	10	median 1,630 characters
posted_at	10
budget_type	10
budget_text	10
experience_level	10
skills	10	median 5 entries
duration	5

Request parameters

Parameter	Type	Required	Default	Description	Example
q	string	Yes		Free-text job search keyword	python developer
page	integer	No	1	1-based result page. Defaults to 1.	2
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/upwork/search?q=python+developer&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "query": "python developer",
    "page": 1,
    "jobs": [
      {
        "id": "2085006288356888767",
        "title": "Python full stack developer, python automation",
        "url": "https://www.upwork.com/jobs/span-class-highlight-Python-span-full-stack-developer_~022085006288356888767/",
        "description": "We are seeking a python full stack developer to join our team...",
        "posted_at": "Posted 2 days ago",
        "budget_type": "hourly",
        "budget_text": "Hourly: $60.00 - $75.00",
        "experience_level": "Expert",
        "duration": "1 to 3 months, 30+ hrs/week",
        "skills": [
          "Python",
          "Django",
          "Flask"
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/upwork.searchResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	upwork.SearchResponse	No
data.jobs	array	No
data.jobs[].budget_text	string	No
data.jobs[].budget_type	string	No		"hourly" or "fixed"
data.jobs[].description	string	No
data.jobs[].duration	string	No
data.jobs[].experience_level	string	No
data.jobs[].id	string	No		ID is Upwork's own opaque job identifier (the digits after "~" in the job's URL), suitable for Service.Job.
data.jobs[].posted_at	string	No
data.jobs[].skills	array	No
data.jobs[].title	string	No
data.jobs[].url	string	No
data.page	integer	No
data.query	string	No
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/upwork/search?q=python+developer&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More Upwork endpoint docs Upwork Scraper API Upwork freelancer API documentation Upwork job API documentation

Open in Playground Back to group

Upwork search API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

Upwork search API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related