Partner API

Send your staff email + password (the ones you use on this website). Optional label names the token. Returns token, its lifetime, your role, and the exact pages the token may reach. The same lockout rules as the website apply to wrong passwords.

TOKEN=$(curl -s -X POST https://teepwork.com/api/staff/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "job@teepwork.com",
    "password": "your-staff-password",
    "label": "Mycorra portal"
  }' | php -r 'echo json_decode(stream_get_contents(STDIN), true)["token"];')

echo "$TOKEN"   # store this server-side; reuse it on every call below

Success → {"ok":true,"token":"…","token_type":"Bearer","expires_in_days":30,"staff":{…},"pages":["dashboard","businesses","post-work","qa-review","work-log","edit-work-unit"]}. The pages list is your tab list.

Confirms the token is still valid and lists the tabs it may call. A good first call after startup — a 401 means log in again.

curl https://teepwork.com/api/staff/me -H "Authorization: Bearer $TOKEN"

Your notification feed, newest first, with the unread count. Each item carries an absolute link to the place it refers to. Params: page, per_page (max 100).

curl "https://teepwork.com/api/staff/notifications?per_page=20" -H "Authorization: Bearer $TOKEN"

Revokes only the token you send — retiring one integration never logs the team out of the website or other tokens. Log in again (endpoint 1) to get a new one.

curl -X POST https://teepwork.com/api/staff/logout -H "Authorization: Bearer $TOKEN"

Returns jobs_posted, active_jobs, awaiting_teep (in the work pool), delivered_this_week, avg_business_rating_out_of_5, repeat_business_rate_pct, acceptance_queue, jobs_by_status (count + label per status) and trend_last_8_weeks.

curl https://teepwork.com/api/staff/dashboard -H "Authorization: Bearer $TOKEN"

Every business, newest first, with tier, status, work-order count and its order_code. If a business has no username yet, it is created on this call, exactly as the website's "Copy link" does. Filters: q (company, contact or email), status (pending|active|paused|offboarded), tier (starter|growth|pro), page, per_page (max 100).

curl "https://teepwork.com/api/staff/businesses?q=skincare&status=active" -H "Authorization: Bearer $TOKEN"

Creates a business (status: active), queues its welcome email, and returns the new business_id, its order_code (username) and order_link at once. Required: company_name, contact_name, email. Optional: phone, membership_tier (starter|growth|pro, default starter).

curl -X POST https://teepwork.com/api/staff/business-create \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{
    "company_name": "Acme Skincare",
    "contact_name": "Jane Smith",
    "email": "jane@acme.com",
    "phone": "+1 555 0100",
    "membership_tier": "growth"
  }'

Two editable fields only. field=membership_tier → starter|growth|pro; field=status → pending|active|paused|offboarded. Anything else is rejected.

curl -X POST https://teepwork.com/api/staff/business-update \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"business_id": 12, "field": "status", "value": "paused"}'

The same credentials the website button gives. action=get (default) returns the order_code and a ready-to-share order_link. action=regenerate rotates the secret and keeps the username, so printed material keeps working; any previously shared link stops working.

curl -X POST https://teepwork.com/api/staff/business-order-link \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"business_id": 12, "action": "get"}'

The order_link skips the username step, so treat it as a secret. The bare order_code is what you give the business.

The shared category list with ids. Fetch it once and cache it. You may skip it and send skill_name instead — a known name is reused, an unknown one is created.

curl https://teepwork.com/api/staff/skill-categories -H "Authorization: Bearer $TOKEN"

Posts for any business as available_pool, visible to workers at once. Required: business_id, title, description, estimated_hours, and a category: skill_category_id, skill_name, or skill_category_id=other with new_skill_name. Optional brief fields: business_need, work_requested, deliverables, required_capabilities, quality_criteria, completion_standard, instructions, revision_policy, expected_output, training_video_url, video_visibility (assigned_only|matched_preview|public_preview), complexity_tier (bronze|silver|gold), capability_level (L1–L4, or CUSTOM with custom_level_label and custom_capacity_rate_usd), estimated_work_units, workers_needed, deadline (YYYY-MM-DD HH:MM:SS).

curl -X POST https://teepwork.com/api/staff/post-work \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{
    "business_id": 12,
    "skill_name": "Market Research",
    "title": "Competitor pricing research for our skincare line",
    "description": "Compare 5 competing brands on price, positioning and reviews.",
    "deliverables": "One spreadsheet with 5 competitors plus a 1-page summary",
    "complexity_tier": "bronze",
    "capability_level": "L2",
    "estimated_hours": 4,
    "estimated_work_units": 2,
    "workers_needed": 1,
    "deadline": "2026-11-30 17:00:00"
  }'

Response: work_unit_id, status, capability_level, capacity_rate_usd, message. The capacity rate is the amount TEEP WORK pays per accepted unit; it is computed on the server.

