API & custom integration

Connect internal apps to worker pay with custom API integrations

Connect your internal apps to Wingspan with the Custom API integration. Sync worker records, assignments, and approved work. Worker types include Contractor and W-2. Contractor pay uses invoices and payables. W-2 pay uses pay statements and employee payroll runs. Read check and payment status in your own tools.

Custom API icon Your apps
Wingspan

Connect your apps to worker workflows

  • Your apps

    Worker roster

    Wingspan

    Worker records (payees)

  • Your apps

    Work templates

    Wingspan

    Engagement templates

  • Your apps

    Job assignments

    Wingspan

    Assignments (payee engagements)

Choose which records sync and when they move. Your team stays in control of work review and payment approval.

Automate worker onboarding and required checks

Sync selected worker records from your app to Wingspan with their Contractor or W-2 type. An invite starts onboarding, and workers complete the forms for their type. Your app reads check status and readiness for the linked assignments.

Review work logs and manage bills you owe

Send approved contractor hours, tasks, or shifts to Wingspan work logs. Approving a log creates one amount owed. The contractor sees an invoice. Your team sees a payable. Finance gives separate payment approval. Known amounts also enter as direct payables. Use one path for each cost.

Track worker payment progress

Read payment status and references in your own app. Your team tracks pay in transit, paid records, and returns. Deposit confirmation means the sending bank finished processing. It does not prove the worker's bank posted funds.

How your apps work with Wingspan

Your internal apps track daily work and client projects. The Custom API integration links those records with Wingspan. Each Wingspan worker record is called a payee. Worker types include Contractor and W-2.

An engagement is a reusable work template. It sets rates, work rules, and required checks. Each assignment links one worker to that template. Check status and review rules determine readiness for the attached assignments.

Contractor work entries fill work logs. Approving a log creates one amount owed. The contractor sees an invoice. Your team sees a payable. Finance gives separate payment approval. W-2 workers receive pay statements through employee payroll runs with taxes withheld.

Client invoices bill your clients. They stay separate from worker pay. Your tools read payment status and funds movement references. Deposit confirmation means the sending bank finished processing. It does not prove the worker's bank posted funds.

Start with the records you already use

Worker roster
A list of worker records. It tracks names, roles, and worker types.
Work templates
A shared work scope. It sets rates and required checks.
Job assignments
A job record for one worker. It tracks dates and tasks.
Work entries
A work entry for hours, tasks, shifts, or units.
Worker bills
A bill for contractor work. It shows what you owe.
Client bills
A bill sent to a client for finished services.
Pay status
A payment status record. It tracks progress and references for your books.
Tax summaries
A yearly tax total. It tracks earnings and form status.

Sync options

Choose which tool holds each record. Set the changes that sync between them. Connect your records to the Wingspan workflows below.

Worker roster

Worker records (payees)

Your apps to Wingspan

Selected worker profiles sync to Wingspan worker records. Each record is called a payee. Keep the chosen Contractor or W-2 type. Creating a record and sending an invite are separate steps. Payment setup and required checks stay separate from record creation. Creating a worker does not approve payment.

Work templates

Engagement templates

Your apps to Wingspan

Project scopes in your app map to reusable work templates in Wingspan. An engagement is a work template. Each template sets default rates, work rules, and required checks. Your team sets checks for each template. This keeps job terms clear.

Job assignments

Assignments (payee engagements)

In both directions

Worker placements sync to Wingspan assignments. Each assignment links one worker to an engagement template. It keeps its own dates and terms. Your app reads readiness for the assignments your team selects. One completed check does not clear every assignment.

Work entries

Work logs and work items

Your apps to Wingspan

Approved contractor hours, shifts, and tasks fill work items in Wingspan. A work log groups entries for one assignment. Agreed rates set the amount. Approving the log creates one amount owed. The contractor sees an invoice. Your team sees a payable. Finance gives separate payment approval.

Worker bills

Payables

In both directions

Known contractor amounts create direct payables in Wingspan. Work logs supply another path. Choose one path for each cost. The contractor sees an invoice. Your team sees a payable. These are two views of one amount owed. Finance gives separate payment approval before money moves.

