> ## Documentation Index > Fetch the complete documentation index at: https://docs.cernel.com/llms.txt > Use this file to discover all available pages before exploring further. # Developer Tools > Manage API keys and service accounts to integrate Cernel into your own systems. Developer Tools give you programmatic access to Cernel. Use the API to push products from your own systems and pull enriched content back once it's generated. ## How it works Under **Settings > Developer > API**, you authenticate requests to the [Public API](/integrations/public-api) with keys, organized into service accounts, one per integration. Push products in, let automations enrich them, then poll the [changes endpoint](/integrations/public-api#getting-enriched-data-back) to pull the results back. ### Why you would use this Push products from your ERP, PIM, or custom backend into Cernel without manual imports. Poll the changes endpoint to pull AI-generated content and product updates back into your own systems on your schedule. ## Step-by-step guide ### Managing API keys with service accounts An API key authenticates requests to the [Public API](/integrations/public-api). Keys are organized into **service accounts**: one account per integration, each holding its own keys. Grouping keys this way lets you see which integration has been calling and switch one off without disturbing the others. The API Settings page under Settings > Developer > API. A 'Service accounts' section lists accounts named Product, Test, and Service account, each showing its key count, created date, and last-active date, with a New key button and an expand control. The Product account is expanded to show its individual keys, each with a masked value, created date, last-used date, and a delete button. A New service account button sits at the top right. Go to **Settings > Developer > API**. Each service account is listed with the number of keys it holds, when it was created, and when it was last used. Expand an account to see its individual keys. Click **New service account** and name it after the integration that will use it, for example `Shopify` or `ERP sync`. That name is what shows up on the work its keys do. Creating an account immediately mints its first key. When a key is created, Cernel shows it once in a **Your new API key** dialog. Copy it and store it somewhere safe. For your security you won't be able to see the full key again, only a masked version. Store your API key like a password. Anyone with the key can access your organization's data through the API. If a key is ever exposed, revoke it and mint a new one. Click **New key** on an account to mint another key for it. To roll over to a fresh key without downtime, add the new key, update your integration to use it, then revoke the old one. Revoking a key stops it working immediately while the account and its other keys keep going. A revoked key stays in the list, marked **Revoked**, so a past call still has an explanation. Renaming and deleting a service account are **admin-only**; minting a key stays open to any member. You can delete an account only once none of its keys are still live, so revoke its keys first. Click **Visit Documentation** to open the full API reference in a new tab, with every endpoint, request format, and response schema. Keys created before service accounts existed appear under a **Keys without an account** list at the bottom of the page. There's nothing to do there: the next time such a key is used, it gets an account of its own and moves up to the main list. Revoke any you no longer need. ### Getting enriched content back Cernel does not push results to your systems. Once automations have enriched your products, poll the [changes endpoint](/integrations/public-api#getting-enriched-data-back) to pull the updates back in chronological order, using the offset it returns to pick up where you left off on the next poll. See [Building a custom product pipeline](/integrations/public-api#building-a-custom-product-pipeline) for the full walkthrough. ## Frequently asked questions Go to **Settings > Developer > API**, where keys are grouped under service accounts. Cernel shows a key's full value only once, in a dialog right after it's created, so copy it then. Afterwards only a masked version is shown. If you've lost a key, mint a new one on its account and revoke the old one. Yes. Create a **service account** per integration, and give each account as many keys as you need. Keys are revoked individually, so you can rotate one key or switch off a single integration without affecting the others. This is a change from the earlier model of one key per organization. Mint a new key on the same service account with **New key**, update your integration to use it, then revoke the old key. Because both keys are live during the switch, nothing stops working in between. Revoking takes effect immediately, so revoke only after the new key is in place. Poll the [changes endpoint](/integrations/public-api#getting-enriched-data-back) on the Public API. It returns enrichment updates in chronological order, and you use the offset it returns to fetch only what changed since your last poll. There is no push-style webhook delivery, so retrieving results is always a poll from your side. ## What's next Set up a full API integration for pushing products programmatically. Auto-enrich products pushed via API with automations. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.