Author: Connor McArthur (connor@fishtownanalytics.com)
This is a Singer tap that produces JSON-formatted data following the Singer spec.
Uniquely identify an authorized API user - the 'key' part of 'API key' authenticate that user - cannot be guessed/forged; can be revoked if a user misbehaves - typically they key into a database that can have a record deleted. Typically you will have thousands or millions of API keys not billions, so they do not need to.
It: Office16proplusr_grace edition key generator.
Get credentials from Campaign Monitor. You'll need your client ID and an API key.
Create the config file.
There is a template you can use at config.example.json
, just copy it to config.json
in the repo root and insert your client ID and secret.
Step 4 creates a file called catalog.json
that specifies all the available endpoints and fields. You'll need to open the file and select the ones you'd like to replicate. See the Singer guide on Catalog Format for more information on how tables are selected.
campaign_*
streams, you MUST select campaigns
as well. Likewise for list_*
and lists
.Copyright © 2018 Stitch
Author: Connor McArthur (connor@fishtownanalytics.com)
This is a Singer tap that produces JSON-formatted data following the Singer spec.
It:
Get credentials from Campaign Monitor. You'll need your client ID and an API key.
Create the config file.
There is a template you can use at config.example.json
, just copy it to config.json
in the repo root and insert your client ID and secret.
Step 4 creates a file called catalog.json
that specifies all the available endpoints and fields. You'll need to open the file and select the ones you'd like to replicate. See the Singer guide on Catalog Format for more information on how tables are selected.
campaign_*
streams, you MUST select campaigns
as well. Likewise for list_*
and lists
.Copyright © 2018 Fishtown Analytics