Book a DemoStart Free Trial

XML API v1.1

Build against the documented method surface.

This reference preserves the method names implemented by Invoicera's XML v1.1 application interface. Confirm account access, required fields and operating limits before committing a production connector.

Open API endpoint API overview
Request contractXML v1.1
Method
POST
Endpoint
https://api.invoicera.com/xml/1.1/
Authentication
HTTP Basic authentication; API token as username
Payload field
xml_request

Use a server-side integration. Never expose an account token in browser code or a public repository.

Reference status

The method index below is grounded in the XML v1.1 application implementation and its request templates. It documents method names, not universal account entitlement or a guarantee that every historical operation remains enabled.

Method index

Choose the resource, then the smallest required operation.

Begin with one end-to-end record path. Test the response, duplicate protection, retry behaviour and reconciliation before adding another resource.

01

Invoices

  • createInvoice
  • updateInvoice
  • deleteInvoice
  • getInvoice
  • listInvoice
  • sendInvoiceMail
  • addInvoiceItem
  • updateInvoiceItem
  • deleteInvoiceItem
02

Estimates

  • createEstimate
  • updateEstimate
  • deleteEstimate
  • getEstimate
  • listEstimate
  • sendEstimateMail
  • addEstimateItem
  • updateEstimateItem
  • deleteEstimateItem
03

Recurring invoices

  • createRecurring
  • updateRecurring
  • deleteRecurring
  • getRecurring
  • listRecurring
  • addRecurringItem
  • updateRecurringItem
  • deleteRecurringItem
04

Clients

  • createClient
  • updateClient
  • deleteClient
  • getClient
  • listClient
05

Staff

  • createStaff
  • updateStaff
  • deleteStaff
  • getStaff
  • listStaff
06

Products and services

  • createProduct
  • updateProduct
  • deleteProduct
  • getProduct
  • listProduct
  • createService
  • updateService
  • deleteService
  • getService
  • listService
07

Expenses

  • createExpense
  • updateExpense
  • deleteExpense
  • getExpense
  • listExpense
  • createExpenseCategory
  • updateExpenseCategory
  • deleteExpenseCategory
  • listExpenseCategory
08

Projects

  • createProject
  • updateProject
  • deleteProject
  • getProject
  • listProject
09

Tasks

  • createTask
  • updateTask
  • deleteTask
  • getTask
  • listTask
10

Time logs

  • createTimeLog
  • updateTimeLog
  • deleteTimeLog
  • getTimeLog
  • listTimeLog
11

Account and supporting operations

  • getAccountInfo
  • createInvoiceFromTimeTracking
  • createInvoiceFromExpense
  • createInvoiceFromEstimate
  • invoiceOfflinePayment
  • listLateFee
  • listTax
  • listOfflinePaymentMethod

Request envelope

Send the token separately from the XML body.

The XML root identifies the method. Child elements carry that method's fields. The sample uses placeholders and contains no live account data.

XML request

<?xml version="1.0" encoding="utf-8"?>
<request method="getInvoice">
  <invoice_id>[INVOICERA_INVOICE_ID]</invoice_id>
</request>

cURL outline

curl --request POST \
  --user "$INVOICERA_API_TOKEN:x" \
  --data-urlencode 'xml_request=<?xml version="1.0" encoding="utf-8"?><request method="getInvoice"><invoice_id>[INVOICERA_INVOICE_ID]</invoice_id></request>' \
  https://api.invoicera.com/xml/1.1/

Before production

Treat method availability and field requirements as account-specific checks.

The historical reference did not establish a safe universal contract for access, limits or every field. Confirm those points with Invoicera using the exact workflow you intend to operate.

  1. 01

    Confirm access Verify the account token and the required method set.

  2. 02

    Validate fields Test mandatory and optional fields with representative non-sensitive records.

  3. 03

    Handle responses Parse XML success and error responses and retain a safe correlation record.

  4. 04

    Control retries Prevent a timeout or repeated request from creating duplicate commercial records.