Create asset from transactions

POST/api/v1/fixed-assets/from-transactions

Capitalize ledger transactions into a fixed asset.

Creates a fixed asset whose cost basis is the sum of the selected transactions' absolute amounts. All transactions must belong to the business and be assigned to ledger_id (typically an account tagged depreciable/amortizable in the chart of accounts).

Request Body:

ledger_id: Ledger the source transactions are assigned to (required)
transaction_ids: Transactions to capitalize, at least one (required)
name: Asset name, 1-255 chars (required)
useful_life_months: Useful life in months, 1-600 (optional, defaults to 60)
depreciation_method: straight_line, declining_balance, double_declining, units_of_production (optional, defaults to 'straight_line')
in_service_date: In-service date, YYYY-MM-DD (optional, defaults to the latest transaction date)
salvage_value: Salvage value in cents (optional, defaults to 0)
auto_place_in_service: Place the asset in service immediately so depreciation can start (optional, defaults to true)
line_entry_ids: Debit journal-entry lines on ledger_id (e.g. a manual opening-balance JE) to capitalize alongside or instead of transactions (optional)
expense_ledger_id: Expense account each period charges; required when the category has none (optional)

At least one transaction or line is required.

Returns: The created asset and its projected depreciation schedule.

Operation ID: create_asset_from_transactions·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Request body

Schema: CreateAssetFromTransactionsRequest

ledger_idstringrequired: Ledger the source transactions are assigned to
transaction_idsarray · string: Transactions to capitalize into the asset
line_entry_idsarray · string: Journal-entry lines (debits on ledger_id, e.g. from a manual opening-balance JE) to capitalize alongside or instead of transactions
expense_ledger_idstring: Expense account each period charges. Required when the asset's category has no expense account yet; saved on a newly created category, otherwise kept as this asset's override.
namestringrequired: Asset name
useful_life_monthsinteger: Expected useful life in months
depreciation_methodDepreciationMethodDepreciationMethod: Depreciation calculation method
in_service_datestring · date: In-service date (defaults to the latest transaction date when auto-placing in service)
salvage_valueinteger: Estimated salvage value in cents
auto_place_in_serviceboolean: Place the asset in service immediately so depreciation can start (otherwise it is created as a draft)

Responses

201Successful Response

Schema: SuccessEnvelope_CreateAssetFromTransactionsResponse_

successboolean
messagestring
codestring
dataCreateAssetFromTransactionsResponse

400Bad Request - Invalid input

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

401Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

403Forbidden - Insufficient permissions

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

404Not Found - Resource does not exist

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

422Validation Error

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

Code samples

POST/api/v1/fixed-assets/from-transactions

bash

curl -X POST 'https://api.ondayzero.com/api/v1/fixed-assets/from-transactions' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "ledger_id": "string",
  "name": "string"
}'