Every field of the form, whether it is required, what to write, and a placeholder example. The response is the file itself: format=pdf (A4) or format=csv (opens in Excel).

curl -o "Post-a-job guide.pdf" "https://teepwork.com/api/staff/post-guide?format=pdf" -H "Authorization: Bearer $TOKEN"

Each waiting delivery with its deliverable link (file_url opens directly), revision number, business and brief context, deadline and on_time, the timing label, milestones (done of total), and help_ticket_open. If a help ticket is open, approval is paused until the coordinator mediates it, so read this before you decide.

curl https://teepwork.com/api/staff/acceptance-queue -H "Authorization: Bearer $TOKEN"

Decide on a submission from the queue. decision = approved (marks the job delivered once every slot is in, releases worker pay, and closes the job), revision_requested (sends it back to the worker), or rejected (removes that worker; the job reopens if no slots remain). Add notes for the record.

curl -X POST https://teepwork.com/api/staff/acceptance-decision \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"submission_id": 88, "decision": "approved", "notes": "Meets the brief."}'

Approval returns 409 while a help ticket is open. Revisions and rejections still work. A token can never record the TEEP WORK first-pass review, so the two-layer model holds.

Your quality rating on a delivery waiting in your queue. It is saved on the Mycorra layer, and the worker sees only the stars, never who rated them. Only assignment_id values from the queue are accepted; anything else returns 409.

curl -X POST https://teepwork.com/api/staff/rate-delivery \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"assignment_id": 42, "stars": 5, "comment": "Accurate and well sourced."}'

Both documents as JSON: document_1_posted_jobs (count, units, value, rows) and document_2_completed_works (count, capacity, worker pay, by_worker rollup, rows). Defaults to the current month.

curl "https://teepwork.com/api/staff/work-log?month=2026-10" -H "Authorization: Bearer $TOKEN"

The three PDFs, one per document: doc=posted (Document 1), doc=completed (Document 2), doc=workers (Document 3). The response is the PDF file.

curl -o "work-log-2026-10.pdf" "https://teepwork.com/api/staff/work-log-pdf?doc=completed&month=2026-10" -H "Authorization: Bearer $TOKEN"

The jobs that can still be edited: in the pool, assigned, or paused. Pass a comma-separated status list. Also filter by business_id or search with q; paginate with page and per_page. Each row includes the business order_code.

curl "https://teepwork.com/api/staff/jobs?status=available_pool,assigned,paused" -H "Authorization: Bearer $TOKEN"

The full brief, scoping (level, hours, units, live capacity), staffing counts, deadline, whether it is still editable, and its status_history. Worker names are not shown here. Listed (talent-facing) pay is shown only to superadmin accounts, as on the website.

curl "https://teepwork.com/api/staff/job-detail?work_unit_id=42" -H "Authorization: Bearer $TOKEN"

Send work_unit_id plus the fields to change (same names as Post a job). Three safeguards match the website: only pool, assigned or paused jobs can be edited (409 otherwise); workers_needed cannot drop below the slots already filled; and once a slot is filled the capacity is frozen, so level, hours, units, rate type and custom rate are refused. Editing an assigned job notifies its worker.

curl -X POST https://teepwork.com/api/staff/edit-work-unit \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{
    "work_unit_id": 42,
    "title": "Competitor pricing research (revised scope)",
    "description": "Compare 8 competing brands on price, positioning and reviews.",
    "complexity_tier": "bronze",
    "capability_level": "L2",
    "rate_type": "fixed",
    "estimated_hours": 4,
    "estimated_work_units": 2,
    "workers_needed": 1,
    "deadline": "2026-12-05 17:00:00"
  }'

Orders a business has submitted and that are still Received — Mycorra is reviewing it. Accounts without the Work orders tab get 403 for these statuses.

curl "https://teepwork.com/api/staff/jobs?status=submitted" -H "Authorization: Bearer $TOKEN"

Corrects an order that is still Received. Send work_unit_id plus only the fields to change: title (8+ characters), description (20+), deliverables, skill_category_id or skill_name, workers_needed (1–20), deadline (empty clears it), submitter_name, submitter_contact. Past review, use Save a job edit.

curl -X POST https://teepwork.com/api/staff/update-submitted-order \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"work_unit_id": 42, "workers_needed": 2, "deadline": "2026-12-15 17:00:00"}'

Withdraws an order that is still Received — for example a duplicate, or a business that changed its mind. It is removed before any worker sees it. Orders past review return 409 and are unwound on the website.

curl -X POST https://teepwork.com/api/staff/cancel-job \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"work_unit_id": 42}'

Records the business's rating for a delivered job. It closes the job (delivered → closed) and feeds the rating into each worker's trust score. One rating per job: resending the same rating is safe; a different one returns 409.

curl -X POST https://teepwork.com/api/staff/job-feedback \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"job_id": 42, "rating": 5, "comments": "Thorough, delivered a day early."}'