Managing API Keys
When you signup for our compression API service, you get a single API key. If you purchase more credits, they go on the same key. If you purchase a second or third subscription, it all goes on the same key. In fact, multiple subscriptions will cause problems, so don't do that.
Your API key is not locked or limited to a single site, it may be used on 10 sites or 1,000 sites, it's totally up to you. But some folks need more flexibility, and for them we have created the concept of "sub-keys".
You can manage your API keys at https://ewww.io/manage-keys/ which gives you several options. Of course, if you are believe someone is abusing your key, you can generate a new primary key, which will invalidate the old one immediately.
But you can also create "sub-keys" on that page, which can be very useful for client work. Whether you want to limit how many credits each client uses, or just keep track of their usage, sub-keys give you greater ability to keep track of your usage when you have many websites to take care of. On the key management page, you can generate an unlimited number of sub-keys. You can then label them so that you have a handy reminder of what the key is for or what site it is installed on.
You can also set a limit to how many credits a sub-key can use each month. If you use pre-paid credits, of course the sub-keys are still limited to however many pre-paid credits are on your account. For example, if you purchase 9,000 credits, and limit a sub-key to 5,000 and the sub-key uses 5,000 credits the first month, then it can really only use 4,000 the next month (or less if credits have been used on the primary key or other sub-keys). If you have a monthly subscription, your usage is unlimited, so then the sub-key is only subject to whatever limits you have configured. Our system will alert you once 10,000 or more credits have been used on your account within a given billing cycle, and that alert threshold can also be changed upon request.