Docs

Put Aspire to workacross your business

Integrate Aspire between all of the tools your business uses. MindCloud works with you to connect apps, move data and keep processes running.

Businesses save 434,412 work hours and $19.7M every month by automating Aspire.

Every action you need

Your company can interact with Aspire using our 149 actions.
Can’t find what you need? Let us know.

Create ContactCreateAdd a new contact.
Update ContactUpdateUpdate an existing contact record.
List AddressesReadRun a list addresses action in Aspire.
List Bank DepositsReadRun a list bank deposits action in Aspire.
Approve ReceiptCreateApproves an existing Aspire receipt and can optionally receive it at the same time. This is the only post-create update path for a receipt. At approve time, the only receipt fields that can be added or changed are the vendor invoice number and vendor invoice date. No other receipt field can be edited through this action, including notes, extra costs or freight, receipt items, received date, vendor, branch, or work ticket. If the user asks to change a non-invoice-metadata field on an existing receipt, surface that limitation upfront and offer the available path of recreating the receipt with the corrected values.
Create ReceiptCreateCreates an Aspire receipt and is the only point where receipt-level fields can be set. Set receipt notes, extra costs or freight and other non-standard cost fields, receipt items, received date, vendor, branch, work ticket, and other receipt details here because Aspire has no updateReceipt endpoint or field-level patch action after creation. Vendor invoice number and vendor invoice date may also be set here. Those two invoice metadata fields are the only receipt fields that can also be added or changed later, through approveReceipt. If the user asks to add or change any other field after a receipt already exists, explain that it must be recreated with the corrected values. Do not plan an update path for existing receipt notes, costs, items, dates, or similar receipt fields.
List ReceiptsReadLists Aspire receipts using the available OData query parameters. Use this to find existing receipts and inspect fields such as status, invoice metadata, notes, received date, items, and costs. Aspire receipts cannot be updated after createReceipt; there is no updateReceipt endpoint or field-level patch action. The only post-create change path is approveReceipt, and it can add or change only the vendor invoice number and vendor invoice date. If the user wants to change any other field on an existing receipt, surface that constraint upfront and offer to recreate the receipt with the corrected values.
Receive ReceiptCreateMarks an existing Aspire receipt as received. This action accepts the receipt identifier only and does not perform receipt-level edits. It cannot set or change invoice metadata, notes, extra costs or freight, receipt items, received date, or any other receipt field. If the user wants to record vendor invoice number or vendor invoice date around the same workflow, use approveReceipt because approveReceipt is the only post-create path for those two fields. For any other requested change to an existing receipt, explain that Aspire has no updateReceipt or patch action and the receipt must be recreated with the correct values.
List Invoice BatchesReadRun a list invoice batches action in Aspire.
List Invoice RevenuesReadRun a list invoice revenues action in Aspire.
List InvoicesReadRun a list invoices action in Aspire.
Create Partial PaymentCreateCreate partial payment in Aspire.
List PaymentsReadRun a list payments action in Aspire.
List Payment TermsReadRun a list payment terms action in Aspire.
Create VendorCreateCreate vendor in Aspire.

Frequently Asked Questions

Common questions about working with MindCloud on your Aspire integration.

No. MindCloud is a full-service integration provider — our team designs, builds, launches, monitors, and maintains your Aspire integration end to end. You tell us what you need and we deliver a working, production-ready connection.