Get a single resource by provider-native ID
Authorizations
Enter your API key with the Bearer prefix — e.g. Bearer sk_live_xxx (production) or Bearer sk_test_xxx (sandbox)
Headers
Identifier of the end user whose connected provider should be queried. This is the same endUserId you supplied when creating the connect token. Required on every CRM and accounting call.
"user-001"
Path Parameters
Canonical accounting resource type to fetch. Must be one of the values in the enum below. RouteMCP maps this to the equivalent provider-native object (e.g. invoice → QuickBooks Online Invoice/Bill, Xero Invoice, Zoho Books Invoice). On-demand reports (balance_sheet, income_statement, cash_flow_statement) accept synthetic period URNs as the {id} — see the relevant guide for the URN format.
invoice, contact, account, payment, tax_rate, journal_entry, expense, purchase_order, sales_order, credit_note, vendor_credit, company_info, item, tracking_category, accounting_period, payment_method, payment_term, address, attachment, balance_sheet, bank_feed_account, bank_feed_transaction, cash_flow_statement, employee, expense_report, general_ledger_transaction, income_statement, item_fulfillment, phone_number, project, transaction Provider-native record id. This is the id as it appears in the source system (e.g. a HubSpot contact id, a Pipedrive deal id, a QuickBooks invoice id). Use the remote_id field returned by the list endpoint.
"12345"
Query Parameters
Provider slug identifying which connected provider to target (e.g. hubspot, pipedrive, zoho-crm, quickbooks-online, xero, zoho-books). Required — single-record operations always target a specific provider.
"hubspot"
Controls enrichment of related-record fields such as owner_name, owner_email, contact_name, companyName, etc. Accepts:
true(default) — enrich all supported fields. Adds extra provider calls; slower but more complete.false— skip enrichment entirely. Fastest; returns only ids for related records.- A comma-separated list of field names (e.g.
owner_name,owner_email) — enrich only the listed fields.
"true"
Response
Single accounting resource record
Standard envelope returned by GET /accounting/{resource}/{id}. The shape of data depends on the {resource} path parameter — see the tabs to switch between resource variants.
Always true for successful (2xx) responses.
true
HTTP status code mirrored inside the envelope.
200
"OK"
Fields present on every accounting resource returned by RouteMCP.
- Invoice
- Contact
- Account
- Payment
- TaxRate
- JournalEntry
- Expense
- PurchaseOrder
- SalesOrder
- CreditNote
- VendorCredit
- CompanyInfo
- Item
- TrackingCategory
- Period
- PaymentMethod
- PaymentTerm
- Address
- PhoneNumber
- Attachment
- BalanceSheet
- BankFeedAccount
- BankFeedTransaction
- CashFlowStatement
- Employee
- ExpenseReport
- GeneralLedgerTransaction
- IncomeStatement
- ItemFulfillment
- Project
- Transaction