Skip to content

FousSAP Fieldglass

Turn SAP Fieldglass into an API

Read new job postings, job seeker statuses and invoices from SAP Fieldglass with one API call each, or submit a worker's draft time sheet. A workflow can check Work Items each weekday morning and email you the job postings that came in overnight.

Works with your own SAP Fieldglass account. Fous is an independent product.

What you can build on Fieldglass

  • Get job postings waiting for a response

    Build this

    Reads the job postings listed under Respond in Work Items, with each one's Details and Rate Details tabs.

    Takes
    Nothing
    Returns
    Job posting ID, buyer, job title, location, start date, end date, rates, respond-by date, job seekers submitted
  • Check job seeker statuses

    Build this

    Reads the Job Seeker list under the Contingent Labor menu: where each candidate you submitted stands with the buyer.

    Takes
    Job posting ID (optional), status (optional)
    Returns
    Job seeker ID, name, job posting ID, buyer, status, next step, submitted date
  • Get invoices and their statuses

    Build this

    Reads the Invoice list under the Payments menu for a date range, with the time sheet or expense sheet behind each invoice.

    Takes
    From date, to date, status (optional)
    Returns
    Invoice ID, invoice code, buyer, worker, time sheet or expense sheet ID, status, amount, submitted date
  • Submit a worker's draft time sheet

    Build this

    Opens the worker's time sheet on the Draft Time Sheets tab, enters the hours for the period and submits it for the buyer's approval.

    Takes
    Worker name, period end date, hours per day
    Returns
    Time sheet ID, worker, period, total hours, status

Automate Fieldglass 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 job postings in your inbox before 8:00

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    Get the job postings waiting for a response in Work Items.
    Step 2
    Keep the job postings that were not there on the last run.
    Step 3
    Email you each one with its buyer, title, location, dates, rates and respond-by date.
  • Job seeker status changes, posted to your ATS

    Build this
    Starts
    Every hour on weekdays
    Step 1
    Check the statuses of all job seekers you have submitted.
    Step 2
    Keep the job seekers whose status changed since the last run.
    Step 3
    Post each one, with its old and new status and next step, to your applicant tracking system's webhook.
  • Invoice status changes, handed to your accounting system

    Build this
    Starts
    Every day at 18:00
    Step 1
    Get the invoices from the last 60 days with their statuses.
    Step 2
    Keep the invoices whose status changed since the last run, such as to Rejected, Payment Review or Paid, and stop if none did.
    Step 3
    Post invoice ID, invoice code, buyer, worker, amount and new status to your accounting system's webhook.

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 job postings waiting for a response” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "www.us.fieldglass.cloud.sap/get_job_postings",
    "input": {}
  }'
Example response
{
  "status": "completed",
  "data": {
    "job_postings": [
      {
        "job_posting_id": "ACMEJP00000412",
        "buyer": "Acme",
        "job_title": "Senior Java Developer",
        "location": "Chicago, IL",
        "start_date": "2026-12-01",
        "end_date": "2027-05-28",
        "rates": "Bill rate up to 95.00 USD/hr",
        "respond_by": "2026-11-14",
        "job_seekers_submitted": 0
      }
    ],
    "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.

Fieldglass’s own options

SAP documents supplier connectors that download job postings, time sheets and invoices, and upload job seekers, time sheets and work order acceptances. A Configuration Manager user enables them in the Connector Catalog. A REST API for talent channel systems needs a client-specific application key and your SAP Fieldglass implementation representative.

OptionWhat it coversWhat it takes
Supplier connectorsJob postings (XML or JSON), time sheets (CSV), invoices (XML, CSV or JSON) and worker data out; job seekers, time sheets and work order acceptances in.A Configuration Manager user created by your supplier administrator, and each connector enabled in the Connector Wizard. Runs on a schedule or by hand.
REST API for talent channelsJob Posting, Job Seeker, Worker, Time Sheet, Invoicing and Interview, for contingent labor only.Set up with SAP's implementation representative for each buyer: buyer and supplier tenant codes, your endpoint and a client-specific application key.
Fieldglass by handWork Items, the Contingent Labor, Worker and Payments menus, and predefined reports under Analytics, for one buyer's instance at a time.An account created after a buyer invites you and your company signs the Supplier Access Agreement.

Read on November 12, 2026: SAP Fieldglass Supplier Integration Enablement, Configuration Guide for SAP Fieldglass REST API and Freelance Management System Integration, Supplier Workflows for Contingent and Services.

Signing in to Fieldglass

Fieldglass signs suppliers in with a username and password at the address for the buyer's data center: www.us.fieldglass.cloud.sap or the EU one. With two-factor authentication on, a one-time passcode goes to the email on your profile. With Fous you sign in once through Fieldglass's own sign-in: the login is sealed with AES-256, emailed passcodes are handled, and an expired session is signed back in.

Worth knowing

One buyer, one instance
Each buyer program is its own Fieldglass instance. Linked user accounts let you switch between them without signing out, and reporting across your supplier tenants needs SAP Fieldglass to link them.
Invoices are made one of two ways
With Auto Invoicing On, an approved time sheet becomes an invoice by itself. With it off, you create invoices in the Invoice Generator, only against the invoice billing schedule the buyer assigned you.
An invoiced time sheet cannot be changed
Once a time sheet is submitted, approved and invoiced, it cannot be rejected or adjusted. A correction goes in as a revised time sheet, and the system creates a reversal time sheet for the original.
Payment happens outside Fieldglass
Fieldglass is not an accounts payable application, so payment questions go to the buyer's company. An approved invoice shows Payment Review until it is paid, then Paid.

More in HR: staffing and vendor management

Other industries: Henry Schein online ordering, Covered California Enroller Portal, Arbitration Forums, Dubai Trade, Nest employer account, CMA CGM eBusiness.

Frequently asked questions

Yes, in two forms. Supplier connectors download job postings, time sheets and invoices and upload job seekers and time sheets, once a Configuration Manager user enables them. A REST API for talent channel systems is set up per buyer with SAP's implementation representative and a client-specific application key.

Not in one list. Each buyer is a separate Fieldglass instance, and linked user accounts only let you switch between them. With Fous, a workflow can run the same method for each of your Fieldglass accounts on a schedule and send you one email or one webhook post.

They show where a candidate stands with the buyer: Submitted, Shortlisted, Interviewed or Rejected, then Work Order Created, Work Order Accepted, Work Order Activated and Work Order Confirmed. Closed and Withdrawn end a candidacy. While the buyer approves a work order, you still see Shortlisted.

Yes, through its status. An invoice moves from Pending Approval to Approved, shows Payment Review while it is approved but not paid, and Paid once paid. Fieldglass is not an accounts payable application, and SAP's guide sends payment questions to the buyer's company.

No. Fous is an independent product. You use it with your own SAP Fieldglass account, and a method reads and does only what that account can.

Put SAP Fieldglass behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextWorkday VNDLYe-staffingUpworkHenry Schein online orderingHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of SAP Fieldglass (SAP). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.