Object create without endAt: suspected bug in API spec

[sergei-maertens]

Version: latest / 2.1 (API spec)

When I create an object with unknown end date, then this is typically stored as null in the database. Then I also expect to receive null in the response JSON (record.endAt: null). However, the API spec documents this as string(date) and does not show it could be null too:

This is all theory and untested - possibly the API returns an empty string for empty values.