I can see why this is popular.  It is rare to find such variability with short locks.  Does it run over 18 hours ever...I guess that is a stupid question that one would not know as it depends upon Mistress,

It appears that that the readyToUnlock only shows up after the application has run in the forground and has a chance to evaluate the lock.  That makes sense now that you mention it as the logic is in the app and not on the server.  It does change some things as it makes it not possible to do remote unlocking without touching the phone (at least in Android) as the app will be sleeping.

very good. I'll give it a go and let you know if I see an issue. You were rather quick about it!
Documentation page doesn't show the new status

Thanks for the reply.

I would like to know that the status of the key is ready to be unlocked. Not the actual time length.  Though knowing the time length might be nice as well for timed locks.

My thoughts is add a few status
so you have UnlockedFake, UnlockedReal, sucess  already.  My thoughts would be add something like "KeyAvailable" when the timer or keyholder has unlocked it but the lockee has not yet tried the key.  (LockedReady or LockedKeyAvailable ... any words to that effect would work just as well)
You can't see at this point if if a real or fake key since the user does not know.  If the keyholder adds time before the lock is tried it would update back to the Locked status.

Any remote app would just send a once every minute or so query to your server so it does not need to predict when it will be unlocked. If it notices the status that the key is available it could then remotely unlock its lock. If the key turns out to be fake the lockee might still not be able to enter a lock box but that is not the fault of the api.

If you want to populate the time in the future for timestampUnlocked of when it would be unlocked but not update the status that would be OK for timed locks but that isn't what I was after.  That would be nice in that a remote API could use that data to update a color light or something though perhaps that is better handled by a different field that would also give a prediction of the number of cards in the case of non-timed lock but that is a different request.

Great to see an API.  I was playing with it to see if I could use it for some of my remote controlled stuff
   Documentation page http://www.chastikey.com/api/doku.php has a typo on the tense of the API.  it has checklocks.php (plural) and the actual API is singular.
 
   Also it would be nice to mention that userid must be in all caps (or perhaps update the API to uppercase before doing the lookup?

   Finally the API does not show when a lock can be opened but still locked. That is nice for remote control to automatically unlock a lock--say a magnetic lock holding keys or .....

Once again great job and great to see an actively developed application!