Logs, exports and APIs write the same moment many ways: with a T or a space, with Z or +01:00 or +0100, or as a European date with a time. Parsed one by one, the offsets are dropped or the formats rejected.
Column type: DATETIME
| In the file | Cleaned | Status |
|---|---|---|
2025-03-04T10:00:00+01:00 | 2025-03-04 10:00:00+01:00 | clean |
2025-03-04T08:30:00Z | 2025-03-04 08:30:00+00:00 | clean |
2025-03-05 11:00:00+0100 | 2025-03-05 11:00:00+01:00 | clean |
04.03.2025 10:15 | 2025-03-04 10:15:00 | ambiguous |
2025-03-06 07:45:00 | 2025-03-06 07:45:00 | clean |
Every timestamp is written as YYYY-MM-DD HH:MM:SS, with its offset when it had one (Z becomes +00:00). A timestamp without an offset stays without one: Data Cleaner does not invent a time zone.
https://mcp.data-cleaner.com/mcp, then ask it to clean your file.curl -X POST https://data-cleaner.com/clean/v1/column \
-H 'Content-Type: application/json' \
-d '{"values": ["2025-03-04T10:00:00+01:00", "2025-03-04T08:30:00Z", "2025-03-05 11:00:00+0100", "04.03.2025 10:15", "2025-03-06 07:45:00"]}'
The answers above are the API's own, captured when this page was built.