Skip to main content
GET
Get a single resource by provider-native ID

Authorizations

Authorization
string
header
required

Enter your API key with the Bearer prefix — e.g. Bearer sk_live_xxx (production) or Bearer sk_test_xxx (sandbox)

Headers

X-End-User-Id
string
required

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.

Example:

"user-001"

Path Parameters

resource
enum<string>
required

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.

Available options:
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
id
string
required

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.

Example:

"12345"

Query Parameters

provider
string
required

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.

Example:

"hubspot"

enrich
string

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.
Example:

"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.

success
boolean
required

Always true for successful (2xx) responses.

Example:

true

statusCode
integer
required

HTTP status code mirrored inside the envelope.

Example:

200

message
string
required
Example:

"OK"

data
Invoice · object
required

Fields present on every accounting resource returned by RouteMCP.