This integration is powered by Singer's Invoiced tap. For support, visit the GitHub repo or join the Singer Slack.
Invoiced integration summary
Stitch’s Invoiced integration replicates data using the Invoiced REST API. Refer to the Schema section for a list of objects available for replication.
Invoiced feature snapshot
A high-level look at Stitch's Invoiced (v1) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status |
Released on March 21, 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 Invoiced
Step 1: Generate an Invoiced API key
- Sign into your Invoiced account.
- Click Settings on the left side of the page.
- In the Business Settings section, click Developers.
- On the Developers page, click the New API Key button. A New API Key window will display.
- In the Key Description field, enter a description that identifies the API key. For example:
Stitch
- Click Save. This will direct you back to the Developers page after the API key is created.
-
A section for the new API key will display on the Developers page. Click the Show Secret link next to the name of the API key to display it:
Leave this page open for now - you’ll need it to complete the setup in Stitch.
Step 2: Add Invoiced as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Invoiced 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 Invoiced” would create a schema called
stitch_invoiced
in the destination. Note: Schema names cannot be changed after you save the integration. - In the API Key field, paste your Invoiced API key.
- If the Invoiced instance you’re connecting to is a sandbox, check the Is this a sandbox connection? box.
Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Invoiced 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 Invoiced’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.
Invoiced 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 Invoiced 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 Invoiced, 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.
Invoiced 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 Invoiced 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.
credit_notes
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The credit_notes
table contains info about the credit notes in your Invoiced account. A credit note represents a balance you owe to a customer.
id
The credit note ID. Reference: |
|||||||||||||||||||||||
updated_at
The timestamp when the credit note was last updated. |
|||||||||||||||||||||||
balance
The balance owed on the credit note. |
|||||||||||||||||||||||
closed
If |
|||||||||||||||||||||||
created_at
The timestamp when the credit note was created. |
|||||||||||||||||||||||
currency
The three letter ISO code for the currency used in the credit note. |
|||||||||||||||||||||||
customer
The ID of the customer associated with the credit note. Reference: |
|||||||||||||||||||||||
date
The date of the credit note. |
|||||||||||||||||||||||
discounts
The discounts associated with the credit note.
|
|||||||||||||||||||||||
draft
If |
|||||||||||||||||||||||
invoice
The ID of the invoice associated with the credit note. Reference: |
|||||||||||||||||||||||
items
The line items associated with the credit note.
|
|||||||||||||||||||||||
metadata
Additional information about the credit note. |
|||||||||||||||||||||||
name
The internal name of the credit note. |
|||||||||||||||||||||||
notes
Additional notes displayed on the credit note. |
|||||||||||||||||||||||
number
The reference number assigned to the credit note, used in the Invoiced dashboard. |
|||||||||||||||||||||||
paid
If |
|||||||||||||||||||||||
status
The status of the credit note. Possible values are:
|
|||||||||||||||||||||||
subtotal
The subtotal of the credit note. |
|||||||||||||||||||||||
taxes
The taxes associated with the credit note.
|
|||||||||||||||||||||||
total
The total of the credit note. |
customers
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The customers
table contains info about the customers in your Invoiced account.
id
The customer ID. Reference: |
|||||||||||
updated_at
The time the customer was last updated. |
|||||||||||
address1
The first line of the customer’s address. |
|||||||||||
address2
The second line of the customer’s address. |
|||||||||||
attention_to
Used for |
|||||||||||
autopay
If |
|||||||||||
chase
|
|||||||||||
chasing_cadence
|
|||||||||||
city
The city of the customer’s address. |
|||||||||||
country
The two-letter ISO code of the customer’s country. |
|||||||||||
created_at
The time the customer was created. |
|||||||||||
credit_hold
|
|||||||||||
credit_limit
The credit limit for the customer. |
|||||||||||
email
The customer’s email address. |
|||||||||||
language
The two-letter ISO code of the customer’s language. |
|||||||||||
metadata
Additional information about the customer. |
|||||||||||
name
The name of the customer. |
|||||||||||
next_chase_step
|
|||||||||||
notes
Additional notes about the customer. |
|||||||||||
number
A unique ID used to tie the customer to external systems. |
|||||||||||
parent_customer
|
|||||||||||
payment_source
The customer’s payment source, if attached.
|
|||||||||||
payment_terms
The payment terms for the customer when AutoPay is not enabled. |
|||||||||||
phone
The customer’s phone number. |
|||||||||||
postal_code
The customer’s postal code. |
|||||||||||
sign_up_page
The ID of the sign up page used by the customer. |
|||||||||||
state
The customer’s state. |
|||||||||||
tax_id
The customer’s tax ID. |
|||||||||||
taxable
If |
|||||||||||
taxes
The taxes applicable to the customer.
|
|||||||||||
type
The customer’s type. Possible values are:
|
estimates
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The estimates
table contains info about the estimates, or quotes you provide to customers, in your Invoiced account.
id
The estimate ID. |
||||||||||||||||||
updated_at
The time the estimate was last updated. |
||||||||||||||||||
approved
Indicates whether the estimate has been approved. |
||||||||||||||||||
balance
The balance of the estimate. |
||||||||||||||||||
closed
If |
||||||||||||||||||
created_at
The time the estimate was created. |
||||||||||||||||||
currency
The three letter ISO code used by the estimate. |
||||||||||||||||||
customer
The ID of the customer associated with the estimate. Reference: |
||||||||||||||||||
date
The date of the estimate. |
||||||||||||||||||
deposit
The deposit required for the estimate. |
||||||||||||||||||
deposit_paid
Indicates whether the |
||||||||||||||||||
discounts
The discounts applicable to the estimate.
|
||||||||||||||||||
draft
If |
||||||||||||||||||
expiration_date
The expiration date of the estimate. |
||||||||||||||||||
invoice
The ID of the invoice associated with the estimate. Reference: |
||||||||||||||||||
items
The line items associated with the estimate.
|
||||||||||||||||||
metadata
Additional information about the estimate. |
||||||||||||||||||
name
The name of the estimate. |
||||||||||||||||||
notes
Additional notes about the estimate. |
||||||||||||||||||
number
The reference number assigned to the estimate. |
||||||||||||||||||
paid
Indicates if the estimate has been paid. |
||||||||||||||||||
payment_terms
The payment terms for the estimate. |
||||||||||||||||||
status
The status of the estimate. Possible values are:
|
||||||||||||||||||
subtotal
The subtotal of the estimate. |
||||||||||||||||||
taxes
The taxes applicable to the estimate.
|
||||||||||||||||||
total
The total of the estimate. |
invoices
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The invoices
table contains info about the invoices in your Invoiced account. An invoice represents a balance owed to you by a customer.
id
The invoice ID. Reference: |
|||||||||||||||||||||||
updated_at
The time the invoice was last updated. |
|||||||||||||||||||||||
attempt_count
The number of payment attempts for the invoice. |
|||||||||||||||||||||||
autopay
If |
|||||||||||||||||||||||
balance
The balance of the invoice. |
|||||||||||||||||||||||
closed
If |
|||||||||||||||||||||||
created_at
The time the invoice was created. |
|||||||||||||||||||||||
currency
The three letter ISO code used by the invoice. |
|||||||||||||||||||||||
customer
The ID of the customer associated with the invoice. Reference: |
|||||||||||||||||||||||
date
The date of the invoice. |
|||||||||||||||||||||||
discounts
The discounts applicable to the estimate.
|
|||||||||||||||||||||||
draft
If |
|||||||||||||||||||||||
due_date
The due date of the invoice. |
|||||||||||||||||||||||
items
The line items associated with the invoice.
|
|||||||||||||||||||||||
metadata
Additional information about the invoice. |
|||||||||||||||||||||||
name
The name of the invoice. |
|||||||||||||||||||||||
needs_attention
|
|||||||||||||||||||||||
next_payment_attempt
The time of the next scheduled payment attempt, when in automatic collection. |
|||||||||||||||||||||||
notes
Additional notes about the invoice. |
|||||||||||||||||||||||
number
The reference number assigned to the invoice. |
|||||||||||||||||||||||
paid
Indicates whether an invoice has been paid in full. |
|||||||||||||||||||||||
payment_terms
The payment terms for the invoice. |
|||||||||||||||||||||||
status
The status of the invoice. Possible values are:
|
|||||||||||||||||||||||
subscription
The subscription ID, if the invoice came from a subscription. Reference: |
|||||||||||||||||||||||
subtotal
The subtotal of the invoice. |
|||||||||||||||||||||||
taxes
The taxes applicable to the invoice.
|
|||||||||||||||||||||||
total
The total of the invoice. |
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The plans
table contains info about the plans in your Invoiced account. A plan describes a fixed amount that is billed to customers over a recurring interval.
amount
Plan amount. Not applicable when pricing mode is custom. |
catalog_item
Item ID the plan belongs to |
created_at
Timestamp when created |
currency
3-letter ISO code |
description
|
id
The plan’s unique ID |
interval
One of day, week, month, year. The frequency with which a subscription should be billed. |
interval_count
The number of intervals between each subscription billing. Defaults to 1. |
metadata
A hash of key/value pairs that can store additional information about this object. |
name
Plan name |
notes
|
object
Object type, plan |
pricing_mode
per_unit, volume, tiered or custom |
quantity_type
constant or usage |
tiers
|
updated_at
Timestamp when updated |
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 Invoiced account.
id
The subscription ID. Reference: |
||||||
updated_at
The time the subscription was last updated. |
||||||
addons
Details about subscription’s add ons.
|
||||||
cancel_at_period_end
If |
||||||
canceled_at
The time when the subscription was canceled. |
||||||
contract_period_end
|
||||||
contract_period_start
|
||||||
contract_renewal_cycles
|
||||||
contract_renewal_mode
|
||||||
created_at
The time when the subscription was created. |
||||||
customer
The ID of the customer associated with the subscription. Reference: |
||||||
cycles
The number of billing cycles the subscription runs for. When |
||||||
discounts
The discounts applicable to the subscription.
|
||||||
metadata
|
||||||
mrr
The amount the subscription contributes to monthly recurring revenue. |
||||||
period_end
The start of the current billing period. |
||||||
period_start
The end of the current billing period. |
||||||
plan
The ID of the plan associated with the subscription. Reference: |
||||||
quantity
The plan quantity. |
||||||
recurring_total
The total recurring amount, including taxes. |
||||||
renewed_last
The date the subscription was last renewed. |
||||||
renews_next
The date the subscription renews next. |
||||||
start_date
The time the subscription starts, or started. |
||||||
status
The status of the subscription. Possible values are:
|
||||||
taxes
The taxes applicable to the subscription.
|
transactions
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
The transactions
table contains info about the transactions in your Invoiced account.
id
The transaction ID. Reference: |
|||||||||||
updated_at
The time the transaction was last updated. |
|||||||||||
amount
The amount of the transaction. |
|||||||||||
created_at
The time the transaction was created. |
|||||||||||
credit_note
The ID of the credit note associated with the transaction, if any. Reference: |
|||||||||||
currency
The three letter ISO code used by the transaction. |
|||||||||||
customer
The ID of the customer associated with the estimate. Reference: |
|||||||||||
date
The date of the transaction. |
|||||||||||
failure_reason
The failure message from the payment gateway when |
|||||||||||
gateway
The payment gateway that processed the transaction, if any. |
|||||||||||
gateway_id
The transaction ID from the payment gateway. |
|||||||||||
invoice
The ID of the invoice associated with the transaction, if any. |
|||||||||||
metadata
Additional details about the transaction. |
|||||||||||
method
The payment instrument used to facilitate the transaction. Possible values are:
|
|||||||||||
notes
Additional notes about the transaction. |
|||||||||||
parent_transaction
For refunds, the ID of the original transaction. Reference: |
|||||||||||
payment_source
The transactions’s payment source, if attached.
|
|||||||||||
status
The status of the transaction. Possible values are:
|
|||||||||||
type
The type of the transaction. Possible values are:
|
Related | Troubleshooting |
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.