Client bills

Client invoices

Your apps to Wingspan

Client billing events supply Wingspan client invoices. Each bill links to a client payer and client engagement. Client billing stays separate from contractor payables and W-2 payroll. Finance reviews collections and worker pay separately. Client payment does not release worker pay on its own.

Pay status

Payment status and references

Wingspan to Your apps

Your app reads Wingspan payment status and funds movement references. Paid is the payment record in Wingspan. Deposit confirmation means the sending bank finished processing. It does not prove the worker’s bank posted funds. Payments can still return. Finance matches the references to bank activity.

Tax summaries

Tax information

Reference or reporting

Tax readiness flags and yearly totals sync to your reporting tools. Syncing a summary does not submit a tax filing to the government.

Required checks and check status

Requirement definitions and requirements

In both directions

Reusable check definitions set the rules in Wingspan. Your app links checks to the selected work templates. Check results and review decisions stay distinct. A requirement can serve several attached assignments. Your app reads check status and payment readiness for those assignments. Readiness does not give payment approval.

Integration workflows

01

Worker onboarding and assignment readiness

Your team creates a new worker profile and links a placement.

Your app sends selected worker details to Wingspan. Each worker keeps their Contractor or W-2 type. An invite starts onboarding. The assignment links the worker to an engagement template. Checks follow your review rules. Your app reads check status and readiness for that assignment. Completing one check does not clear every job.

02

Approved operational work to contractor payable

A field lead approves finished contractor work in your app.

Approved contractor work details fill a Wingspan work log. Agreed rates set the amount. Approving the log creates one amount owed. The contractor sees an invoice. Your team sees a payable. Finance gives separate payment approval. A contractor payroll run pays approved payables. Your app reads payment status and references.

03

Client billing and linked contractor pay

Your team completes a client project.

Your billing app supplies a Wingspan client invoice. The invoice links to the client payer and client engagement. Worker costs use their own assignments. Contractor payables and W-2 payroll follow separate pay paths. Finance reviews client billing and worker pay separately. Shared references help your team compare income and costs.

Plan your integration

Worker classification and pay path separation

Decide how your tools separate contractor and W-2 workers. The worker record in Wingspan holds the chosen type. Contractor pay uses invoices and bills you owe. W-2 workers use pay statements and payroll runs with taxes withheld. Keep these two pay tracks separate.

Work approval versus payment authorization

Decide who reviews work and who approves pay. Approving a work log sets the amount owed. Payment needs a separate sign-off from finance. Finance approves pay before money moves. Keeping these steps separate protects your money.

Choose the status and references your apps read

Choose the records, status, and references your internal apps read. Shared IDs match updates to the right workers and assignments. Check the latest record state when an event arrives. Set access by role for private records.

How the worker lifecycle fits

Connect worker records from hire to pay. Choose the Contractor or W-2 type and keep the right checks for each.

Workers and worker types
Worker records sync to Wingspan. Each record keeps its Contractor or W-2 worker type.
Engagements and assignments
Project templates map to work templates. Worker roles map to assignments in the app.
Requirements and eligibility
Check definitions set reusable rules. Requirements track the selected checks and review state. One requirement can serve several attached assignments. Readiness is assessed for each assignment. It does not approve payment.
Work logs and approved work
Approved contractor entries fill work items in work logs. Approving a log creates one invoice/payable. Finance approves payment separately. W-2 work follows its own payroll path.
Payables
Contractor payables come from work logs or known amounts. Use one path for each cost. The contractor sees an invoice. Your team sees a payable. Finance approves payment separately.
Client invoices
Client bills sync to client invoices in Wingspan. They stay separate from bills owed to workers.
Payments and payouts
Your tools read payment status and funds movement references. Deposit confirmation means the sending bank finished processing. It does not prove the worker’s bank posted funds. Payments can still return.
Tax forms and reporting
Yearly pay totals and tax readiness flags sync to your reporting tools. Sharing these summaries does not submit a tax filing.

Connect your apps to your worker workflows

Bring worker records, work review, and payments together. We’ll help you set up the flow your team needs.

Discuss your integration