How to create an API Token
Last updated:
API keys let another service access one Store through Sign Customiser’s public API. Older instructions may call them API tokens; they are the same credential.
Create a separate key for each integration and give it only the access it needs. This makes the key easier to identify and lets you revoke one integration without affecting another.
Open API Tokens
-
Universal: In the left sidebar, under Integrate, click API Tokens.
-
Shopify: Open Sign Customiser, go to Tools & Settings, then click API Tokens.
Create an API key
-
Click Create API key.
-
Enter a name that identifies the service and its purpose, such as WooCommerce orders or Monthly reporting.
-
Optional: choose an expiry date. The key expires at the end of that day in your local time. Leave this blank if the key should not expire.
-
Under Access, select at least one permission. Read access lets the service view that resource. Write access lets it change data or run actions for that resource.
-
Click Create key.
-
Copy the key and store it in your password manager or secrets manager. When it is safely stored, click I’ve stored this key.
Important
The complete key is shown once. Sign Customiser cannot show it again after you continue. If you lose it, revoke the key and create a replacement.
Choose the right access
Use the integration’s setup instructions to decide which permissions it needs. Avoid selecting write access unless the integration needs to create, update, resend, export, or delete data.
A key’s permissions and expiry cannot be changed after creation. Revoke it and create a replacement if either needs to change.
Use the key
Paste the key into the integration you created it for. For direct API requests, send it as a Bearer token in the Authorization header. See the Sign Customiser API documentation for endpoints and examples.
Revoke an API key
-
Return to API Tokens.
-
Click the delete icon beside the key.
-
Click Revoke to confirm. The key stops working immediately.
Older keys may be labelled Legacy key. They continue to work until revoked, but new integrations should use scoped keys.