# Get your Payapps progress claims through an API > Read your Payapps progress claims by status, with approval and payment due dates, approved totals and variation lines, one API call each. A workflow can list the claims awaiting assessment each morning and post each approved claim to your accounting system. Page: https://fous.com/automate/payapps Updated: 2026-11-12 Works with your own Payapps account. Fous is an independent product. ## What you can build on Payapps ### Get progress claims by status Reads the progress claims across your projects and contracts, filtered by status, with each claim's dates, claimant and respondent. - Takes: Status (Draft, Submitted or Approved), project (optional) - Returns: Project, contract, claim number, claim as at, status, claimant, respondent, submitted at, approved at, approval due date, payment due date, invoice reference ### Read an approved claim's totals Opens one approved progress claim and reads what was claimed and what was approved, split into original works and variations, with retention and tax. - Takes: Project, contract, claim number - Returns: Original works claimed and approved, variations approved, variations on account, retention to date, net claim excluding tax, net claim including tax ### Get a contract's variation lines Reads the variation lines on one contract, with the amounts claimed and approved to date and any reason given for a modification or rejection. - Takes: Project, contract - Returns: Variation reference, description, contract value, claimed to date, approved to date, reason for modification or rejection ### Submit a draft progress claim Opens a progress claim in Draft status on one of your contracts, adds your invoice reference and submits it to your client for assessment. - Takes: Project, contract, claim number, invoice reference - Returns: Claim number, status, submitted at, approval due date ## Automate Payapps with a workflow A [workflow](/product/workflows) 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. ### Submitted claims nearing their approval due date Starts: Every weekday at 7:00 1. Get the progress claims in Submitted status across your projects. 2. Keep the claims whose approval due date is in the next three days or has passed. 3. Email you the list grouped by project, with claimant, claim number and approval due date. ### Approved claims, posted to your accounting system Starts: Every day at 18:00 1. Get the progress claims in Approved status and keep those not there on the last run. 2. For each one, read the approved claim's totals. 3. Post project, contract, claim number, net claim, retention to date and payment due date to your webhook. ### Month-end list of submitted claims for accruals Starts: Every month on the 1st at 8:00 1. Get the progress claims in Submitted status, not yet fully assessed. 2. Group them by project with an AI step. 3. Email you the list and post each claim to your finance 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](/product/methods), it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get progress claims by status” 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": "my.payapps.com/get_progress_claims", "input": { "status": "Submitted", "project": "Northwind Medical Centre" } }' ``` Example response: ``` { "status": "completed", "data": { "claims": [ { "project": "Northwind Medical Centre", "contract": "Mechanical services", "claim_number": 7, "claim_as_at": "2026-10-31", "status": "Submitted", "claimant": "Acme Air Pty Ltd", "respondent": "Globex Construction", "submitted_at": "2026-10-28", "approved_at": null, "approval_due_date": "2026-11-11", "payment_due_date": "2026-11-25", "invoice_reference": "INV-2207" } ], "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. ## Payapps’s own options Payapps documents a public API for extracting data: projects, contracts and progress claims (payapps), with approved claim totals and PDFs. Its write endpoints were marked deprecated in December 2024, so it reads only. It needs a client ID and secret, and the public pages do not say who can get them or what they cost. | Option | What it covers | What it takes | | --- | --- | --- | | Payapps Public API | Reads projects, contracts, contract lines and progress claims, and an approved claim's totals and PDFs. Write endpoints are deprecated. | A client ID and secret, with OAuth sign-in as a Payapps user. Who can get them and the price are not on the public pages. | | ERP and accounting integrations | Payapps describes claim posting, project and contract syncing and retention data flowing to construction ERPs, and Xero and MYOB for subcontractors. | Your ERP, or Xero or MYOB, connected to your Payapps account. | | Payapps by hand | Preparing, submitting, assessing and tracking progress claims, variations and retention in the app. | A subcontractor plan: A$65 per claim, or A$49 a month for 1 contract up to A$440 for unlimited, excluding GST. | Read on November 12, 2026: [Payapps Public API documentation](https://api.payapps.com/documentation/), [Construction ERP and accounting integrations](https://payapps.com/features/construction-erp-integrations), [Subcontractor pricing](https://www.payapps.com/pricing-subcontractors/). ## Signing in to Payapps Payapps now signs people in with Autodesk ID: you enter your email on my.payapps.com, then a 6-digit code sent by email by default, or your organisation's single sign-on when it has one. With Fous you sign in once through Payapps' own sign-in with your own account: the login is sealed with AES-256, the emailed code is handled, and an expired session is signed back in. ## Worth knowing - **Three statuses, and totals only once approved**: A claim not yet submitted is Draft, a submitted claim that is not fully assessed is Submitted, and a fully assessed one is Approved. Payapps produces the approved claim's totals and invoice only for Approved claims. - **The public API reads only**: Payapps marked its API write endpoints as deprecated on 12 December 2024. Submitting a claim or changing a contract happens in the app itself. - **Sign-in moved to Autodesk ID**: From 1 February 2026 Payapps moved accounts to Autodesk ID in stages. The default second step is an emailed 6-digit code, and other methods are chosen at profile.autodesk.com. - **One login for every counterparty**: One Payapps account covers all your projects and the builders you claim from. A subcontractor joins a builder's contract through an email invitation from that builder. ## More in Construction - [BuildingConnected](https://fous.com/automate/buildingconnected.md) - [LCPtracker](https://fous.com/automate/lcptracker.md) - [Procore](https://fous.com/automate/procore.md) - [Autodesk Build](https://fous.com/automate/autodesk-build.md) - [SOKA-BAU Online-Service](https://fous.com/automate/soka-bau-online-service.md) - [United Rentals Total Control](https://fous.com/automate/united-rentals-total-control.md) - [Hyphen SupplyPro](https://fous.com/automate/hyphen-supplypro.md) - [Trimble Unity Construct](https://fous.com/automate/trimble-unity-construct.md) - [GCPay](https://fous.com/automate/gcpay.md) - [Oracle Textura Payment Management](https://fous.com/automate/oracle-textura-payment-management.md) Other industries: [MWI Animal Health](/automate/mwi-animal-health), [Meesho Supplier Panel](/automate/meesho-supplier-panel), [Infinite Campus](/automate/infinite-campus), [AEP online account](/automate/aep-online-account), [GrabMerchant](/automate/grabmerchant), [businessONLINE](/automate/businessonline). ## Frequently asked questions ### Does Payapps have an API? Yes, a read-only one. The Payapps Public API returns projects, contracts and progress claims, with approved totals and PDFs, for data warehouses and backups. Its write endpoints are deprecated. It needs a client ID and secret, and Payapps' public pages do not say who can get them or what they cost. ### Can I list all submitted claims that are waiting for approval? Yes. In Payapps, a claim that has been submitted but not fully assessed has the status Submitted, and Payapps' API documentation names this list as a common use for accruals reporting. A method you build can read those claims across your projects, and a workflow can email you the ones near their approval due date. ### Can I send approved Payapps claims to my accounting system? Yes. Payapps offers integrations with construction ERPs, and with Xero and MYOB for subcontractors. With Fous, a workflow you build can read each newly approved claim's totals on a schedule and post them by webhook to your own system. ### Can progress claims be submitted automatically? Not through Payapps' API, whose write endpoints are deprecated. With Fous you can build a write method that submits a claim you already prepared in Draft status, using your own account. ### Is Fous affiliated with Payapps (an Autodesk company)? No. Fous is an independent product. You use it with your own Payapps account, and a method reads and does only what that account can. Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Payapps (Payapps (an Autodesk company)). 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.