Recurly (v14-09-2016)

Recurly integration summary

Stitch’s Recurly integration replicates data using the Recurly REST API (V2.3). Refer to the Schema section for a list of objects available for replication.

Recurly feature snapshot

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

STITCH
Release status	Deprecated on November 21, 2019	Supported by	Stitch
Stitch plan	Standard	API availability	Not available
Singer GitHub repository	Not applicable
REPLICATION SETTINGS
Anchor Scheduling	Supported	Advanced Scheduling	Unsupported
Table-level reset	Unsupported	Configurable Replication Methods	Unsupported
DATA SELECTION
Table selection	Unsupported	Column selection	Unsupported
Select all	Unsupported
TRANSPARENCY
Extraction Logs	Unsupported	Loading Reports	Supported

Connecting Recurly

Recurly setup requirements

To set up Recurly in Stitch, you need:

• Admin permissions in your Recurly account. This is needed to generate an API key.

---

Step 1: Generating a Recurly API Key

1. Sign into your Recurly account.
2. From the Recurly dashboard, click the Developers option in the sidebar.
3. Click API credentials.
4. Click the Add Private API Key button.
5. Enter a name for the key. We recommend something that will tell you, at a glance, who or what is using the key - for example, ‘Stitch.’

6. The last section - Will this key be used with a third-party application? - is optional.

   If you want to enter something here, you can select Other from the dropdown menu and then type Stitch into the Application Name field.

7. When finished, click the Save Changes button to generate the key.

Leave this page open for now - you’ll need it to complete the setup in Stitch.

Step 2: Add Recurly as a Stitch data source

1. Sign into your Stitch account.

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

3. Click the Recurly 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 Recurly” would create a schema called stitch_recurly in the destination. Note: Schema names cannot be changed after you save the integration.

5. Enter the subdomain for your Recurly site. For example, if our subdomain were stitch.recurly.com, we would just enter stitch into this field.
6. Paste the Recurly API key you generated into the API Key field.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Recurly integration. This means that:

• For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
• For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.

Change this setting if you want to replicate data beyond Recurly’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

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

Recurly integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

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

Step 5: Set objects to replicate

The last step is to select the tables you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

1. In the Integration Details page, click the Tables to Replicate tab.
2. Locate a table you want to replicate.

3. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

4. Repeat this process for all the tables you want to replicate.

Initial and historical replication jobs

After you finish setting up Recurly, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending 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.

---

Recurly table reference

Related	Troubleshooting
Destination & Integration Compatibility Replication Scheduling Syncing Historical SaaS Data Resetting Replication Keys Nested Data Structures & Row Count Impact	Third-Party Downtime Understanding & Reducing Your Usage Re-Authorizing Integrations Replication Issues

---

Questions? Feedback?

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