Turn your clients' Workday VNDLY tenants into an API

What you can build on VNDLY

• Get jobs released to you

  Build this

  Reads the Jobs page in one client's VNDLY tenant, filtered by Current Status, with the fields that client shows to vendors.

  Takes

  Client tenant, current status (optional)

  Returns

  Job ID, job title, location, start date, positions, current status

• Check applicant statuses

  Build this

  Opens a job and reads its Applicants tab: each candidate you submitted and the applicant status they are in now.

  Takes

  Client tenant, job ID

  Returns

  Candidate name, Candidate Unique ID, applicant status, bill rate, interview status

• Get timesheet statuses

  Build this

  Reads the Timesheets page for one work period, filtered By Status, for the contractors you place with that client.

  Takes

  Client tenant, date range, status (optional)

  Returns

  Contractor, work period, status, total hours

• Add a candidate

  Build this

  Selects Candidates, then Add a Candidate, uploads the resume, checks the parsed fields, enters the rates and saves the profile.

  Takes

  Client tenant, resume, contact details, years of experience, worker classification, skills, pay rate, markup, bill rate

  Returns

  Candidate name, Candidate Unique ID, saved

Automate VNDLY with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• New jobs from every client, each morning

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  For each client tenant you name, get the jobs released to you.

  Step 2

  Keep the jobs that were not there on the last run.

  Step 3

  Email you the list, one section per client, with job title, location and start date.

• Applicant status changes, posted to your ATS

  Build this

  Starts

  Every weekday at 12:00 and 17:00

  Step 1

  For each open job you name, check the applicant statuses on its Applicants tab.

  Step 2

  Keep the applicants whose status changed since the last run.

  Step 3

  Post each one, with job ID, Candidate Unique ID and new status, to your ATS webhook.

• Missing and rejected timesheets, every Monday

  Build this

  Starts

  Every Monday at 9:00

  Step 1

  For each client tenant, get last week's timesheets with status Unsubmitted or Rejected.

  Step 2

  Stop when there are none.

  Step 3

  Email you the contractors to follow up with, grouped by client.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get jobs released to you” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "yourclient.vndly.com/get_jobs",
    "input": {
      "client_tenant": "yourclient.vndly.com"
    }
  }'

{
  "status": "completed",
  "data": {
    "client": "Acme",
    "jobs": [
      {
        "job_id": "4821",
        "title": "Senior Data Engineer",
        "location": "Remote, US",
        "start_date": "2026-12-01",
        "positions": 2,
        "current_status": "Open"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

VNDLY’s own options

Workday VNDLY lets client and vendor users create API tokens from their own profile, up to 10 active at a time, to connect external systems to VNDLY's APIs. Its Workday connector and invoice APIs are set up by the client for its own systems. Each client decides what vendors see and may upload.

Read on November 12, 2026: Workday VNDLY Administrator Guide (PDF), Concept: Timesheets, Transactional Workday Connector API Requests.

Signing in to VNDLY

Each client runs its own VNDLY tenant at its own address. You sign in there with your username, which is your company email address, and your password; when the client turns on multi-factor authentication, VNDLY also asks for a one-time password from an authenticator app. With Fous you sign in through the tenant's own sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

One tenant per client

Every client has its own VNDLY address, such as yourclient.vndly.com, with its own users. Build each method to take the client tenant as an input, so a workflow can loop over your clients.

Your client decides what you see

Clients choose the job fields vendors see, can hide custom fields from all vendors, and decide whether vendors may view or upload timesheets.

Invoices can come from approved time

Approve sends a timesheet on to invoicing. Some programs generate every invoice automatically from approved time and expense entries, so there is nothing for the vendor to submit.

Unique users, not group emails

Programs can require each username to be a named person's own email address, never a group mailbox. Plan one user per person who signs in.

More in HR: staffing and vendor management

• e-staffing
• Upwork
• ShiftWise Flex
• Bullhorn
• Beeline
• Magnit VMS
• SAP Fieldglass

Other industries: AAH Hub, HealthCare.gov for agents and brokers, CCMS, Customs Declaration Service, LPL ClientWorks, COSCO SHIPPING Lines eBusiness.