The Phaxio API states that for the faxList request, both the start and end timestamps have default values (-1 week, and now). It should be possible for the client to take advantage of these defaults by not passing values for them.
In particular requiring an end timestamp seems like a trap for the developer. I wanted all available updates, and would have happily taken the phaxio's server's default for "now". But since I was forced to pass a value, I used time() on my local machine. Well it turns out the clock on my dev box VM had drifted a couple minutes, such that the end timestamp I was passing was inadvertently excluding the most recent updates. I fixed that problem for now by passing time() + 15 minutes instead but ideally I shouldn't have had to worry about this.
The Phaxio API states that for the faxList request, both the start and end timestamps have default values (-1 week, and now). It should be possible for the client to take advantage of these defaults by not passing values for them.
In particular requiring an end timestamp seems like a trap for the developer. I wanted all available updates, and would have happily taken the phaxio's server's default for "now". But since I was forced to pass a value, I used time() on my local machine. Well it turns out the clock on my dev box VM had drifted a couple minutes, such that the end timestamp I was passing was inadvertently excluding the most recent updates. I fixed that problem for now by passing time() + 15 minutes instead but ideally I shouldn't have had to worry about this.