Already have an account? Sign in

Darksky

Darksky feature snapshot

A high-level look at Stitch's Darksky (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Darksky

Step 1: Retrieve your Darksky secret key

1. Log into your Darksky API accounthere.
2. On your account home page, your Secret Key is available at the top of the page. You will use this Secret Key to add your integration.

Step 2: Add Darksky as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theDarksky icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Darksky” would create a schema calledstitch_darksky in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theLanguage field, enter the language code. Ex: ‘en’ for English, ‘es’ for Spanish, and ‘fr’ for French. For a full list of available language codes, check theRequest Parameters section of theDarksky API documentation.
6. In theLocation List field, enter the latitude and longitude of the the locations to be returned for weather forecast information. The locations must be semi-colon deliniated. Ex:<latitude>,<longitude> is an accepted value for a single location, and<latitude>,<longitude>;<latitude>,<longitude>; ... etc is accepted for multiple locations.
7. In theSecret Key field, paste your Darksky secret key that you retrieved inStep 1.
8. In theUnits field, enter the measurement system to be returned for weather forecast information. Ex: ‘us’ for Imperial Units, and ‘si’ for International System of Units. For a full list of available measurement systems, check theRequest Parameters section of theDark Sky API documentation

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Darksky integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Darksky’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Darksky integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Darksky, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Darksky table reference

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.