Create Mapping Association
Link a chart-of-accounts element to a US GAAP reporting concept. One mapping edge per call — use auto-map-elements for bulk AI-assisted mapping. Duplicate (from, to, type) tuples return 409. The target must be a leaf concept: a subtotal the statement sums from its children is refused (422). Map before you close: a new arc for an account with landed history in a closed month is refused (422), since the month's stamped statements were computed through the arcs as they stood. To move such an account, pass replaces_association_id (its current arc, removed in the same write). A move within the same primary statement is a reclassification and goes through: the stamped statements keep the answer as closed, live renders follow the new arc, and reclassified_periods names the months. A move across statements restates net income and is refused, naming the months to reopen latest-first.
Idempotency: supply an Idempotency-Key header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
Request
- Base URL: https://api.robosystems.ai (the document declares no server; this is the origin it was published from)
- URL: https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/create-mapping-association
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Path parameters
Headers
Request body
Example request
{
"association_type": "mapping",
"confidence": 0.95,
"from_element_id": "elem_coa_revenue_product",
"mapping_id": "map_01HVF8T0M2YTAY3BBNRH0V0",
"suggested_by": "user",
"to_element_id": "elem_usgaap_Revenues",
"weight": 1
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.