Xero: Retrieves a specific expense claim using a unique expense claim Id

← Accounting operations · Get started

Operation xero.getexpenseclaim

Provider route: GET /api.xro/2.0/ExpenseClaims/{ExpenseClaimID}. Alter supplies the connection’s credentials and routing.

Call through Alter

Install @alter-ai/sdk @alter-ai/xero with npm, or alter-sdk-xero with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { XeroIntegration } from "@alter-ai/xero";

async function execute(input: Parameters<XeroIntegration["accounting"]["getExpenseClaim"]>[0]) {
  const app = new App({ apiKey: process.env.ALTER_API_KEY! });
  try {
    const provider = new XeroIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
    const call = await provider.accounting.getExpenseClaim(input);
    const result = await call.wait();
    return result.bodyJson();
  } finally {
    await app.close();
  }
}

import os
from alter_sdk import App
from alter_sdk_xero import XeroIntegration

async def execute(arguments):
    async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
        provider = XeroIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
        call = await provider.accounting.get_expense_claim(arguments)
        result = await call.wait()
        return result.body_json()

Input

Field	Type	Presence	Description and constraints
$	object	Root	Additional keys: not allowed
path	object	Required within parent	Additional keys: not allowed
path.ExpenseClaimID	string	Required within parent	Format: uuid
headers	object	Required within parent	Additional keys: not allowed
headers.xero-tenant-id	string	Required within parent

Response

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

Field	Type	Presence	Description and constraints
$	Model	Root	Expand Creates expense claims — response body

Referenced models: Creates expense claims — response body

Schemas

26 more schemas are linked from the tables above, on the schema pages.

Creates expense claims — response body

Field	Type	Presence	Description and constraints
$	object	Root
ExpenseClaims	array	Optional
ExpenseClaims[]	Model	Each item	Expand Creates expense claims — response body — Expense Claims item

Referenced models: Creates expense claims — response body — Expense Claims item

Creates expense claims — response body — Expense Claims item

