PPlatformAppStores

Pipedrive Marketplace

General SaaS

Pipedrive Inc. · General SaaS app marketplaces

Best for: Vendors adding CRM-adjacent functionality for Pipedrive sales teams.

Overview

Pipedrive Marketplace lists apps built against Pipedrive's REST API and App Extensions SDK, which can add custom panels, actions, and automations inside the Pipedrive deal pipeline. Public apps use OAuth 2.0; simpler internal integrations can use personal API tokens.

How to build & ship

  1. 1Open Developer Hub (Tools and Integrations) and register a draft app to get client_id and client_secret
  2. 2Implement the OAuth 2.0 authorization-code flow with the redirect URL and requested scopes
  3. 3Call the Pipedrive REST API to read and write deals, persons, and other CRM data (optionally scaffold with create-pipedrive-app)
  4. 4Add App Extensions (app panels, custom UI actions, JSON modals) and/or webhooks for real-time events
  5. 5Complete the marketplace listing details and run the app-approval QA checklist
  6. 6Submit the app for review to make it public

Key APIs & SDKs

Pipedrive REST API (v1/v2)
OAuth 2.0
Webhooks
App Extensions (panels, custom UI actions, JSON modals)
create-pipedrive-app scaffolder
Developer Hub

Integration types

Embedded app
Connector
Workflow action

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key
  • Security review: Required
  • Marketplace app review covers functionality, security, and UX guidelines.
  • Every public app goes through Pipedrive's app-approval review of the listing, OAuth flow, and functionality after a self-QA checklist; approval is typically days to a couple of weeks (not officially fixed).
  • Token-bucket API rate limits per company account.
Auth docs Store policies

Monetization

Free
Paid app
Usage-based
Onboarding
$0
Commission
20% on Marketplace-billed subscriptions
Merchant of Record
Pipedrive acts as MoR for Marketplace-billed apps

Pros & cons for builders

Pros

  • Direct reach into a focused, sales-oriented CRM user base
  • Rich embedding via App Extensions, not just API calls
  • Clear OAuth flow and scaffolding tooling
  • Private apps are possible for single-org use

Cons

  • Audience limited to Pipedrive CRM customers
  • Public listing requires passing a review and maintaining the listing
  • Deeper UI extensions add development and maintenance overhead