mrisoftware
MRI Software (via Apideck)
Access MRI Software through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant MRI Software plumbing.
Beta connector. MRI Software is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
mrisoftware - Unified API: Accounting
- Auth type: basic
- Status: beta
- Gotchas: page
- MRI Software docs: https://www.mrisoftware.com
- Homepage: https://www.mrisoftware.com/
When to use this skill
Activate this skill when the user explicitly wants to work with MRI Software — for example, "create an invoice in MRI Software" or "reconcile payments in MRI Software". This skill teaches the agent:
- Which Apideck unified API covers MRI Software (Accounting)
- The correct
serviceIdto pass on every call (mrisoftware) - MRI Software-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
- Accounting: https://specs.apideck.com/accounting.yml · API Explorer
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List invoices in MRI Software
const { data } = await apideck.accounting.invoices.list({
serviceId: "mrisoftware",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from MRI Software to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — MRI Software
await apideck.accounting.invoices.list({ serviceId: "mrisoftware" });
// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });
This is the compounding advantage of using Apideck over integrating MRI Software directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
MRI Software via Apideck Accounting
MRI Software is an enterprise real-estate management platform (property management + accounting). Apideck coverage targets the accounting surface within MRI's financial modules.
Entity mapping
| MRI entity | Apideck Accounting resource |
|---|---|
| Journal Entry | journal-entries |
| Tenant / Receivable | customers |
| Vendor | suppliers |
| Account | ledger-accounts |
| Department | departments |
| Location / Property | locations |
| Purchase Order | purchase-orders |
| Tax | tax-rates |
| Bill | bills |
| Entity / Portfolio | subsidiaries |
Coverage highlights
- ✅ Journal entries (general ledger)
- ✅ Customers (tenants), suppliers (vendors)
- ✅ Chart of accounts
- ✅ Purchase orders
- ✅ Multi-entity / multi-property via departments, locations, subsidiaries
- ❌ Invoices in the unified sense — MRI uses tenant billing workflows; use Proxy for invoice-like records
- ❌ Lease management, property records — separate MRI module surfaces
- ❌ MRI-specific reporting tools — use Proxy
Auth notes
- Type: Basic auth (MRI API username + password), managed by Apideck Vault
- Client binding: MRI installations are per-client; one connection per client ID.
- Version / product variant: MRI has many product lines (Commercial Management, Residential Management, AnyBUILD). Confirm which API surface the user has access to.
- Enterprise-only: MRI is typically sold to large real-estate organizations — integration setup requires coordination with MRI admin staff.
Example: list journal entries for a property
const { data } = await apideck.accounting.journalEntries.list({
serviceId: "mrisoftware",
filter: { location_id: "property_xyz" },
});
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call MRI Software directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on MRI Software's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: mrisoftware" \
-H "x-apideck-downstream-url: <target endpoint on MRI Software>" \
-H "x-apideck-downstream-method: GET"
See MRI Software's API docs for available endpoints.
Sibling connectors
Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):
access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.
See also
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- MRI Software official docs
More from apideck-libraries/api-skills
apideck-connector-coverage
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
18apideck-best-practices
Best practices for building Apideck integrations. Covers authentication patterns, pagination, error handling, connection management with Vault, webhook setup, and common pitfalls. Use when designing or reviewing any Apideck integration regardless of language.
18apideck-rest
Apideck Unified REST API reference for any language. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using direct HTTP calls. Covers authentication headers, CRUD operations, cursor-based pagination, filtering, sorting, error handling, rate limiting, pass-through parameters, and webhooks. Language-agnostic — works with curl, fetch, axios, httpx, or any HTTP client.
16apideck-portman
API contract testing with Portman by Apideck. Use when generating Postman collections from OpenAPI specs, writing contract tests, variation tests, integration tests, fuzz testing, or setting up CI/CD API test pipelines. Portman converts OpenAPI 3.x specs into Postman collections with auto-generated test suites.
14apideck-node
Apideck Unified API integration patterns for TypeScript and Node.js. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors. Covers the @apideck/unify SDK, authentication, CRUD operations, pagination, filtering, webhooks, and Vault connection management.
14apideck-codegen
Generate typed API clients from Apideck OpenAPI specs using code generators. Use when the user wants to generate custom SDK clients, typed models, API stubs, or server scaffolding from Apideck's published OpenAPI specifications. Covers openapi-generator, Speakeasy, and Postman import workflows.
14