dashboards

Run a widget config without saving it (Agent-Native PR 3).

The metric layer has had POST /metrics/preview since the Metrics Composition program; an assembled widget had no equivalent, so the only way to learn whether a report produced numbers was to persist it and look. For an agent that is the wrong order — it should verify before a human sees anything.

The config is validated with the same gate the write path uses, then composed and executed through run_widget_query. There is no second execution path, and nothing is persisted.

post/api/v1/dashboards/widgets/preview

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/dashboards/widgets/preview
  • Auth: none declared

Request body

viz_type'line' | 'bar' | 'pie' | 'number' | 'pivot' | 'logs_table' | 'heatmap' required
start_datestring date required
end_datestring date required
category_idstring uuid nullable
property_idsstring[] nullable
property_ids_excludestring[] nullable

Response

Successful Response

Changes

    • warning

      added the new crm_object_type enum value to the // response property for the response status

    • warning

      added the new crm_record enum value to the // response property for the response status

    • warning

      added the new crm_record_count enum value to the ////////// response property for the response status

    • warning

      added the new crm_record_count enum value to the //////// response property for the response status

    • warning

      added the new handling_outcome enum value to the // response property for the response status

    • info

      added the new optional request property ///

    • info

      added the new crm_object_type enum value to the request property //

    • info

      added the new crm_record enum value to the request property //

    • info

      added the new handling_outcome enum value to the request property //

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ///// to the response with the status

    • info

      added the optional property ///// to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ///// to the response with the status

    • info

      added the optional property ///// to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status