Keypad codes (as well as Authorizations for Users) are stored inside the Smart Lock. The limitation is the available storage inside the flash chip of the Smart Lock.
For your usage scenario you would (most likely) need is a completely different way on how codes are created. With a time based algorithm you could generate unlimited, automatically expiring codes which are valid for preset time periods. Basically an algorithm that you have running at your end and that runs inside the Smart Lock and that generates the same code at the same time at both ends. As such you would not even need an API to generate a new code. Drawback is that you can not remove or block a certain code. Once handed out, it is simply valid at the specified point in time.
Hmmm. Also the requirement on my side woult be that the codes are created to another time than the “booking”. Currently, the customer gets the code with the booking confirmation, which could be long time before the booked time. So somwhere the code has to be stored and applied to the SmartLock to another time. So something like a cron-job needs to be implemented and running, which I currently cannot provide. Right now, there is only the possibility to create and push the code right after the booking has been made, which could lead to many more than 100 codes before they even get active.