Get your Tipalti payment statuses through an API

What you can build on the Supplier Hub

• Get payment history

  Build this

  Reads the Payment History tab: each payment from your payer with its status, amount and the invoices it covers.

  Takes

  Earliest payment date (optional), status (optional)

  Returns

  Payment date, amount, currency, status, invoices covered

• Get invoice history

  Build this

  Reads the Invoice History tab: the invoices your payer has on record for you, with their numbers, dates and amounts.

  Takes

  Invoice date from (optional)

  Returns

  Invoice number, invoice date, amount, currency

• Read your payment details

  Build this

  Reads the payment method from Payment Details, with the currency and payment threshold you chose in the Supplier Hub.

  Takes

  Nothing

  Returns

  Payment method, currency, payment threshold

Automate the Supplier Hub 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.

• Payments marked Paid, posted to your accounting system

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Get the payment history for the last 14 days.

  Step 2

  Keep the payments whose status changed to Paid since the last run.

  Step 3

  Post each one, with its amount, currency and invoices covered, to your accounting webhook.

• Deferred and Rejected payments, emailed each weekday

  Build this

  Starts

  Every weekday at 9:00

  Step 1

  Get the payment history for the last 30 days.

  Step 2

  Keep the payments in Deferred or Rejected status that were not on the last run.

  Step 3

  Email you each one with its amount, date and invoices covered.

• New invoices in Invoice History, weekly

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  Get the invoice history for the last 60 days.

  Step 2

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

  Step 3

  Email you the list with invoice number, date, amount and currency.

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 payment history” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "suppliers.tipalti.com/get_payment_history",
    "input": {
      "from_date": "2026-10-01"
    }
  }'

{
  "status": "completed",
  "data": {
    "payments": [
      {
        "payment_date": "2026-11-06",
        "amount": 8420,
        "currency": "USD",
        "status": "Paid",
        "invoices": [
          {
            "invoice_number": "NW-2291",
            "amount": 5100
          }
        ]
      }
    ],
    "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.

The Supplier Hub’s own options

Tipalti's REST API and iFrames are used by the company that pays you: it creates payees, invites them to the Supplier Hub and creates invoices, and it can embed Invoice History and Payment History in its own website. Tipalti documents no API for payees. As a payee you use the Supplier Hub and the payment status emails.

Read on November 12, 2026: Tipalti developer documentation: Payees, Tipalti developer documentation: iFrames, Tipalti Payee FAQs.

Signing in to the Supplier Hub

You register through your payer's emailed invitation by creating a password, then sign in with the Supplier Hub login link your payer gives you. Some updates ask for two-factor authentication. With Fous you sign in once through the Supplier Hub's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Your payer decides what you see

The Payment History tab appears only if your payer has enabled it, and the payment methods offered are the ones your payer made available. Invoice approval, payment timing and amounts are set by the payer.

Deferred means blocked before the bank

A Deferred payment was stopped before bank submission because of missing tax forms, invalid banking details or a compliance hold. Rejected marks returned funds.

The login link, not the invitation

Registration links are temporary and stop working once used. Only your payer can change your Supplier Hub login email, which may differ from the email in your contact details.

One payment can cover several invoices

Payment History shows the invoices that make up each payment, so the payment history method you build can return them with every payment, to match against your receivables.

More in Procurement

• Petronect
• Basware Portal
• BtoBプラットフォーム 請求書
• Tungsten Network
• Taulia supplier portal
• OpenInvoice
• Coupa Supplier Portal
• JAGGAER Supplier Network
• SAP Business Network
• Oracle Fusion Cloud Supplier Portal
• Workday supplier portal
• Nalanda
• Avetta
• ISNetworld

Other industries: Confirmation, Zillow Premier Agent, Omnipart, Toyota Dealer Daily, Paylocity, Hyphen SupplyPro.