Setup 11 of 14
Keep API keys and CMS tokens safe
Anyone who has one of your CMS tokens or API keys can change what’s on your site. Give each key only the permissions it needs, keep it in one place, and be ready to turn it off quickly if it may have leaked. This page lists what we ask you to do, and explains how Get1pct handles keys.
- Required?
- Before connecting
- Where you do it
- Your CMS and the dashboard
Least privilege
Create a separate key just for Get1pct, and give it only the permissions Get1pct actually uses.
- Shopify: only the
write_productsandwrite_content(orwrite_online_store_pages) scopes. No scopes for orders, customers, themes and so on. Steps - Webflow: a site token with CMS set to Read and write, Sites set to Read-only, and No access for everything else. Steps
- Contentful: the token has exactly the access of the user who creates it. Create it as a dedicated user who belongs only to the connected space and can publish (such as an Editor). The Admin role isn’t needed. Steps
- microCMS: clear GET under Default Permission (it’s checked from the start), and give only GET and PATCH to the APIs you connect. Steps
- WordPress: create the application password as a user who can edit posts or pages. It doesn’t have to be an administrator. Steps
- Get1pct API key (opct_): if you only read edits, create it without the “record results” checkbox. Steps
Where keys belong
- Paste CMS tokens only into the fields in the Get1pct dashboard. Don’t put them in email, chat, contact forms or shared documents, and don’t send them to us when you contact us.
- Keep Get1pct API keys (opct_) on your own server only. Put them in environment variables or a secret store, such as your cloud provider’s secret manager. Never put them in code that runs in a browser (including variables exposed with prefixes such as
NEXT_PUBLIC_), in mobile apps, in Git or in logs. - Decide who is in charge of keys. When that person changes, hand the keys over and replace them.
If a key may have leaked
If you sent a key to the wrong place, wrote it somewhere public or lost a computer, turn it off right away, in this order:
- Turn it off in the service that issued it. After that, it works nowhere. In Shopify, uninstall or delete the app. In Webflow, revoke the token. In Contentful, revoke the CMA token. In microCMS, delete the API key. In WordPress, revoke the application password.
- Click “Disconnect” under Connections in your Get1pct dashboard. Get1pct deletes the key it stored.
- For a Get1pct API key (opct_), click “Turn off key” or “Create or renew key” on the API page. Either way, the old key stops working at once.
- Create a new key and connect again. Then check your CMS’s change history for edits you don’t recognize.
When to replace keys
- Replace keys when the person in charge changes, when a contract with an outside agency ends, or when you start using a key for something else.
- Even if none of that happens, replacing keys on a fixed schedule is safer. Where you can choose an expiry date, as in Contentful, set one.
- “Create or renew key” replaces your Get1pct API key (opct_), and the previous key stops working at once. Pick a time when you can update the key on your server right away.
How Get1pct handles keys
This is how the Get1pct software actually works.
- CMS tokens and WordPress application passwords are encrypted (AES-256-GCM) with a key that only our server holds. They are never shown again on screen or returned by the API. Each encrypted key is tied to its site’s connection, so it can’t be read if it is copied to another site’s record. Get1pct uses them only to apply and undo the edits you choose.
- Get1pct connects only to each CMS’s official API host (
*.myshopify.com,api.webflow.com,api.contentful.com/api.eu.contentful.com,*.microcms.io). It doesn’t use URLs that are typed in or taken from edits as they are, and it doesn’t follow redirects, so a key is never sent to another host. - Get1pct deletes the keys it stores when you click “Disconnect”, when you cancel, and when you remove a site you added on Pro.
- To stop anyone from guessing keys, connection attempts are limited to 10 an hour per person and per site, counted across all our servers. When an attempt fails, the message doesn’t say exactly why.
- Get1pct API keys (opct_) are made from 32 random bytes, and we store only their SHA-256 hash. The key itself is shown once, when it is created, and we don’t keep it. Each key can make 60 requests a minute, and works only while your plan is Growth or Pro.
- The API doesn’t write to your site. It only handles edits and records of how they were applied. It never writes to or publishes your site, and never connects to a URL the caller supplies.
The ownership line (get1pct-verification) isn’t a secret. It is meant to be on your public page, and it is not an API key.
When you stop
Disconnect in Get1pct, and delete the key in the service that issued it. A key is fully gone only after you do both. Change payment, cancel, and remove access also lists what to remove when you cancel.
If the steps don’t match what you see, contact us with your site URL and the screen where you got stuck. Please don’t send passwords.