Become integration partner

Join the Vanta Integration Partner Program to publish your integration in the Vanta marketplace and reach thousands of security-conscious customers.

The Vanta Integration Partner Program is for software companies who want to build and publish a public integration to the Vanta marketplace. Public integrations let any Vanta customer connect your product through OAuth and automatically pull data into their compliance program.

Building an integration only for your own Vanta account? You don’t need to become a partner — follow the Build a private integration quickstart instead.

Why become a partner

Joining the program turns your integration into a co-marketed, customer-installable product on a platform used by thousands of fast-growing companies.

Reach Vanta customers

Get discovered by thousands of Vanta customers actively looking for integrations to automate their security and compliance evidence.

Marketplace listing

A dedicated listing page in the in-app Vanta marketplace, with your logo, description, category, and one-click install.

Co-marketing

Joint announcements, blog features, and inclusion in Vanta’s integration newsletters and customer communications when you launch.

Reduced compliance friction

Customers stay on your product longer when it removes manual evidence collection from their audits — a meaningful retention and expansion lever.

Partner support

Direct access to Vanta’s partnerships and engineering teams for integration design reviews, troubleshooting, and launch planning.

Who should apply

The program is a fit if you can answer yes to all of the following:

• You sell a SaaS product that produces data Vanta customers care about — identity, devices, vulnerabilities, infrastructure, HR, ticketing, training, vendor management, etc. See Supported resource types for examples.
• You can host a server-side OAuth client and a periodic job (typically hourly) to push data to Vanta on each customer’s behalf.
• You have engineering capacity for the build time, plus review and launch.
• You’re comfortable being listed publicly in Vanta’s marketplace and supporting shared customers post-launch.

How the process works

1. Apply

   Email [e-mail] with:

   • Your company name and product URL
   • A short description of the integration you want to build (what data flows into Vanta, and the customer problem it solves)
   • The engineering contact who’ll own the build

   Vanta’s partnerships team reviews fit and responds within a few business days. If approved, you’ll be provisioned a partner email of the form [your_email]+connectors@[your_company].com for accessing the Developer Console.

2. Build your integration

   Follow the Build an Integration quickstart to:

   • Create a Build Integrations → Public application in the Developer Console
   • Implement the OAuth 2.0 authorization-code flow, including state validation on callback for CSRF protection
   • Push your first resource (most partners start with UserAccount) on an hourly schedule
   • Wire up token refresh and the Suspend API for clean disconnects

   Vanta’s team is available to answer questions and review your design before you go to review.

3. Test end-to-end

   Before submitting for review, complete a full OAuth flow and at least one resource sync against a live Vanta tenant. Vanta will provision a tenant for you for development and testing.

4. Submit for marketplace review

   Follow List your integration to send Vanta your marketing assets (logo, descriptions, customer setup guide URL) and request a marketplace review. Vanta validates the OAuth flow, the resources you push, and your customer-facing setup documentation.

   Most reviews complete within one to two weeks. You’ll get a single consolidated round of feedback — fix and resubmit if needed.

5. Launch

   Once approved, Vanta enables your listing and any joint marketing (if approved). Customers can then discover and install your integration directly from the in-app marketplace.

   After launch, monitor installs and resource ingestion in the Developer Console, and subscribe to Webhooks for install, uninstall, and disconnect events.

What Vanta provides

• A partner email and Developer Console access for creating Public Build Integrations applications and managing OAuth credentials.
• A documented API surface — OAuth, the Build Integrations REST API, document upload via GraphQL, and webhooks.
• Design and review support from the partnerships and engineering teams during build and review.
• A marketplace listing with your logo, description, and a one-click install flow surfaced to every Vanta customer.

What you’re responsible for

• Building and operating the integration — running the OAuth client, hourly sync job, and any document upload pipeline against your customers’ Vanta tenants.
• Securing tokens — client_secret, access_token, and refresh_token values per customer.
• Customer setup documentation — a public page that walks shared customers through enabling the integration.
• Tier-1 support for shared customers when the integration breaks on your side.
• Notifying Vanta of metadata or scope changes after launch — some changes require re-review.

FAQ

How long does the whole process take?

Most partners complete the build in about 1 week of engineering time. Review and marketing prep typically take one to two weeks on top of that, for a total of 2–4 weeks from intake to live listing.

Is there a cost to become a partner?

No. The Vanta Integration Partner Program is free to join.

Can I build a private integration first and convert later?

Private integrations cannot be automatically converted to public ones — you’ll need to create a separate public app. Private integrations are best for testing your integration in your Vanta test sandbox. When you’re ready to roll out to customers, create a Build Integrations → Public app and switch the OAuth flow over. Resource schemas and the data plane are identical between the two.

What happens when my integration is published?

Once your public integration is approved and published, it goes live to all Vanta customers at once via the marketplace.

What data can my integration push?

Anything Vanta supports as a resource type — UserAccount, computers and devices, vulnerabilities, custom resources, and more — plus document uploads for file-based evidence. Pick the types that match the data your product owns.

What if I need a resource type that doesn't exist?

Use Custom Resources to model data Vanta doesn’t have a built-in type for. If you’re building something many customers will need, mention it during intake — the team can advise on whether a built-in type makes sense.

What changes after launch require re-review?

Adding new scopes, changing resource types you push, or significantly changing the integration’s behavior require Vanta to re-validate the listing. Cosmetic changes to your description, logo, or setup guide do not. Email [e-mail] when in doubt.

Next steps

Apply to the program

Email [e-mail] with your company, product, and proposed integration.

Build an Integration

The end-to-end technical quickstart — OAuth, first resource, and verification.

List your integration

Submission checklist and marketplace review process.

Build Integrations API

Full reference for every endpoint available to public integrations.