API keys
API keys let another system, such as an ERP, a feed manager or your own scripts, read and update your Fulify catalog through the Fulify API. Each key belongs to your organization and only has the access you give it. Only organization admins can manage keys.
This page covers creating and managing keys. For endpoints, request formats and examples, see the API reference.
Where to find it
Go to Settings → API Keys, or open /settings/api-keys.
Create a key
- Click Create key.
- Give the key a Name that says what uses it, for example "Feed manager".
- Choose its Access (see below).
- Choose when it Expires: Never, 24 hours, 30 days or 90 days.
- Click Create key.
- Copy the key from the API key created window and store it somewhere safe, then click Done.
Keys start with flfy_live_. Send the key as a bearer token to https://api.fulify.io/v1.
Choose the right access
Pick the smallest level of access the integration needs:
| Access | What it allows |
|---|---|
| Read only | Read products and size charts. Can't change anything. The default for new keys. |
| Edit catalogue | Read and change products and size charts. Can't switch sync on, so nothing reaches a live system. |
| Full integration | Everything, including turning Channel Sync and Linnworks on or off per product. For an ERP or OMS that decides what goes where. |
| Custom | Pick individual permissions yourself. |
With Custom, you choose from these permissions:
- Read products — products, variants, categories, and whether each is switched on for Linnworks.
- Create and update products — matched by SKU. Also creates variant groups. Doesn't send anything to your channels.
- Read size charts — selection guides and which products carry them.
- Manage size charts — create, edit and delete selection guides, and attach them to products.
- Control sync — turn Channel Sync and Linnworks on or off per product. This sends data to live systems, and it also needs Create and update products.
Manage your keys
The keys table lists each key's Name, the start of the Key, its Access, when it Expires, and when it was Last used. A key that's never been used, or that hasn't been used in a long time, may be safe to revoke.
To revoke a key, click Revoke on its row and confirm. Any integration using it stops working immediately, and this can't be undone.