Here I'm using the package sqids for generating these IDs, since it seems like a good alternative to plain base62 with a salt, and it's reasonably convenient. It is on the endpoint side instead of the database side, so when writing new endpoints we need to keep in mind the encoding and decoding of these IDs.
However, once the current endpoints are moved to use sqids instead of the previous numeric IDs, whoever creates a new endpoint will probably realize that the id is a number instead of a string if they forgot to encode/decode, giving them a hint as to what the issue is.
Here I'm using the package
sqidsfor generating these IDs, since it seems like a good alternative to plain base62 with a salt, and it's reasonably convenient. It is on the endpoint side instead of the database side, so when writing new endpoints we need to keep in mind the encoding and decoding of these IDs.However, once the current endpoints are moved to use sqids instead of the previous numeric IDs, whoever creates a new endpoint will probably realize that the id is a number instead of a string if they forgot to encode/decode, giving them a hint as to what the issue is.