Debugging Timestamp Filters

Some things to check:

Is each filter which uses a gte, lte, using a double underscore __ vs _

For example:

curl -H 'Authorization: Bearer \<TOKEN_HERE>'  
-H 'X-Pm-Org: \<MID_HERE>'  
'<https://app.propertymeld.com/api/v0.0.1/meld/?limit=40&offset=0&created__gte=1633015800000>'  
| jq '.results\[] | .created'

or

curl -H 'Authorization: Bearer \<TOKEN_HERE>'  
-H 'X-Pm-Org: <MID>'  
'<https://app.propertymeld.com/api/v0.0.1/meld/?limit=40&offset=0&created__gte=1633015846850>'  
| jq '.results\[] | .created'

Try the filters in the browser

Another thing to try is putting the filters directly on a meld list view and see if that works:

Not working:

https://app.propertymeld.com/MID/m/MID/melds/melding/?created_gte=1633015846850

Working:

https://app.propertymeld.com/MID/m/MID/melds/melding/?created__gte=1633015846850

Is the unix timestamp 13 characters long?

The unix epoch time isn't currently able to handle nanoseconds so must be 13 characters long

1633015846850 works
1633015846000 works
16328916000 doesn't work
16328916000000 doesn't work
1632891600000000 doesn't work