This integration is powered by Singer's Recurly tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Stitch support.
Recurly integration summary
Stitch’s Recurly integration replicates data using the Recurly Partner API (v2018-08-09). Refer to the Schema section for a list of objects available for replication.
Recurly feature snapshot
A high-level look at Stitch's Recurly (v1) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status |
Released on June 13, 2019 |
Supported by | |
Stitch plan |
Standard |
API availability |
Available |
Singer GitHub repository | |||
REPLICATION SETTINGS | |||
Anchor Scheduling |
Supported |
Advanced Scheduling |
Supported |
Table-level reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
DATA SELECTION | |||
Table selection |
Supported |
Column selection |
Supported |
Select all |
Supported |
||
TRANSPARENCY | |||
Extraction Logs |
Supported |
Loading Reports |
Supported |
Connecting Recurly
Recurly setup requirements
To set up Recurly in Stitch, you need:
-
Admin or Manager permissions in Recurly. These permissions are required to create an API key for Stitch.
Step 1: Generate a Recurly API key
In this step, you’ll create an API key for Stitch.
- Sign into your Recurly account.
- Click Admin > Users in the sidenav.
- On the Users page, click the Configure API Access button at the top of the page. Thsi will open the API Credentials page.
- Click the Add Private API Key button. The Add Private API Key page will display.
- Fill in the fields as follows:
- Key Name: Enter a name for the API key. For example:
Stitch
- Notes: Enter any notes you want about the API key.
- Key Name: Enter a name for the API key. For example:
- Click Save Changes.
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
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Recurly icon.
-
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. - In the API Key field, paste the Recurly API key you created in Step 1.
- In the Recurly Subdomain field, enter your Recurly subdomain. For example: If the full URL of the subdomain were
stitchdata.recurly.com
, you’d only enterstitchdata
into this field. - In the Quota Limit field, enter the percentage of the API rate limit you want to allocate to the integration. For example: A value of
30
would be30%
of the rate limit. Refer to Recurly’s documentation for more info.
Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Recurly integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
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:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
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 and columns 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.
For Recurly integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- Click the Finalize Your Selections button at the bottom of the page to save your data selections.
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.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
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
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the Recurly integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
accounts
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The accounts
table contains info about the customer accounts in your Recurly account. Account objects store the history of the customer, billing info, etc.
Custom fields
Stitch’s Recurly integration supports replicating custom fields for accounts objects.
id
The account ID. Reference:
|
||||||||||||||||||||||||||||||||||
updated_at
The date and time the account or its billing info was last updated. |
||||||||||||||||||||||||||||||||||
address
The address info for the account.
|
||||||||||||||||||||||||||||||||||
bill_to
Indicates whether charges on the account are billed using the parent’s billing info or the account itself. Possible values are:
|
||||||||||||||||||||||||||||||||||
billing_info
Details about the account’s billing info.
|
||||||||||||||||||||||||||||||||||
cc_emails
Additional email addresses that should receive account correspondence. These emails will receive all emails that the |
||||||||||||||||||||||||||||||||||
code
The unique identifier of the account. |
||||||||||||||||||||||||||||||||||
company
The company name of the account. |
||||||||||||||||||||||||||||||||||
created_at
The date and time the account was created. |
||||||||||||||||||||||||||||||||||
custom_fields
A list of custom fields associated with the account.
|
||||||||||||||||||||||||||||||||||
deleted_at
The date and time the account was deleted. |
||||||||||||||||||||||||||||||||||
email
The email address for the account. |
||||||||||||||||||||||||||||||||||
exemption_certificate
The tax exemption certificate number for the account. If the merchant has an integration for the Vertex tax provider, this optional value will be sent in any tax calculation requests for the account. |
||||||||||||||||||||||||||||||||||
first_name
The first name of the account. |
||||||||||||||||||||||||||||||||||
hosted_login_token
The unique token for automatically logging the account into the hosted management pages. |
||||||||||||||||||||||||||||||||||
last_name
The last name of the account. |
||||||||||||||||||||||||||||||||||
object
This will be |
||||||||||||||||||||||||||||||||||
parent_account_id
If the account is a child account, the ID of the parent account. Reference:
|
||||||||||||||||||||||||||||||||||
preferred_locale
Used to determine the language and locale of emails sent on behalf of the merchant to the customer. The list of locales is restricted to those the merchant has enabled on the site. |
||||||||||||||||||||||||||||||||||
shipping_addresses
The shipping address info for the account.
|
||||||||||||||||||||||||||||||||||
state
The state of the account. Possible values are |
||||||||||||||||||||||||||||||||||
tax_exempt
The tax status of the account. A value of |
||||||||||||||||||||||||||||||||||
username
The username of the account. |
||||||||||||||||||||||||||||||||||
vat_number
The VAT number of the account. |
adjustments
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The adjustments
table contains info about adjustments, which are credits and charges associated with your customers.
id
The adjustment ID. Reference: |
|||||||||||||||||
updated_at
The date and time the adjustment was last updated. |
|||||||||||||||||
account
Details about the account associated with the adjustment. |
|||||||||||||||||
accounting_code
The accounting code. |
|||||||||||||||||
add_on_code
The code for the add-on the adjustment applies to. |
|||||||||||||||||
add_on_id
The ID of the add-on the adjustment applies to. Reference: |
|||||||||||||||||
amount
The amount of the adjustment. |
|||||||||||||||||
created_at
The timestamp when the adjustment was created. |
|||||||||||||||||
credit_applied
The amount of credit from this line item that was applied to the invoice. |
|||||||||||||||||
credit_reason_code
The credit reason code associated with the adjustment. |
|||||||||||||||||
currency
The three-letter ISO code of the currency used for the adjustment. |
|||||||||||||||||
description
A description of the adjustment. |
|||||||||||||||||
discount
The discount on the adjustment. |
|||||||||||||||||
end_date
The timestamp when the adjustment ended. |
|||||||||||||||||
invoice_id
The ID of the invoice associated with the adjustment. Reference:
|
|||||||||||||||||
invoice_number
The number of the invoice associated with the adjustment. |
|||||||||||||||||
legacy_category
The category to describe the role of a line item on a legacy invoice. Possible values include:
|
|||||||||||||||||
object
|
|||||||||||||||||
origin
The origin of the adjustment to return. Possible values are:
|
|||||||||||||||||
original_line_item_invoice_id
The invoice where the credit originated. This field will only have a value if the line item is a credit created from a previous credit, or if the credit was created from a charge refund. |
|||||||||||||||||
plan_code
The plan code the adjustment applies to. |
|||||||||||||||||
plan_id
The ID of the plan associated with the adjustment. Reference: |
|||||||||||||||||
previous_line_item_id
This field will only have a value if the line item is a credit created from a previous credit, or if the credit was created from a charge refund. |
|||||||||||||||||
product_code
For plan-related line items, this will be the plan’s code. For add-on related items, this will be the add-on’s code. |
|||||||||||||||||
proration_rate
Applicable only to prorated adjustments. This represents how much the adjustment was prorated to account for a mid-cycle subscription change. |
|||||||||||||||||
quantity
The quantity of the adjustment. |
|||||||||||||||||
refund
Indicates whether the adjustment is a refund or not. |
|||||||||||||||||
refunded_quantity
The refunded quantity of the adjustment. |
|||||||||||||||||
shipping_addresses
The shipping address info for the adjustment.
|
|||||||||||||||||
start_date
The timestamp when the adjustment began. |
|||||||||||||||||
state
The state of the adjustments to return. Possible values are:
|
|||||||||||||||||
subscription_id
The ID of the subscription associated with the adjustment. |
|||||||||||||||||
subtotal
The subtotal of the adjustment. |
|||||||||||||||||
tax
The tax amount for the adjustment. |
|||||||||||||||||
tax_code
Applicable only to EU VAT and Avalara AvaTax Pro merchants. The tax code for the adjustment. If using Recurly’s EU VAT feature, possible values include |
|||||||||||||||||
tax_exempt
Indicates whether the adjustment is tax exempt or not. If |
|||||||||||||||||
tax_info
|
|||||||||||||||||
taxable
Indicates if the adjustment is taxable. |
|||||||||||||||||
type
The type of adjustment to return. Possible values are:
|
|||||||||||||||||
unit_amount
The unit amount for the adjustment, in cents. For |
|||||||||||||||||
uuid
The unique identifier of the adjustment. |
billing_info
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
account_id |
API endpoint : |
The billing_info
table contains info about the billing information for accounts
.
Note: To replicate this table, you must also have the accounts
table set to replicate.
Custom fields
Stitch’s Recurly integration supports replicating custom fields for billing info objects.
account_id
The ID of the account associated with the billing info. Reference:
|
|||||||||
updated_at
The timestamp when the billing info was last updated. |
|||||||||
address
The address info for the account.
|
|||||||||
company
The company name of the account. |
|||||||||
created_at
The timestamp when the billing info was created. |
|||||||||
custom_fields
A list of the custom fields associated with the billing info.
|
|||||||||
exemption_certificate
The tax exemption certificate number for the account. If the merchant has an integration for the Vertex tax provider, this optional value will be sent in any tax calculation requests for the account. |
|||||||||
first_name
The first name of the account. |
|||||||||
fraud
Details about the most recent fraud result.
|
|||||||||
id
The billing info ID. |
|||||||||
last_name
The last name of the account. |
|||||||||
object
|
|||||||||
payment_method
Details about the payment method associated with the account’s billing info.
|
|||||||||
updated_by
Details about the user who last updated the billing info for the account.
|
|||||||||
valid
Indicates if the billing info is valid. |
|||||||||
vat_number
The VAT number associated with the account. |
coupons
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The coupons
table contains info about the coupons available in your Recurly account.
id
The coupon ID. Reference: |
||||||||
updated_at
The date and time when the coupon was last updated. |
||||||||
applies_to_all_plans
Indicates if the coupon is valid for all plans. |
||||||||
applies_to_non_plan_charges
Indicates if the coupon is valid for one-time, non-plan charges. |
||||||||
code
The code the customer enters to redeem the coupon. |
||||||||
coupon_type
The type of the coupon. Possible values are:
|
||||||||
created_at
The timestamp when the coupon was created. |
||||||||
discount
Details of the discount a coupon applies.
|
||||||||
duration
The duration that the coupon will be applied to invoices for. Possible values are:
|
||||||||
expired_at
The date and time the coupon was expired early or reached its |
||||||||
free_trial_amount
The duration of time the |
||||||||
free_trial_unit
The description of the unit of time the coupon is for. Used with the
|
||||||||
hosted_page_description
This description will show up when a customer redeems a coupon on your Hosted Payment Pages, or if you choose to show the description on your own checkout page. |
||||||||
invoice_description
The description of the coupon as it will appear on invoices. |
||||||||
max_redemptions
The maximum number of redemptions for the coupon. The coupon will expire when the maximum redemption is hit. |
||||||||
max_redemptions_per_account
The number of times a specific account can redeem the coupon. |
||||||||
name
The internal name for the coupon. |
||||||||
object
|
||||||||
plans
|
||||||||
plans_names
A list of plan names that the coupon may be applied to. |
||||||||
redeem_by
the date and time the coupon will expire and can no longer be redeemed. |
||||||||
redemption_resource
Indicates if the coupon is for all eligible charges on the account or only a specific subscription. Possible values are:
|
||||||||
state
The coupon’s redemption status. Possible values are:
|
||||||||
temporal_amount
Applicable when |
||||||||
temporal_unit
Applicable when
|
||||||||
unique_coupon_codes_count
The total number of unique redemptions for the coupon. |
invoices
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The invoices
table contains info about the invoices for a Recurly site. An invoice relates charges, credits, and payments together. When a subscription is created or renewed or a charge is created on the account, Recurly will sum the charges, discount or tax as appropriate, and send the invoice out for collection.
id
The invoice ID. Reference:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
updated_at
The date and time the invoice was last updated. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
account
Details about the account associated with the invoice. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
address
Details about the address associated with the invoice.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
balance
The outstanding balance remaining on this invoice. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
closed_at
The date the invoice was marked paid or failed. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
collection_method
The collection method for the invoice. Possible values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
created_at
The date and time the invoice was created. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
credit_payments
Details about the credit payments associated with the invoice.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
currency
The three-letter ISO 4217 currency code. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
customer_notes
The customer notes text specified in Invoice Settings. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
discount
The total amount of discounts applied on the invoice. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
due_at
The date and time the invoice is due. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
line_items
Details about the line items in the invoice.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
net_terms
An integer representing the number of days after an invoice’s creation that the invoice will become past due. If set to |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
number
If VAT taxation and the Country Invoice Sequencing feature are enabled, invoices will have country-specific invoice numbers for invoices billed to EU countries (ex: FR1001). Non-EU invoices will continue to use the site-level invoice number sequence. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
object
This will be |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
origin
The event that created the invoice. Possible values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
paid
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
po_number
For manual invoicing, the PO number associated with the subscription. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
previous_invoice_id
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
refundable_amount
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
state
The state of the invoice. Possible values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
subscription_ids
If the invoice is charging or refunding one or more subscriptions, this will be a list of the associated subscription IDs. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
subtotal
The summation of charges, discounts, and credits, before tax. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
tax
The total tax on the invoice. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
tax_info
Details about the tax applied to the invoice.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
terms_and_conditions
This will default to the Terms and Conditions text specified on the Invoice Settings page in your Recurly admin. This specifies custom notes to add or override Terms and Conditions. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
total
The final total on this invoice. The summation of invoice charges, discounts, credits, and tax. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
transactions
Details about the transactions associated with the invoice.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type
The type of the invoice. Possible values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
vat_number
The VAT registration number for the customer on this invoice. This will come from the VAT Number field in the Billing Info or the Account Info depending on your tax settings and the invoice collection method. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
vat_reverse_charge_notes
VAT Reverse Charge Notes only appear if you have EU VAT enabled or are using your own Avalara AvaTax account and the customer is in the EU, has a VAT number, and is in a different country than your own. This will default to the VAT Reverse Charge Notes text specified on the Tax Settings page in your Recurly admin, unless custom notes were created with the original subscription. |
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The plans
table contains info about the plans in your Recurly account. A plan tells Recurly how much to charge customers.
id
The plan ID. Reference: |
||||
updated_at
The date and time the plan was last updated. |
||||
accounting_code
Accounting code for invoice line items for the plan. |
||||
auto_renew
Subscriptions will automatically inherit this value once they are active. If |
||||
code
The unique code to identify the plan. This is used in Hosted Payment Page URLs and in the invoice exports. |
||||
created_at
The date and time the plan was created. |
||||
currencies
Details about the currencies associated with the plan.
|
||||
deleted_at
The date and time the plan was deleted. |
||||
description
The description of the plan. |
||||
hosted_pages
The hosted pages associated with the plan.
|
||||
interval_length
The length of the plan’s billing interval in |
||||
interval_unit
The unit for the plan’s billing interval. Possible values are:
|
||||
name
This name describes the plan and will appear on the Hosted Payment Page and the subscriber’s invoice. |
||||
object
|
||||
setup_fee_accounting_code
Accounting code for invoice line items for the plan’s setup fee. |
||||
state
The current state of the plan. Possible values are:
|
||||
tax_code
Used by Avalara, Vertex, and Recurly’s EU VAT tax feature. The tax code values are specific to each tax system. If you are using Recurly’s EU VAT feature:
|
||||
tax_exempt
Indicates whether the plan is tax exempt. |
||||
total_billing_cycles
Automatically terminate subscriptions after a defined number of billing cycles. Number of billing cycles before the plan automatically stops renewing, defaults to null for continuous, automatic renewal. |
||||
trial_length
The length of the plan’s trial period in |
||||
trial_unit
The unit for the plan’s trial period. Possible values are:
|
plans_add_ons
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The plans_add_ons
table contains info about the add-ons in your Recurly account. An add-on is a charge billed each billing period in addition to a subscription’s base charge.
Note: To replicate this table, you must also have the plans
table set to replicate.
id
The plan add-on ID. Reference: |
||
updated_at
The date and time the add-on was last updated. |
||
accounting_code
The accounting code for invoice line items for this add-on. |
||
code
The unique identifier for the add-on within its plan. |
||
created_at
The date and time the add-on was created. |
||
currencies
The currencies associated with the add-on.
|
||
default_quantity
The default quantity for the hosted pages. |
||
deleted_at
The date and time the add-on was deleted. |
||
display_quantity
Determines if the quantity field is displayed on the hosted pages for the add-on. |
||
name
The add-on name. |
||
object
|
||
plan_id
The ID of the plan the add-on is associated with. Reference: |
||
state
The state of the add-on. Possible values are:
|
||
tax_code
Used by Avalara, Vertex, and Recurly’s EU VAT tax feature. The tax code values are specific to each tax system. If you are using Recurly’s EU VAT feature:
|
subscriptions
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The subscriptions
table contains info about the subscriptions in your Recurly account. Subscriptions are created when your customers subscribe to one of your plans. The customer’s subscription tells Recurly when and how much to bill the customer.
Custom fields
Stitch’s Recurly integration supports replicating custom fields for subscription objects.
id
The subscription ID. Reference:
|
|||||
updated_at
The date and time the subscription was last updated. |
|||||
account
Details about the account associated with the subscription.
|