Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Anonymous
4 years agoYour client has been rate-limited
I've been using the CLI 2.0 in a bunch of tests lately and I've run into being rate limited. I've been unable to find any information on what the limits actually are.
Can you provide me with the l...
kovpack
4 years agoOccasional Contributor
I have a similar problem and got this (429) Too Many Requests: Too many requests. Your client has been rate-limited. when trying to get details of each item. It's not documented anywhere (at least I was not able to find the documentation).
Before fetching each item separately, I listed them all with --cache option. Then started getting details of each item (making a 2-seconds pause between each request just to be safe). Someone on the forum told me some time ago, that this should not make a real call (thus be rate-limited), but this does not seem to be true at all. In CLI 1 the information I need now was available in a list command, but now in CLI 2 I have to make a separate request per item to get the username, password, and URL for a LOGIN item. Basically, upgrading to CLI 2 broke a lot of things for us and made 1password less useful and more expensive.
Once a day I need to make a copy of 1password vaults, users, items & their permissions (we use this data internally and build some monitors and overview dashboards of permissions, which is not possible with the web UI at all). This is fine, as all the information can be fetched with a few list calls and a few dozens of calls when iterating over entities.
But we also need extra data (username, password & URL) to track item duplicates, password change/rotation dates, etc. Though, this will be around 800 requests more (maybe, even more in the future).
Setting up a Connect Server for us means +$300 to our monthly bills, which are already pretty high for a company of almost 150 employees (currently on a Business plan). Our InfoSec says, "you already did more for 1password, than 1password did for you", so we may soon consider alternatives.
If rate limits would be documented, this will at least give us enough information to make a daily sync possible not violating rate limits, and will give us the benefits we had before the CLI 2 release. Yes, this sync will take ages, but at least it will not decrease the value of 1password that much.