[71,72] Track item moving between vaults and requests rate limits

Interesting use case, thanks for sharing!

Are the resources you're linking to in your internal system all sign-ins or do they also include resources completely unrelated to what 1Password is offering? Would Universal Sign On that we share in our vision at https://www.future.1password.com/ be helpful for you so that you can link not just username/password logins, but any type of login via 1Password?

Just to make sure I understand correctly what you're currently using, are these the URLs you're using: https://<your company name>.1password.com/vaults/<vault id>/allitems/<item id> ?

Is there a better way to keep track of an item that is moved between vaults (or during vaults restructuring)?

My first hunch would be to solve this by tracking the items ID instead of name, as the ID uniquely identifies the item independent of the vault the item is stored in.

However, I believe moving items in 1Password is currently actually a create + delete under the hood, so the items ID will change when the item is moved. Is this why you have the workaround of storing a unique id in one of the items fields?

Are there any request rate limits documented?

1Password API ratelimits are unfortunately not documented at this moment.

Is using --cache an option for you? This will hopefully prevent you from running into the ratelimits, as the item get commands will fetch the details from the cache that was filled by the item list command.