Field	Type	Presence	Description and constraints
$	object	Root
AmountDue	JSON	Optional
AmountDue (anyOf 1)	number	Alternative	The amount due to be paid for an expense claim Format: double Read only: true
AmountDue (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
AmountPaid	JSON	Optional
AmountPaid (anyOf 1)	number	Alternative	The amount still to pay for an expense claim Format: double Read only: true
AmountPaid (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
ExpenseClaimID	string	Optional	Xero generated unique identifier for an expense claim Format: uuid
PaymentDueDate	string	Optional	The date when the expense claim is due to be paid YYYY-MM-DD Read only: true
Payments	array	Optional	See Payments
Payments[]	Model	Each item	Expand Retrieves payments for invoices and credit notes — response body — Payments item
ReceiptID	string	Optional	The Xero identifier for the Receipt e.g. e59a2c7f-1306-4078-a0f3-73537afcbba9 Format: uuid
Receipts	array	Optional
Receipts[]	Model	Each item	Expand Updates a specific draft expense claim receipts — response body — Receipts item
ReportingDate	string	Optional	The date the expense claim will be reported in Xero YYYY-MM-DD Read only: true
Status	string	Optional	Current status of an expense claim – see status types Known values: SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED
Total	JSON	Optional
Total (anyOf 1)	number	Alternative	The total of an expense claim being paid Format: double Read only: true
Total (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
UpdatedDateUTC	string	Optional	Last modified date UTC format Read only: true
User	Model	Optional	Expand Retrieves users — response body — Users item

Referenced models: Retrieves users — response body — Users item, Retrieves payments for invoices and credit notes — response body — Payments item, Updates a specific draft expense claim receipts — response body — Receipts item

Retrieves users — response body — Users item

Field	Type	Presence	Description and constraints
$	object	Root
EmailAddress	string	Optional	Email address of user
FirstName	string	Optional	First name of user
IsSubscriber	boolean	Optional	Boolean to indicate if user is the subscriber
LastName	string	Optional	Last name of user
OrganisationRole	string	Optional	User role that defines permissions in Xero and via API (READONLY, INVOICEONLY, STANDARD, FINANCIALADVISER, etc) Known values: READONLY, INVOICEONLY, STANDARD, FINANCIALADVISER, MANAGEDCLIENT, CASHBOOKCLIENT, UNKNOWN, REMOVED
UpdatedDateUTC	string	Optional	Timestamp of last change to user Read only: true
UserID	string	Optional	Xero identifier Format: uuid

Retrieves payments for invoices and credit notes — response body — Payments item

Field	Type	Presence	Description and constraints
$	object	Root
Account	Model	Optional	Expand Deletes a chart of accounts — response body — Accounts item
Amount	JSON	Optional
Amount (anyOf 1)	number	Alternative	The amount of the payment. Must be less than or equal to the outstanding amount owing on the invoice e.g. 200.00 Format: double
Amount (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
BankAccountNumber	string	Optional	The suppliers bank account number the payment is being made to
BankAmount	JSON	Optional
BankAmount (anyOf 1)	number	Alternative	The amount of the payment in the currency of the bank account. Format: double
BankAmount (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
BatchPayment	Model	Optional	Expand Creates one or many batch payments for invoices — response body — Batch Payments item
BatchPaymentID	string	Optional	Present if the payment was created as part of a batch. Format: uuid
Code	string	Optional	Code of account you are using to make the payment e.g. 001 (note- not all accounts have a code value)
CreditNote	Model	Optional	Expand Deletes an Allocation from a Prepayment — response body — Credit Note
CreditNoteNumber	string	Optional	Number of invoice or credit note you are applying payment to e.g. INV-4003
CurrencyRate	JSON	Optional
CurrencyRate (anyOf 1)	number	Alternative	Exchange rate when payment is received. Only used for non base currency invoices and credit notes e.g. 0.7500 Format: double
CurrencyRate (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
Date	string	Optional	Date the payment is being made (YYYY-MM-DD) e.g. 2009-09-06
Details	string	Optional	The information to appear on the supplier's bank account
HasAccount	boolean	Optional	A boolean to indicate if a contact has an validation errors Default: false
HasValidationErrors	boolean	Optional	A boolean to indicate if a contact has an validation errors Default: false
Invoice	Model	Optional	Expand Deletes an Allocation from a Prepayment — response body — Invoice
InvoiceNumber	string	Optional	Number of invoice or credit note you are applying payment to e.g.INV-4003
IsReconciled	boolean	Optional	An optional parameter for the payment. A boolean indicating whether you would like the payment to be created as reconciled when using PUT, or whether a payment has been reconciled when using GET
Overpayment	Model	Optional	Expand Deletes an Allocation from a Prepayment — response body — Overpayment
Particulars	string	Optional	The suppliers bank account number the payment is being made to
PaymentID	string	Optional	The Xero identifier for an Payment e.g. 297c2dc5-cc47-4afd-8ec8-74990b8761e9 Format: uuid
PaymentType	string	Optional	See Payment Types. Known values: ACCRECPAYMENT, ACCPAYPAYMENT, ARCREDITPAYMENT, APCREDITPAYMENT, AROVERPAYMENTPAYMENT, ARPREPAYMENTPAYMENT, APPREPAYMENTPAYMENT, APOVERPAYMENTPAYMENT Read only: true
Prepayment	Model	Optional	Expand Deletes an Allocation from a Prepayment — response body — Prepayment
Reference	string	Optional	An optional description for the payment e.g. Direct Debit
Status	string	Optional	The status of the payment. Known values: AUTHORISED, DELETED
StatusAttributeString	string	Optional	A string to indicate if a invoice status
UpdatedDateUTC	string	Optional	UTC timestamp of last update to the payment Read only: true
UpdatedDateUTCString	string	Optional	UTC ISO-8601 formatted timestamp of last update to the payment Read only: true
ValidationErrors	array	Optional	Displays array of validation error messages from the API
ValidationErrors[]	Model	Each item	Expand Retrieves journals — response body — Warnings item
Warnings	array	Optional	Displays array of warning messages from the API
Warnings[]	Model	Each item	Expand Retrieves journals — response body — Warnings item

Referenced models: Deletes a chart of accounts — response body — Accounts item, Creates one or many batch payments for invoices — response body — Batch Payments item, Deletes an Allocation from a Prepayment — response body — Credit Note, Deletes an Allocation from a Prepayment — response body — Invoice, Deletes an Allocation from a Prepayment — response body — Overpayment, Deletes an Allocation from a Prepayment — response body — Prepayment, Retrieves journals — response body — Warnings item

Retrieves journals — response body — Warnings item

Field	Type	Presence	Description and constraints
$	object	Root
Message	string	Optional	Validation error message

Creates contacts to a specific contact group — response body — Contacts item Sales Tracking Categories item

Field	Type	Presence	Description and constraints
$	object	Root
TrackingCategoryName	string	Optional	The default sales tracking category name for contacts
TrackingOptionName	string	Optional	The default purchase tracking category name for contacts

Policy, approvals and errors

SDK function policy ID: xero.getexpenseclaim. Catalog operation: getExpenseClaim. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source