Merge C# SDK sends non-ISO-8601 datetimes, API rejects time filters

TL;DR

Fixed in the latest SDK release; datetime serialization now emits ISO 8601 compliant values. Upgrade the package if your time filters fail.

Fix

1. Fixed in the latest SDK release; datetime serialization now emits ISO 8601 compliant values. Expected: You get the expected result; the problem is gone.

2. Upgrade the package if your time filters fail. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Merge C# SDK sends non-ISO-8601 datetimes, API rejects time filters.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source.

Variant phrasings

Merge C# SDK sends non-ISO-8601 datetimes, API rejects time filters

Why it happens

GitHub issue on merge-api/merge-csharp-client: datetime values were formatted with a wrong format string, so time-based filters produced API errors.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

GitHub issue on merge-api/merge-csharp-client: datetime values were formatted with a wrong format string, so time-based filters produced API errors. Resolved: Fixed in the latest SDK release; datetime serialization now emits ISO 8601 compliant values. Upgrade the package if your time filters fail. Source: https://github.com/merge-api/merge-csharp-client/issues/30