Service overview
Vista integration API for the Hub and AP Automation.
API base path
/api/v1Authentication
Bearer token
Submissions
Queued · tracked by ID
Endpoints
All API requests require a scoped credential| Method | Path | Purpose |
|---|---|---|
| GET | /api/v1/companies/{company}/vendors?q=… | Vendor lookup |
| GET | /api/v1/companies/{company}/jobs?q=… | Job lookup |
| GET | /api/v1/companies/{company}/gl-accounts?q=… | GL account lookup |
| POST | /api/v1/invoices | Submit invoice data and PDF |
| GET | /api/v1/operations/{id} | Submission status and audit events |
Operational notes
Check app liveness ↗Submitting an invoice
Send invoice JSON, a PDF, the approving user's email, and an Idempotency-Key. A 202 response means accepted into the queue. Check the operation ID for the final result.
Troubleshooting
An unknown outcome needs reconciliation before retrying. The liveness endpoint checks Laravel only; it does not verify the VPN, Vista connection, or queue worker.