Local accounting agent queue
List accounting connection records
/a/DataSyncs_list
List the tenant’s saved DataSync IDs, names and stored types.
When to use this endpoint
Start the local-agent settings workflow here. Cloud integrations should use Accounting_status rather than interpreting historical DataSync rows as live cloud connections.
Authentication and permissions
Use signed API-key authentication or a logged-in CRM session on the account’s routed host. API keys act as their owner; session requests require the dispatcher’s CSRF token where configured. Tenant rows and settings belong to that authenticated account.
These handlers add no accounting page or CRM2 role check. The dispatcher has no Accounting/DataSync object-scope mapping. Settings-screen access controls are separate from these shared API handlers; CRM2 screen roles are not a CRM1 API requirement.
Parameters
This endpoint has no operation-specific parameters.
Example request
$result = FM_api('DataSyncs_list', []);
Example response
[
{
"id": "14",
"name": "Office Sage",
"sync_type": "sage50accounts"
}
]
Database numeric values can be strings. Read the JSON error/warning fields as well as the HTTP status.
Errors and unusual responses
| Response | Condition |
|---|---|
{"error":"not logged in"} | No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs. |
Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.
Behaviour and edge cases
- Returns a bare array of id,name,sync_type, with no ok or total wrapper; an empty tenant produces []. No order, pagination, filters or secret columns are selected.
- Includes historical cloud records as well as local Sage/GnuCash rows. List visibility does not prove that login/logout/mapping operations accept that stored type.
- Source searches found no direct callers for these CRM accounting routes in the current mobile app or m intermediary. The desktop accounting agent uses its own signed Data Sync JSON-RPC protocol.
Side effects
- Database read only; does not discover installed agents or test connectivity.
See it in Fieldmotion
CRM1
Open Settings → Data Sync. The pageSettingsDataSync screen uses this route for the operation described above; filter browser Network requests by the exact function name. Local-agent setup is separate from the cloud Finance integrations. Open Data Sync settings to build the saved-connection tabs.
CRM2
Open Settings → Data Sync. The CRM2 pageSettingsDataSync screen retains this local-agent workflow; filter browser Network requests by the exact function name. Its screen permissions do not add a role check to this shared handler. Open Data Sync settings to build the saved-connection tabs.
Related endpoints
DataSync_get— Reload connection state.DataSync_new— Create the local connection.Accounting_status— Check connection state.