When does a software integration need the vendor's approval?

The line most vendors draw

Every software vendor that lets outside software connect has to answer one question: who is this connection for?

If it's for one customer, connecting to that customer's own account, the vendor's risk is contained. The customer chose it. The customer controls it. Only the customer's data is in play.

If it's for many customers, the vendor is effectively vouching for it. Its customers will find it in a marketplace, install it in a click and trust it with their records. That's where reviews, security questionnaires and certification come in.

Most vendors call these private apps and public apps, or something close. The names vary. The logic is almost always the same.

A scene that plays out often

An operations director wants the CRM to stop retyping orders into the accounting system. She finds a capable freelancer, agrees a scope and a start date.

Three weeks in, the freelancer hits a wall. The accounting vendor only opens that kind of access to approved partners. Or the plan the company is on doesn't include it. Or the freelancer has been testing with keys issued to their own company, and now nobody is sure who owns what.

None of that is a coding problem. All of it could have been settled with a few questions before the first invoice.

Real examples, and how they differ

The pattern holds across vendors. The details don't. A few examples from vendor documentation, checked in November 2026:

• Shopify. An app with custom distribution installs on one store, or the stores in one Plus organization, through an install link. App Store review is part of public distribution. Since January 1, 2026, new custom apps can't be created inside the Shopify admin; they're set up through Shopify's developer tools instead.
• Clio. Private apps for Clio Manage serve a single Clio account. Clio's handbook says they are not reviewed by Clio and can't be published in its App Directory. Public apps go through Clio's approval process.
• Jobber. An app can stay in draft and connect to up to five paying Jobber accounts without app review. Going past five requires Jobber's approval.
• HubSpot. Legacy private apps can no longer be created: the cutoff was September 28, 2026 for newer accounts and October 26, 2026 for older ones. Existing ones keep working. New connections to your own account use HubSpot's newer developer platform.
• Xero. From December 1, 2026, you can't create a new Custom Connection, Xero's single-organization connection type. Existing ones keep working. Xero's developer tiers also cap how many organizations an app can connect to, starting at five on the entry tier.
• QuickBooks Online. Intuit asks every app that will reach live QuickBooks data to complete its app assessment questionnaire, whether or not the app is ever listed in its App Store.

Read that list again and notice the spread. One vendor skips review entirely for private use. Two cap the number of accounts. One asks every app, listed or not, for an assessment. Two changed their rules this autumn.

That spread is the point. You can't assume. You have to ask.

The answer can also change while you work. A route that existed when a project was scoped can close before it ships. A company that planned a Xero Custom Connection for early 2027 now needs a different path. Check the vendor's developer changelog when you start, and again before launch.

What "approval" can mean

When people ask whether they need the vendor's approval, they usually mean one of several different things:

• Nothing at all. You create a private app in your own account and connect it. The developer terms still apply.
• A questionnaire. The vendor asks how the app handles data and security before it reaches live records.
• A limit. The app works without review until it connects to more than a set number of accounts.
• A plan or add-on. Developer access exists, but only on certain tiers.
• A partner agreement. The developer must be approved by the vendor before connecting to any customer.
• Certification. A full review, usually for apps listed in the vendor's marketplace and offered to many customers.

A project built for one company usually lands in the first four. The last two mostly apply to software companies selling to many customers. Knowing which one applies tells you how long the path is.

When there's no customer route

Some vendors don't offer a do-it-yourself path. Their connections run through a partner program. A developer applies, signs an agreement and is approved before connecting to any customer's account, including yours.

You see this most often in property-management, field-service and healthcare software. It's a reasonable choice for vendors that hold sensitive records. It does change the plan.

If your vendor works this way, the usual options are an existing partner app that covers the need, a feature the vendor builds, a developer who already holds a partner agreement, or a new partner application. Know which before you scope the project.

Sometimes the honest answer is that the connection you want isn't available yet. Better to learn that on the first day than in the sixth week.

A buyer's checklist

Before you hire a developer, an agency or anyone else, get clear answers to these. Your account manager or the vendor's developer documentation should cover most of them.

• Is there a route for a developer working for us? Ask in those words. "Can our contractor build a private connection to our own account?" gets a clearer answer than "do you integrate with other software?"
• Which plan or add-on does it need? Some vendors include developer access in every plan. Others reserve it for higher tiers or sell it separately.
• Is there a review, and how long does it take? Even private routes can involve a questionnaire or a cap on connected accounts.
• Who owns the access keys? They should be issued to your company, kept in your environment and visible to your administrator.
• Where does the software run? Ideally in a cloud account your company owns. Some vendors expect it.
• How do we revoke access? Your admin should be able to switch the connection off in minutes, without calling the developer.
• Is there a test environment? Building against live records from the first day is avoidable risk.
• What changes are coming? Ask whether the developer program has announced retirements or new requirements. The HubSpot and Xero changes above were announced well ahead of time.

Keep the answers in writing, with the date. If a rule changes later, you'll know what you were told and when.

If the vendor says no

A no is useful information. It saves you from building something you'd later have to switch off.

Ask what the vendor does allow. Sometimes a report export, a scheduled file or a certified marketplace app covers most of the need. Sometimes the vendor has the feature on its roadmap and can give you a date.

And sometimes the right move is to connect everything around that system and leave it as the one place people still enter by hand. That's a smaller win, but a real one. Either way, you've spent a few conversations, not a budget.

What most guides miss

Approval is about the arrangement, not the code. The same software can be fine or prohibited depending on whose name it's registered under and where it runs. ServiceTitan, for example, approves apps a customer creates and hosts, and prohibits a third party using that customer's access keys. Our guide on building your own ServiceTitan integration walks through that case.

"No review" doesn't mean "no rules." Private apps still sit under the vendor's developer terms. Skipping a marketplace listing doesn't skip the terms you agreed to when you created the app.

Growth can move you across the line. A private connection built for one company can become something else when you add sister companies, franchise locations or clients. Jobber's five-account cap is a simple example. Know where the line is before the business grows past it.

The developer's name shouldn't be on anything that matters. If the app, the keys or the hosting account belong to the contractor, you don't fully own your connection. That's fixable on the first day and painful on the last.

Your vendor's rep is an ally. Vendors want customers to get more out of their product. A clear question asked early usually gets a clear answer, and sometimes a pointer to a feature you didn't know you had. Ask them to confirm the answer by email. It costs them a minute and gives your project a written footing.

How we do it

We check this first, on the free intro call: whether your vendor allows a developer working for you, on which plan, and under what review. If the answer is no, we say so and help you find the route that works. When we build, the connection is registered to you, runs where you control it, and you hold the keys. Book an intro call.

Sources

1. Shopify: Select a distribution method
2. Shopify: Legacy custom apps can't be created after January 1, 2026
3. Clio developer handbook: Building private apps
4. Jobber Developer Center: App review process
5. HubSpot Developer Changelog: Legacy private app creation sunset
6. HubSpot: Legacy private apps
7. Xero Developer: Custom integration FAQ
8. Xero Developer: Tiers, connection limits and API usage
9. Intuit Developer: Publish your app
10. ServiceTitan: Understand approved integration paths in ServiceTitan