Regional versions and self-hosted instances: which connector do I use?

Edited

Many providers sell the same product in several regions, editions or hosting models. Some of these are separate connectors in Apideck, and others are one connector with a setting. Pick the wrong one and the connection fails or connects to the wrong account. This article lists the common cases.

Separate connectors per edition or hosting model

Provider

Connectors

Use

Exact Online

Exact Online

Any country: your customer chooses the country domain (NL, BE, DE, ES, UK or .com) in the connection settings

Exact Online NL / Exact Online UK

Fixed to the Netherlands or the UK

QuickBooks

QuickBooks

QuickBooks Online

Intuit Enterprise Suite

Intuit Enterprise Suite. See QuickBooks Online vs Intuit Enterprise Suite

QuickBooks Desktop

The installed desktop product, through the QuickBooks Web Connector

Jira

Jira / Jira (API token)

Jira Cloud

Jira Data Center

Self-hosted Jira. See Jira Data Center: the connection doesn't become ready

GitLab

GitLab / GitLab Server

gitlab.com / self-managed GitLab

Sage Intacct

Sage Intacct / Sage Intacct REST

Same product, two APIs. See Sage Intacct: SOAP/XML vs REST

MYOB

MYOB / MYOB Acumatica

MYOB Business (AU/NZ) / MYOB Acumatica

One connector with a region or environment setting

Your customer chooses in the connection settings in Vault:

Connector

Setting

Exact Online

Country domain. Choose it before authorizing: it defaults to the Netherlands.

Sage Business Cloud Accounting

Country

Yuki

Region (NL or BE)

Zoho People

Data centre (.com, .eu, .in and others)

Microsoft Dynamics 365 Business Central

Environment (production or a sandbox)

Salesforce

Production or sandbox login

For Zoho Books and Zoho CRM, Apideck detects the customer's data centre when they sign in, so there's nothing to choose. Xero and NetSuite each work worldwide with one connector. For NetSuite, a sandbox account simply has its own account ID (ending in _SB1, _SB2 and so on).

Self-hosted and custom URLs

For self-hosted or instance-based products, your customer enters their own address in the connection settings. Examples: Jira Data Center, GitLab Server, GitHub Enterprise Server, Azure DevOps Server, Acumatica, MYOB Acumatica and Microsoft Dynamics (organisation URL).

  • The server must be reachable from the internet over HTTPS with a valid certificate. Instances only reachable inside a company network or VPN can't be connected. If the customer's firewall limits incoming traffic, they can allow Apideck's IP addresses.

  • Odoo connects only to Odoo Online addresses (yourcompany.odoo.com). Self-hosted Odoo on its own domain can't be connected.

  • Many other connectors ask for a subdomain or instance name, for example BambooHR, Zendesk, ServiceNow or Lucca. Enter only that part, not the full URL.

Not sure which one your customer has?

Ask your customer which product and region their login page shows, for example start.exactonline.co.uk or yourcompany.atlassian.net (Jira Cloud) versus jira.yourcompany.com (Jira Data Center). Each connector's Connection Guide in the connector catalog shows exactly what to enter.

Contact Apideck support through the Customer Portal (the Requests link at the top of this help center), your Slack channel with us, or support@apideck.com if you can't find the right connector for a customer's setup.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.