Import offers, creatives and categories from an external network with your own credentials. Re-syncing updates in place and never duplicates.
If your offers already live on another affiliate network, you should not have to retype them to run them in Offer Capsule. Network import connects to that network's API with your own credentials, pulls the offers down, and creates them locally with their creatives and categories attached. Re-running the sync updates the offers it already brought in rather than creating a second copy of each, so you can point it at a live network and keep syncing indefinitely without accumulating duplicates.
You create a network connection: a name, an adapter, an API base URL, and the API key issued to you by that network. The credentials are yours - Offer Capsule is calling that network as you, using access you already have, so nothing about the import depends on a relationship between the two platforms. A connection also carries the defaults that imported offers land with, including the advertiser they are created under and the billing method they use, so an import does not leave you with a pile of half-configured offers.
Two adapters ship today. The Everflow adapter calls the Everflow network offers endpoint and maps its offer shape onto Offer Capsule's: external offer id, name, status, destination and preview URLs, description, currency, payout type and amounts, categories and labels, and the creative entries attached to the offer. Payout types coming back as cpc, cpa, cpl, cpm, or a revenue-share code are mapped onto the matching Offer Capsule offer type, and the offer's status decides whether it lands active or paused.
The generic JSON adapter accepts the same field shape from any source that can produce it. It tolerates a plain array, a data wrapper, or an offers wrapper at the top level, which covers most export formats without custom work. If you can get your current network to hand you a JSON export of its offers, you can import it.
Every offer that comes in is recorded in a mapping ledger that ties the external network's offer id to the local offer it created. On the next sync, an offer that is already in the ledger is looked up and updated in place; only genuinely new external ids create new offers. That is what makes repeated syncing safe. If a mapped offer has since been deleted locally, the import recreates it rather than failing, and an offer arriving without an external id is skipped and reported rather than being guessed at.
A sync brings in the offers themselves, the creatives attached to them, and the category links that place them in your own category tree. Creatives arrive typed, so they show up in the affiliate portal the same way hand-built ones do - see creatives. Categories that do not correspond to anything local are reported as skipped rather than being invented.
Each sync returns a summary of exactly what it did: offers created, offers updated, offers skipped, creatives created, categories linked, and categories skipped, along with a message for each skip explaining why. The connection records when it last synced. This matters more than it sounds: an import you cannot audit is an import you will not trust, and a run that reports "updated 240, created 0" tells you at a glance that your ledger is doing its job.
Imported offers are ordinary Offer Capsule offers. They pick up the same encrypted per-affiliate links, the same fraud screening, the same conversion lifecycle, and the same reports as anything you built by hand, and you can edit them freely - though remember that a later sync will refresh the fields the adapter maps.
Next, tune what you imported on offer setup, hand the offers to affiliates with tracking links, or see the whole flow on how it works.
See Offer Capsule running against your own offers. We will follow up to arrange a walkthrough.