Tesla Jobs API Documentation

First request

Endpoint

GET /tesla-jobs/list

Cost

2 credits/request

curl "https://api.crawlora.net/api/v1/tesla-jobs/list?location=Palo+Alto&query=software+engineer" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use Tesla Jobs endpoints

Crawlora's Tesla Jobs endpoints read tesla.com/careers, which publishes its whole global job list as a single dataset. The listing endpoint filters and paginates that snapshot server-side. On 2026-09-18, 2,764 postings matched engineer. Listing rows are deliberately thin: id, title, department, and location. The full job, including compensation text and Tesla's Avature apply link, comes from /tesla-jobs/job. A pull on 2026-10-27 reported 8,281 Tesla jobs at 20 per page, 2,962 of them matching engineer, with the same first row in both lists.

1. Step 1

   Filter by substring, up to 100 per page

   /tesla-jobs/list takes query (matched against title or department), location, page, and page_size up to 100. Both filters are case-insensitive substring matches, so location=texas matches every Texas site.

2. Step 2

   Group by Tesla's departments

   department values are Tesla's own, such as Tesla AI, Engineering & Information Technology, Manufacturing, Energy Engineering, and Energy - Solar & Storage. For engineer, Tesla AI roles for Optimus clustered in Palo Alto, with factory roles in Brookshire, Texas and Grünheide, Germany.

3. Step 3

   Open a posting for the full text

   /tesla-jobs/job adds job_family, state, country, employment_type, description, responsibilities, requirements, compensation_text, and an apply_url on tesla.avature.net, which is Tesla's application system.

4. Step 4

   Expect a warm-up delay

   Tesla sits behind Akamai, so the first request after a cold start renders through a browser and can take noticeably longer. Results are then cached briefly.

5. Step 5

   Size the board before paging

   list returned total 8,281 with page_size 20, and query engineer returned 2,962. Each row has an id, title, department and location, such as SI Engineer, Manipulation, Optimus (id 224501, Tesla SI, Palo Alto, California).

6. Step 6

   Do not rely on query order

   The first row was the same in the unfiltered and engineer-filtered lists, so order follows the board, not relevance. Sort by your own criteria.

Other Business & Market Intelligence APIs