|
41969
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)...
|
Firefox
|
Pipedrive API v2 migration guide — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41969
|
|
41970
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said...
|
Firefox
|
Pipedrive API v2 migration guide — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41970
|
|
41971
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
You said
ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
Expand
Listen
Gemini said
Gemini said
This is a critical time for Pipedrive integrations.
As of mid-2024, Pipedrive is undergoing a massive shift from
API v1 to API v2
, with a hard deprecation date for many v1 features set for
July 2026
.
View source details for citation from Make Help Center. Opens side panel.
Here is the deep-dive comparison to help you decide.
1. API v1 vs. API v2 Support
1. API v1 vs. API v2 Support
This is the most important factor for a new project in 2024/2025.
pipedrive/client-php
(Official):
Fully supports
both v1 and v2
. It recently introduced version-specific namespaces (
Pipedrive\versions\v1
and
Pipedrive\versions\v2
).
It is built to help you migrate.
Since v2 is the future (offering better performance and lower "token costs" against rate limits), this SDK is future-proof.
View source details for citation from GitHub. Opens side panel.
IsraelOrtuno/pipedrive
(Community):
This package is primarily a wrapper for
API v1
. While it is elegant, it lacks native, structured support for the new v2 endpoints. Using this today means you are building on a foundation that Pipedrive is actively trying to phase out.
2. Maintenance & Activity
2. Maintenance & Activity
Feature
pipedrive/client-php
(Official)
IsraelOrtuno/pipedrive
(Community)
Last Updated
Days/Weeks ago.
Highly active.
Months/Years ago.
Much slower pace.
Open Issues
Managed by a dedicated team at Pipedrive.
Managed by a single developer/community.
Response Time
High. Critical bugs are patched quickly.
Low. Many community packages lose steam over time.
PHP 8.x Support
Native and tested.
Generally works, but lacks modern PHP optimizations.
Feature
Last Updated
Open Issues
Response Time
PHP 8.x Support
pipedrive/client-php
(Official)
Days/Weeks ago....
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41971
|
|
41972
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and...
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41972
|
|
41973
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer....
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41973
|
|
41974
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
Zapier Help Center help.zapier.com Action required: Update your Pipedrive workflows before the V1 API deprecation – Zapier Updated 1 day ago. Pipedrive is deprecating all V1 API endpoints on July 31, 2026. If you use Pipedrive with Zapier, you may need to update your workflows to ...
Zapier Help Center
help.zapier.com
Action required: Update your Pipedrive workflows before the V1 API deprecation – Zapier
Updated 1 day ago. Pipedrive is deprecating all V1 API endpoints on July 31, 2026. If you use Pipedrive with Zapier, you may need to update your workflows to ...
Next slide
Summarize page
Summarize page
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive’s v1 API has been constantly evolving, but it is still based on the same foundations that were laid a long time ago. Pipedrive as a company has grown a lot since then and it is time to reflect that in our API as well. Hence, we are announcing a gradual transition to a new v2 version of our API.
The new v2 API comes with many benefits such as
a lot less breaking changes;
lower
rate limiter token costs
rate limiter token costs
per endpoint;
significantly better performance and response times, especially when iterating over large data sets;
consistent and predictable behavior with compliance with REST best practices;
better data quality due to stricter input validation.
What is changing? Skip link to What is changing?
What is changing?
Skip link to What is changing?
We will gradually release new v2 APIs to replace the corresponding parts of v1 API. The corresponding v1 APIs will then be marked for deprecation and have a grace period of at least 1 year for migrations.
API v2 availability Skip link to API v2 availability
API v2 availability
Skip link to API v2 availability
Currently the following APIs are available as v2:
Activities API
Deals API
Deal Followers API
Deal Products API
Fields API (ActivityFields, DealFields, OrganizationFields, PersonFields, ProductFields)...
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41974
|
|
41975
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
Pipedrive API Changelog
Pipedrive API Changelog
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
client-php/docs/versions/v2/README.md at master · pipedrive/client-php
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
Zapier Help Center help.zapier.com Action required: Update your Pipedrive workflows before the V1 API deprecation – Zapier Updated 1 day ago. Pipedrive is deprecating all V1 API endpoints on July 31, 2026. If you use Pipedrive with Zapier, you may need to update your workflows to ...
Zapier Help Center
help.zapier.com
Action required: Update your Pipedrive workflows before the V1 API deprecation – Zapier
Updated 1 day ago. Pipedrive is deprecating all V1 API endpoints on July 31, 2026. If you use Pipedrive with Zapier, you may need to update your workflows to ...
Next slide
Summarize page
Summarize page
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ...
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
41975
|
|
46626
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
Pipedrive API v2 overview
Pipedrive API v2 overview
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive’s v1 API has been constantly evolving, but it is still based on the same foundations that were laid a long time ago. Pipedrive as a company has grown a lot since then and it is time to reflect that in our API as well. Hence, we are announcing a gradual transition to a new v2 version of our API.
The new v2 API comes with many benefits such as
a lot less breaking changes;
lower
rate limiter token costs
rate limiter token costs
per endpoint;
significantly better performance and response times, especially when iterating over large data sets;
consistent and predictable behavior with compliance with REST best practices;
better data quality due to stricter input validation.
What is changing? Skip link to What is changing?
What is changing?
Skip link to What is changing?
We will gradually release new v2 APIs to replace the corresponding parts of v1 API. The corresponding v1 APIs will then be marked for deprecation and have a grace period of at least 1 year for migrations.
API v2 availability Skip link to API v2 availability
API v2 availability
Skip link to API v2 availability
Currently the following APIs are available as v2:
Activities API
Deals API
Deal Followers API
Deal Products API
Fields API (ActivityFields, DealFields, OrganizationFields, PersonFields, ProductFields)
Organizations API
Organization Followers API
Persons API
Person Followers API
Products API
Product Followers API
Product Variations API
Pipelines and Stages API
User Followers API
Search API
Migrating and overview of changes Skip link to Migrating and overview of changes
Migrating and overview of changes
Skip link to Migrating and overview of changes
We have compiled an in-depth
migration guide
migration guide
for migrating from v1 to v2 APIs and the endpoints are also documented on our
API Reference
API Reference
page. As always, you can reach out to us through our
Developers' Community
Developers' Community
for further questions.
Updated
5 months ago
Read next
Pipedrive API v2 Migration Guide
Pipedrive API v2 Migration Guide
Pipedrive API Reference
Pipedrive API Reference
Did this page help you?
Yes, this page helped me
Yes
No, this page did not help me
No
Copy Page
Copy Page
pipedrive.readme.io/docs/run-pipedrive-[API_KEY]...
|
Firefox
|
Pipedrive API v2 overview — Work
|
pipedrive.readme.io/docs/pipedrive-api-v2
|
46626
|
|
46661
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to main content
Skip to main content
Accessibility help
Accessibility help
Accessibility feedback
Accessibility feedback
Go to Google Home
https://pipedrive.readme.io/docs/api-versions
https://pipedrive.readme.io/docs/api-versions
Clear
Search by voice
Search by image
Search
Google apps
Google Account: [EMAIL]
AI Mode
AI Mode
All
All
Forums
Forums
Videos
Videos
Images
Images
Short videos
Short videos
News
News
More filters
More
Tools
Tools
Search Results
Search Results
Web results
Web results
Pipedrive API v2 overview ReadMe https://pipedrive.readme.io › docs › pipedrive-api-v2
Pipedrive API v2 overview
Pipedrive API v2 overview
ReadMe
https://pipedrive.readme.io
› docs › pipedrive-api-v2
About this result
We are announcing a gradual transition to a new v2
version
of our
API
. The new v2
API
comes with many benefits.
About the Pipedrive API ReadMe https://pipedrive.readme.io › docs › core-api-concepts-ab...
About the Pipedrive API
About the Pipedrive API
ReadMe
https://pipedrive.readme.io
› docs › core-api-concepts-ab...
About this result
Our Pipedrive RESTful API Reference can be accessed via
https://developers.pipedrive.com/docs/api/v1
/, where you will find a list of endpoints and their ...
Missing:
versions
| Show results with:
versions
versions
Pipedrive API Reference and Documentation Pipedrive https://developers.pipedrive.com › docs › api
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
Pipedrive
https://developers.pipedrive.com
› docs › api
About this result
This
Pipedrive API
reference and
documentation
helps you implement the RESTful
Pipedrive API
, enabling developers to build
integrations
with
Pipedrive
.
Missing:
readme.
| Show results with:
readme.
readme.
Changes to the API ReadMe https://pipedrive.readme.io › docs › changes-to-the-api
Changes to the API
Changes to the API
ReadMe
https://pipedrive.readme.io
› docs › changes-to-the-api
About this result
Changes to the
Pipedrive API
can be divided into breaking and non-breaking changes. A breaking change is a backward incompatible change that may require ...
Pipedrive API v2 migration guide ReadMe https://pipedrive.readme.io › docs › pipedrive-api-v2-mi...
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
ReadMe
https://pipedrive.readme.io
› docs › pipedrive-api-v2-mi...
About this result
This document outlines the differences between
Pipedrive API
v1 and v2 of endpoints which are available on v2. Where available, please use
API
v2 for the best ...
Pipedrive\versions\v1\FiltersApi - client-php GitHub https://github.com › blob › master › docs › versions › Api
Pipedrive\versions\v1\FiltersApi - client-php
Pipedrive\versions\v1\FiltersApi - client-php
GitHub
https://github.com
› blob › master › docs › versions › Api
About this result
Pipedrive API client for PHP
. Contribute to pipedrive/client-php development by creating an account on GitHub.
People also ask
People also ask
What is API v1 and v2?
What is API v1 and v2?
Is Pipedrive API free?
Is Pipedrive API free?
Where can I find the Pipedrive API?
Where can I find the Pipedrive API?
Where is the Pipedrive API?
Where is the Pipedrive API?
Web results
Web results
Webhooks v2 migration guide ReadMe https://pipedrive.readme.io › docs › webhooks-v2-migrat...
Webhooks v2 migration guide
Webhooks v2 migration guide
ReadMe
https://pipedrive.readme.io
› docs › webhooks-v2-migrat...
About this result
Learn how to migrate your Pipedrive webhooks from version 1 to version 2
in this migration guide with webhook v2 payload examples.
updateOrganization makes "name" required since v13.2.5 Pipedrive https://devcommunity.pipedrive.com › updateorganizati...
updateOrganization makes "name" required since v13.2.5
updateOrganization makes "name" required since v13.2.5
Pipedrive
https://devcommunity.pipedrive.com
pipedrive.readme.io/docs/core-[API_KEY]...
|
Firefox
|
https://pipedrive.readme.io/docs/api-versions - Go
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46661
|
|
46662
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to main content
Skip to main content
Accessibility help
Accessibility help
Accessibility feedback
Accessibility feedback
Go to Google Home
https://pipedrive.readme.io/docs/api-versions
https://pipedrive.readme.io/docs/api-versions
Clear
Search by voice
Search by image
Search
Google apps
Google Account: [EMAIL]
AI Mode
AI Mode
All
All
Forums
Forums
Videos
Videos
Images
Images
Short videos
Short videos
News
News
More filters
More
Tools
Tools
Search Results
Search Results
Web results
Web results
Pipedrive API v2 overview ReadMe https://pipedrive.readme.io › docs › pipedrive-api-v2
Pipedrive API v2 overview
Pipedrive API v2 overview
ReadMe
https://pipedrive.readme.io
› docs › pipedrive-api-v2
About this result
We are announcing a gradual transition to a new v2
version
of our
API
. The new v2
API
comes with many benefits.
About the Pipedrive API ReadMe https://pipedrive.readme.io › docs › core-api-concepts-ab...
About the Pipedrive API
About the Pipedrive API
ReadMe
https://pipedrive.readme.io
› docs › core-api-concepts-ab...
About this result
Our Pipedrive RESTful API Reference can be accessed via
https://developers.pipedrive.com/docs/api/v1
/, where you will find a list of endpoints and their ...
Missing:
versions
| Show results with:
versions
versions
Pipedrive API Reference and Documentation Pipedrive https://developers.pipedrive.com › docs › api
Pipedrive API Reference and Documentation
Pipedrive API Reference and Documentation
Pipedrive
https://developers.pipedrive.com
› docs › api
About this result
This
Pipedrive API
reference and
documentation
helps you implement the RESTful
Pipedrive API
, enabling developers to build
integrations
with
Pipedrive
.
Missing:
readme.
| Show results with:
readme.
readme.
Changes to the API ReadMe https://pipedrive.readme.io › docs › changes-to-the-api
Changes to the API
Changes to the API
ReadMe
https://pipedrive.readme.io
› docs › changes-to-the-api
About this result
Changes to the
Pipedrive API
can be divided into breaking and non-breaking changes. A breaking change is a backward incompatible change that may require ...
Pipedrive API v2 migration guide ReadMe https://pipedrive.readme.io › docs › pipedrive-api-v2-mi...
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
ReadMe
https://pipedrive.readme.io
› docs › pipedrive-api-v2-mi...
About this result
This document outlines the differences between
Pipedrive API
v1 and v2 of endpoints which are available on v2. Where available, please use
API
v2 for the best ...
Pipedrive\versions\v1\FiltersApi - client-php GitHub https://github.com › blob › master › docs › versions › Api
Pipedrive\versions\v1\FiltersApi - client-php
Pipedrive\versions\v1\FiltersApi - client-php
GitHub
https://github.com
› blob › master › docs › versions › Api
About this result
Pipedrive API client for PHP
. Contribute to pipedrive/client-php development by creating an account on GitHub.
People also ask
People also ask
What is API v1 and v2?
What is API v1 and v2?
Is Pipedrive API free?
Is Pipedrive API free?
pipedrive.readme.io/docs/core-[API_KEY]...
|
Firefox
|
https://pipedrive.readme.io/docs/api-versions - Go
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46662
|
|
46663
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
About the Pipedrive API
About the Pipedrive API
📘
An
application programming interface
(API) is a set of functionalities that a service owner provides so people can use its features and/or build software applications. An API details how a user makes requests and the responses they receive in return.
Pipedrive is a sales CRM with an intuitive
RESTful API
RESTful API
, webhooks, app extensions and API clients to help you build
an app
an app
for the
Pipedrive Marketplace
Pipedrive Marketplace
.
Pipedrive RESTful API Skip link to Pipedrive RESTful API
Pipedrive RESTful API
Skip link to Pipedrive RESTful API
Our Pipedrive
RESTful API Reference
can be accessed via
https://developers.pipedrive.com/docs/api/v1/
https://developers.pipedrive.com/docs/api/v1/
, where you will find a list of endpoints and their descriptions.
Calls to our API are validated against an API token or an
access_token
when using
OAuth 2.0
OAuth 2.0
. Our API supports UTF-8 for character encoding. Learn how to find and use the
api_token
here
here
.
3687
Pipedrive Entity Relationship Diagram (ERD)
Webhooks Skip link to Webhooks
Webhooks
Skip link to Webhooks
Webhooks enable you to obtain real-time, programmatic notifications from Pipedrive regarding changes to your data as they happen. Instead of pulling information via our API, webhooks will push information to your endpoint.
You can create webhooks via the web app and our API. You can create a webhook programmatically by making a
POST
request to the webhook’s endpoint. Pipedrive will then send a notification when an event is triggered (e.g., a new lead is added) as an HTTP post with a JSON body to the endpoint(s) you have specified. Find out more about webhooks
here
here
.
App extensions Skip link to App extensions
App extensions
Skip link to App extensions
App extensions enable apps built for the Pipedrive Marketplace to give additional value to their users. With app extensions, the app’s functionality will be available directly inside the Pipedrive platform’s UI and users will be able to interact with and see the custom functionality of your app.
This also helps to increase your app's visibility and brand awareness, as the app icon will be displayed inside Pipedrive after a user has installed it. Find out more about app extensions
here
here
.
API clients Skip link to API clients
API clients
Skip link to API clients
Pipedrive API clients are available on
GitHub
GitHub
. Some of the most popular repositories include:
Client-nodejs
Client-nodejs
(official)
Client-php
Client-php
(official)
Pipedrive
Pipedrive
(community built)
Python-pipedrive
Python-pipedrive
(community built)
Pipedrive-dotnet
Pipedrive-dotnet
(community built)
Pipedrive.rb
Pipedrive.rb
(community built)
How Pipedrive API works Skip link to How Pipedrive API works
How Pipedrive API works
Skip link to How Pipedrive API works
📘
Do take note that entity/entities may be called “item/items” or “type of item/items” for the end user in the Pipedrive web and mobile app.
At the base of your Pipedrive account is a customer relationship management (CRM) database of your sales pipeline, processes and relationships. As organizing sales data is essential for sales activities, Pipedrive helps to
organize and link your data together
organize and link your data together
for better visibility through the core and adjacent entities.
Core entities Skip link to Core entities
Core entities
Skip link to Core entities
Within the Pipedrive API, we have core entities that consist of multiple endpoints. These core entities represent a larger area inside Pipedrive and can be found in the left-hand side menu in the Pipedrive web app. Tied to them are adjacent entities that contain supplementary information relevant to the core entities.
2041
Pipedrive core entities ERD
The ERD above shows how core entities are connected within Pipedrive.
As leads can be converted to deals, they are sometimes used in place of each other. For example, in the case of activities, an activity can be associated with either a lead or a deal. This goes the same for products.
Persons and organizations are considered contacts and are often grouped together.
Mailbox, found in the Mail tab of the Pipedrive web app, is the email control hub inside Pipedrive that stores all the emails a user decides to keep a record of. Mail is tracked and associated with persons and deals through Pipedrive’s email sync and Smart Bcc features.
[Entity] Fields endpoints allow you to obtain the near-complete schema of the respective core entities. You can add, update and delete main and custom fields through these adjacent entities.
Read on to discover how leads, deals, persons and organizations (contacts), activities, products and users are further connected to other core and adjacent entities.
Leads Skip link to Leads
Leads
Skip link to Leads
1847
Leads ERD
Leads
Leads
are prequalified, potential deals that are kept in a separate inbox called the Leads Inbox. Leads can subsequently be converted to deals via the Pipedrive web app and added to a pipeline.
Leads can have activities, emails (mailbox) and notes attached to them. They can also have multiple LeadLabels to categorize them and be linked with one LeadSource to indicate where the lead came from.
Key aspects of leads:
Leads must always have one person (contacts) or organization (contacts) linked with them
Leads can only have one source (LeadSource). Leads created through the API have a set source “API”.
Leads can only have the same
custom fields
custom fields
(DealFields) as deals
Leads can only be converted to deals via the Pipedrive web app\
Deals Skip link to Deals
Deals
Skip link to Deals
2443
Deals ERD
Deals
Deals
are ongoing transactions pursued with a person or an organization. It’s tracked and processed through the Stages of a pipeline until it’s won or lost. Deals can be converted from leads via the Pipedrive web app.
In Pipedrive, deals contain all actions taken towards closing a sale, for example, activities, emails (mailbox), notes and files, and have their own custom fields (DealFields). Products and subscriptions can also be attached to deals.
A deal can be linked with either a person or organization (contacts) but it must always have one contact linked with them. As a deal is associated with a contact, it will pull all information from the linked contact and, likewise, associate all actions performed on the deal with the linked contact.
Persons & organizations (contacts) Skip link to Persons & organizations (contacts)
Persons & organizations (contacts)
Skip link to Persons & organizations (contacts)
2073
Persons & organizations (contacts) ERD
Persons (or people) are the specific customers of the sales process, while
organizations
organizations
are the companies that the persons work at. Persons and organizations are considered contacts and they rest in one centralized hub in the Pipedrive web app. The ERD above depicts how different core and adjacent entities can either relate to contacts as a whole or persons/organizations specifically.
Both persons and organizations can have activities, notes and files attached to them and their respective main fields and custom fields (PersonFields and OrganizationFields). Emails (Mailbox) and products can only be linked to persons while OrganizationRelationships can only be linked to organizations.
Key aspects of Persons and organizations (contacts):
A person can only be linked to one organization
A lead or a deal must always have a person or an organization linked to it
Both persons and organizations can have multiple deals open for them at the same time
Activities Skip link to Activities
Activities
Skip link to Activities
2043
Activities ERD
Activities
Activities
are any actions a user does towards the closing of a sale. There are different types of activities (ActivityTypes) that can be performed, e.g. a phone call (CallLogs), a meeting or a task. You can have custom activity types and custom fields (ActivityFields) for activities. Users can schedule activities in relation to a person, an organization or a lead/deal.
Key aspects of activities:
Associating an activity with a deal will also associate the activity with the person and/or organization linked to the deal
Currently, Files
can only be added
can only be added
to activities via the API
CallLogs Skip link to CallLogs
CallLogs
Skip link to CallLogs
CallLogs for
calls made via the Pipedrive mobile app
calls made via the Pipedrive mobile app
are also considered activities, which means they can be associated with a deal, a person and/or an organization. Do note that CallLogs differ from other activities as they only receive the information needed to describe the phone call.
Projects Skip link to Projects
Projects
Skip link to Projects
Expand image
Projects
Projects
represents projects and task management entities to assist sales processes from an after-sales activities perspective. Each project has an owner and must be placed in a phase. Projects can be attached to an organization, person or deal. Projects can also be connected with Tasks and ProjectTemplates.
Products Skip link to Products
Products
Skip link to Products
1401
Products ERD
Products
Products
are goods and/or services that your company deals with. Products can have their own custom fields (ProductFields) and be attached to deals. Persons (contacts) can be added as participants and users can be added as followers for a product. Files can also be added to products.
Users Skip link to Users
Users
Skip link to Users
1598
Users ERD
A Company within pipedrive comprises Users who may be grouped into teams. The ERD above depicts how different core and adjacent entities can relate to a company as a whole or users/teams specifically.
Goals may be related to a company, a team and/or a user. Users and teams can have their own specific PermissionSets and Roles, which are a part of the visibility groups’ feature. Users can also have their own UserSettings and UserConnections.
2 main types of webhooks can be created:
webhooks related to a company
webhooks related to a company
and
webhooks for apps
webhooks for apps
. When querying webhooks, a user can obtain the webhooks they’ve created, while apps can only see and delete webhooks that have the type set as...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46663
|
|
46664
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46664
|
|
46665
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
About the Pipedrive API
About the Pipedrive API
📘
An
application programming interface
(API) is a set of functionalities that a service owner provides so people can use its features and/or build software applications. An API details how a user makes requests and the responses they receive in return.
Pipedrive is a sales CRM with an intuitive
RESTful API
RESTful API
, webhooks, app extensions and API clients to help you build
an app
an app
for the
Pipedrive Marketplace
Pipedrive Marketplace
.
Pipedrive RESTful API Skip link to Pipedrive RESTful API
Pipedrive RESTful API
Skip link to Pipedrive RESTful API
Our Pipedrive
RESTful API Reference
can be accessed via
https://developers.pipedrive.com/docs/api/v1/
https://developers.pipedrive.com/docs/api/v1/
, where you will find a list of endpoints and their descriptions.
Calls to our API are validated against an API token or an
access_token
when using
OAuth 2.0
OAuth 2.0
. Our API supports UTF-8 for character encoding. Learn how to find and use the
api_token
here
here
.
3687
Pipedrive Entity Relationship Diagram (ERD)
Webhooks Skip link to Webhooks
Webhooks
Skip link to Webhooks
...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46665
|
|
46670
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Pipedrive
Docs & guides
Explore
Tools
Marketplace
Marketplace
go to pipedrive.com
go to pipedrive.com
Search Developers' corner
Log in
Log in
Sign up
Sign up
Developers' Corner
Developers' Corner
Easily build integrations with our API and developer platform to reach over 100,000 companies through the Pipedrive Marketplace
Build apps & integrations
Build apps & integrations
Create a test environment
Create a test environment
Sign up for a
Sandbox Account
today to begin experimenting and developing in a risk free environment
E-mail
E-mail
First Name
First Name
Sign up for a Sandbox account
Sign up for a Sandbox account
By signing up, you accept our Terms of Service , Developer Agreement and Privacy Notice
By signing up, you accept our
Terms of Service
Terms of Service
,
Developer Agreement
Developer Agreement
and
Privacy Notice
Privacy Notice
Would you like to subscribe to our Changelog updates?
Would you like to subscribe to our Changelog updates?
Play Video
We love working with Pipedrive! The documentation is great, their communication is proactive and the Pipedrive Marketplace exposes us to an SMB audience who is actively looking for solutions.
Andrus Purde,
Co-founder/CEO of Outfunnel
Pipedrive is an amazing tool! Their developer API, well-documented API reference page and easy use of webhooks allow developers to easily build solutions in the Pipedrive Developer Platform.
Kelly Bernardino,
Software Engineer at Gamifier
Developing our Pipedrive integration was a breeze! Their documentation, along with the support we received, is excellent. Pipedrive is one of our best integrations, and we've made many.
Ales Kocjancic,
VP of Engineering at Plecto
Pipedrive API clients
Pipedrive API clients
Kick-start your development by using one of the many API clients available on GitHub.
Here are some of the most popular repositories.
OFFICIAL client-nodejs Javascript 232 Forks 88
OFFICIAL
client-nodejs
client-nodejs
Javascript
232
88
OFFICIAL client-php PHP 60 Forks 65
OFFICIAL
client-php
client-php
PHP...
|
Firefox
|
Pipedrive Developers Corner | Pipedrive API sandbo Pipedrive Developers Corner | Pipedrive API sandbox — Work...
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46670
|
|
46671
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Pipedrive
Docs & guides
Explore
Tools
Marketplace
Marketplace
go to pipedrive.com
go to pipedrive.com
Search Developers' corner
Log in
Log in
Sign up
Sign up
Developers' Corner
Developers' Corner
Easily build integrations with our API and developer platform to reach over 100,000 companies through the Pipedrive Marketplace
Build apps & integrations
Build apps & integrations
Create a test environment
Create a test environment
Sign up for a
Sandbox Account
today to begin experimenting and developing in a risk free environment
E-mail
E-mail
First Name
First Name
Sign up for a Sandbox account
Sign up for a Sandbox account
By signing up, you accept our Terms of Service , Developer Agreement and Privacy Notice
By signing up, you accept our
Terms of Service
Terms of Service
,
Developer Agreement
Developer Agreement
and
Privacy Notice
Privacy Notice
Would you like to subscribe to our Changelog updates?
Would you like to subscribe to our Changelog updates?
Play Video
We love working with Pipedrive! The documentation is great, their communication is proactive and the Pipedrive Marketplace exposes us to an SMB audience who is actively looking for solutions.
Andrus Purde,
Co-founder/CEO of Outfunnel
Pipedrive is an amazing tool! Their developer API, well-documented API reference page and easy use of webhooks allow developers to easily build solutions in the Pipedrive Developer Platform.
Kelly Bernardino,
Software Engineer at Gamifier
Developing our Pipedrive integration was a breeze! Their documentation, along with the support we received, is excellent. Pipedrive is one of our best integrations, and we've made many.
Ales Kocjancic,
VP of Engineering at Plecto
Pipedrive API clients
Pipedrive API clients
Kick-start your development by using one of the many API clients available on GitHub.
Here are some of the most popular repositories.
OFFICIAL client-nodejs Javascript 232 Forks 88
OFFICIAL
client-nodejs
client-nodejs
Javascript
232
88
OFFICIAL client-php PHP 60 Forks 65...
|
Firefox
|
Pipedrive Developers Corner | Pipedrive API sandbo Pipedrive Developers Corner | Pipedrive API sandbox — Work...
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46671
|
|
46672
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
About the Pipedrive API
About the Pipedrive API
📘
An
application programming interface
(API) is a set of functionalities that a service owner provides so people can use its features and/or build software applications. An API details how a user makes requests and the responses they receive in return.
Pipedrive is a sales CRM with an intuitive
RESTful API
RESTful API
, webhooks, app extensions and API clients to help you build
an app
an app
for the
Pipedrive Marketplace
Pipedrive Marketplace
.
Pipedrive RESTful API Skip link to Pipedrive RESTful API
Pipedrive RESTful API
Skip link to Pipedrive RESTful API
Our Pipedrive
RESTful API Reference
can be accessed via
https://developers.pipedrive.com/docs/api/v1/
https://developers.pipedrive.com/docs/api/v1/
, where you will find a list of endpoints and their descriptions.
Calls to our API are validated against an API token or an
access_token
when using
OAuth 2.0
OAuth 2.0
. Our API supports UTF-8 for character encoding. Learn how to find and use the
api_token
here
here
.
3687
Pipedrive Entity Relationship Diagram (ERD)
Webhooks Skip link to Webhooks
Webhooks
Skip link to Webhooks
Webhooks enable you to obtain real-time, programmatic notifications from Pipedrive regarding changes to your data as they happen. Instead of pulling information via our API, webhooks will push information to your endpoint.
You can create webhooks via the web app and our API. You can create a webhook programmatically by making a
POST
request to the webhook’s endpoint. Pipedrive will then send a notification when an event is triggered (e.g., a new lead is added) as an HTTP post with a JSON body to the endpoint(s) you have specified. Find out more about webhooks
here
here
.
App extensions Skip link to App extensions
App extensions
Skip link to App extensions
App extensions enable apps built for the Pipedrive Marketplace to give additional value to their users. With app extensions, the app’s functionality will be available directly inside the Pipedrive platform’s UI and users will be able to interact with and see the custom functionality of your app.
This also helps to increase your app's visibility and brand awareness, as the app icon will be displayed inside Pipedrive after a user has installed it. Find out more about app extensions
here
here
.
API clients Skip link to API clients
API clients
Skip link to API clients
Pipedrive API clients are available on
GitHub
GitHub
. Some of the most popular repositories include:
Client-nodejs
Client-nodejs
(official)
Client-php
Client-php
(official)
Pipedrive
Pipedrive
(community built)
Python-pipedrive
Python-pipedrive
(community built)
Pipedrive-dotnet
Pipedrive-dotnet
(community built)
Pipedrive.rb
Pipedrive.rb
(community built)
How Pipedrive API works Skip link to How Pipedrive API works
How Pipedrive API works
Skip link to How Pipedrive API works
📘
Do take note that entity/entities may be called “item/items” or “type of item/items” for the end user in the Pipedrive web and mobile app.
At the base of your Pipedrive account is a customer relationship management (CRM) database of your sales pipeline, processes and relationships. As organizing sales data is essential for sales activities, Pipedrive helps to
organize and link your data together
organize and link your data together
for better visibility through the core and adjacent entities.
Core entities Skip link to Core entities
Core entities
Skip link to Core entities
Within the Pipedrive API, we have core entities that consist of multiple endpoints. These core entities represent a larger area inside Pipedrive and can be found in the left-hand side menu in the Pipedrive web app. Tied to them are adjacent entities that contain supplementary information relevant to the core entities.
2041
Pipedrive core entities ERD
The ERD above shows how core entities are connected within Pipedrive.
As leads can be converted to deals, they are sometimes used in place of each other. For example, in the case of activities, an activity can be associated with either a lead or a deal. This goes the same for products.
Persons and organizations are considered contacts and are often grouped together.
Mailbox, found in the Mail tab of the Pipedrive web app, is the email control hub inside Pipedrive that stores all the emails a user decides to keep a record of. Mail is tracked and associated with persons and deals through Pipedrive’s email sync and Smart Bcc features.
[Entity] Fields endpoints allow you to obtain the near-complete schema of the respective core entities. You can add, update and delete main and custom fields through these adjacent entities.
Read on to discover how leads, deals, persons and organizations (contacts), activities, products and users are further connected to other core and adjacent entities.
Leads Skip link to Leads
Leads
Skip link to Leads
1847
Leads ERD
Leads
Leads
are prequalified, potential deals that are kept in a separate inbox called the Leads Inbox. Leads can subsequently be converted to deals via the Pipedrive web app and added to a pipeline.
Leads can have activities, emails (mailbox) and notes attached to them. They can also have multiple LeadLabels to categorize them and be linked with one LeadSource to indicate where the lead came from.
Key aspects of leads:
Leads must always have one person (contacts) or organization (contacts) linked with them
Leads can only have one source (LeadSource). Leads created through the API have a set source “API”.
Leads can only have the same
custom fields
custom fields
(DealFields) as deals
Leads can only be converted to deals via the Pipedrive web app\
Deals Skip link to Deals
Deals
Skip link to Deals
2443
Deals ERD
Deals
Deals
are ongoing transactions pursued with a person or an organization. It’s tracked and processed through the Stages of a pipeline until it’s won or lost. Deals can be converted from leads via the Pipedrive web app.
In Pipedrive, deals contain all actions taken towards closing a sale, for example, activities, emails (mailbox), notes and files, and have their own custom fields (DealFields). Products and subscriptions can also be attached to deals.
A deal can be linked with either a person or organization (contacts) but it must always have one contact linked with them. As a deal is associated with a contact, it will pull all information from the linked contact and, likewise, associate all actions performed on the deal with the linked contact.
Persons & organizations (contacts) Skip link to Persons & organizations (contacts)
Persons & organizations (contacts)
Skip link to Persons & organizations (contacts)
2073
Persons & organizations (contacts) ERD
Persons (or people) are the specific customers of the sales process, while
organizations
organizations
are the companies that the persons work at. Persons and organizations are considered contacts and they rest in one centralized hub in the Pipedrive web app. The ERD above depicts how different core and adjacent entities can either relate to contacts as a whole or persons/organizations specifically.
Both persons and organizations can have activities, notes and files attached to them and their respective main fields and custom fields (PersonFields and OrganizationFields). Emails (Mailbox) and products can only be linked to persons while OrganizationRelationships can only be linked to organizations.
Key aspects of Persons and organizations (contacts):
A person can only be linked to one organization
A lead or a deal must always have a person or an organization linked to it
Both persons and organizations can have multiple deals open for them at the same time
Activities Skip link to Activities
Activities
Skip link to Activities
2043
Activities ERD
Activities
Activities
are any actions a user does towards the closing of a sale. There are different types of activities (ActivityTypes) that can be performed, e.g. a phone call (CallLogs), a meeting or a task. You can have custom activity types and custom fields (ActivityFields) for activities. Users can schedule activities in relation to a person, an organization or a lead/deal.
Key aspects of activities:
Associating an activity with a deal will also associate the activity with the person and/or organization linked to the deal
Currently, Files
can only be added
can only be added
to activities via the API
CallLogs Skip link to CallLogs
CallLogs
Skip link to CallLogs
CallLogs for
calls made via the Pipedrive mobile app
calls made via the Pipedrive mobile app
are also considered activities, which means they can be associated with a deal, a person and/or an organization. Do note that CallLogs differ from other activities as they only receive the information needed to describe the phone call.
Projects Skip link to Projects
Projects
Skip link to Projects
Expand image
Projects
Projects
represents projects and task management entities to assist sales processes from an after-sales activities perspective. Each project has an owner and must be placed in a phase. Projects can be attached to an organization, person or deal. Projects can also be connected with Tasks and ProjectTemplates.
Products Skip link to Products
Products
Skip link to Products
1401
Products ERD
Products
Products
are goods and/or services that your company deals with. Products can have their own custom fields (ProductFields) and be attached to deals. Persons (contacts) can be added as participants and users can be added as followers for a product. Files can also be added to products.
Users Skip link to Users
Users
Skip link to Users
1598
Users ERD
A Company within pipedrive comprises Users who may be grouped into teams. The ERD above depicts how different core and adjacent entities can relate to a company as a whole or users/teams specifically.
Goals may be related to a company, a team and/or a user. Users and teams can have their own specific PermissionSets and Roles, which are a part of the visibility groups’ feature. Users can also have their own UserSettings and UserConnections.
2 main types of webhooks can be created:
webhooks related to a company
webhooks related to a company
and
webhooks for apps
webhooks for apps
. When querying webhooks, a user can obtain the webhooks they’ve created, while apps can only see and delete webhooks that have the type set as
type= 'application'
.
Updated
6 months ago
Read next
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
Did this page help you?
Yes, this page helped me
Yes
No, this page did not help me
No
Copy Page
Copy Page
Pipedrive RESTful API
Pipedrive RESTful API
Webhooks
Webhooks
App extensions
App extensions
API clients
API clients
How Pipedrive API works
How Pipedrive API works
Core entities
Core entities
Leads
Leads
Deals
Deals
Persons & organizations (contacts)
Persons & organizations (contacts)
Activities
Activities
Projects
Projects
Products
Products
Users
Users
pipedrive.readme.io/docs/core-[API_KEY]...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46672
|
|
46673
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
About the Pipedrive API
About the Pipedrive API
📘
An
application programming interface
(API) is a set of functionalities that a service owner provides so people can use its features and/or build software applications. An API details how a user makes requests and the responses they receive in return.
Pipedrive is a sales CRM with an intuitive
RESTful API
RESTful API
, webhooks, app extensions and API clients to help you build
an app
an app
for the
Pipedrive Marketplace
Pipedrive Marketplace
.
Pipedrive RESTful API Skip link to Pipedrive RESTful API
Pipedrive RESTful API
Skip link to Pipedrive RESTful API
Our Pipedrive
RESTful API Reference
can be accessed via
https://developers.pipedrive.com/docs/api/v1/
https://developers.pipedrive.com/docs/api/v1/
, where you will find a list of endpoints and their descriptions.
Calls to our API are validated against an API token or an
access_token
when using
OAuth 2.0
OAuth 2.0
. Our API supports UTF-8 for character encoding. Learn how to find and use the
api_token
here
here
.
3687
Pipedrive Entity Relationship Diagram (ERD)
Webhooks Skip link to Webhooks
Webhooks
Skip link to Webhooks
Webhooks enable you to obtain real-time, programmatic notifications from Pipedrive regarding changes to your data as they happen. Instead of pulling information via our API, webhooks will push information to your endpoint.
You can create webhooks via the web app and our API. You can create a webhook programmatically by making a
POST
request to the webhook’s endpoint. Pipedrive will then send a notification when an event is triggered (e.g., a new lead is added) as an HTTP post with a JSON body to the endpoint(s) you have specified. Find out more about webhooks
here
here
.
App extensions Skip link to App extensions
App extensions
Skip link to App extensions
App extensions enable apps built for the Pipedrive Marketplace to give additional value to their users. With app extensions, the app’s functionality will be available directly inside the Pipedrive platform’s UI and users will be able to interact with and see the custom functionality of your app.
This also helps to increase your app's visibility and brand awareness, as the app icon will be displayed inside Pipedrive after a user has installed it. Find out more about app extensions
here
here
.
API clients Skip link to API clients
API clients
Skip link to API clients
Pipedrive API clients are available on
GitHub
GitHub
. Some of the most popular repositories include:
Client-nodejs
Client-nodejs
(official)
Client-php
Client-php
(official)
Pipedrive
Pipedrive
(community built)
Python-pipedrive
Python-pipedrive
(community built)
Pipedrive-dotnet
Pipedrive-dotnet
(community built)
Pipedrive.rb
Pipedrive.rb
(community built)
How Pipedrive API works Skip link to How Pipedrive API works
How Pipedrive API works
Skip link to How Pipedrive API works
📘
Do take note that entity/entities may be called “item/items” or “type of item/items” for the end user in the Pipedrive web and mobile app.
At the base of your Pipedrive account is a customer relationship management (CRM) database of your sales pipeline, processes and relationships. As organizing sales data is essential for sales activities, Pipedrive helps to
organize and link your data together
organize and link your data together
for better visibility through the core and adjacent entities.
Core entities Skip link to Core entities
Core entities
Skip link to Core entities
Within the Pipedrive API, we have core entities that consist of multiple endpoints. These core entities represent a larger area inside Pipedrive and can be found in the left-hand side menu in the Pipedrive web app. Tied to them are adjacent entities that contain supplementary information relevant to the core entities.
2041
Pipedrive core entities ERD
The ERD above shows how core entities are connected within Pipedrive.
As leads can be converted to deals, they are sometimes used in place of each other. For example, in the case of activities, an activity can be associated with either a lead or a deal. This goes the same for products.
Persons and organizations are considered contacts and are often grouped together.
Mailbox, found in the Mail tab of the Pipedrive web app, is the email control hub inside Pipedrive that stores all the emails a user decides to keep a record of. Mail is tracked and associated with persons and deals through Pipedrive’s email sync and Smart Bcc features.
[Entity] Fields endpoints allow you to obtain the near-complete schema of the respective core entities. You can add, update and delete main and custom fields through these adjacent entities.
Read on to discover how leads, deals, persons and organizations (contacts), activities, products and users are further connected to other core and adjacent entities.
Leads Skip link to Leads
Leads
Skip link to Leads...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46673
|
|
46674
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels
LeadBooster Browser API
LeadBooster Browser API
FAQ
FAQ
TOOLS
TOOLS
Node.js API client Opens in new tab
Node.js API client
PHP API client Opens in new tab
PHP API client
Hide sidebar navigation
About the Pipedrive API
About the Pipedrive API
📘
An
application programming interface
(API) is a set of functionalities that a service owner provides so people can use its features and/or build software applications. An API details how a user makes requests and the responses they receive in return.
Pipedrive is a sales CRM with an intuitive
RESTful API
RESTful API
, webhooks, app extensions and API clients to help you build
an app
an app
for the
Pipedrive Marketplace
Pipedrive Marketplace
.
Pipedrive RESTful API Skip link to Pipedrive RESTful API
Pipedrive RESTful API
Skip link to Pipedrive RESTful API
Our Pipedrive
RESTful API Reference
can be accessed via
https://developers.pipedrive.com/docs/api/v1/
https://developers.pipedrive.com/docs/api/v1/
, where you will find a list of endpoints and their descriptions.
Calls to our API are validated against an API token or an
access_token
when using
OAuth 2.0
OAuth 2.0
. Our API supports UTF-8 for character encoding. Learn how to find and use the
api_token
here
here
.
3687
Pipedrive Entity Relationship Diagram (ERD)
Webhooks Skip link to Webhooks
Webhooks
Skip link to Webhooks
Webhooks enable you to obtain real-time, programmatic notifications from Pipedrive regarding changes to your data as they happen. Instead of pulling information via our API, webhooks will push information to your endpoint.
You can create webhooks via the web app and our API. You can create a webhook programmatically by making a
POST
request to the webhook’s endpoint. Pipedrive will then send a notification when an event is triggered (e.g., a new lead is added) as an HTTP post with a JSON body to the endpoint(s) you have specified. Find out more about webhooks
here
here
.
App extensions Skip link to App extensions
App extensions
Skip link to App extensions
App extensions enable apps built for the Pipedrive Marketplace to give additional value to their users. With app extensions, the app’s functionality will be available directly inside the Pipedrive platform’s UI and users will be able to interact with and see the custom functionality of your app.
This also helps to increase your app's visibility and brand awareness, as the app icon will be displayed inside Pipedrive after a user has installed it. Find out more about app extensions
here
here
.
API clients Skip link to API clients
API clients
Skip link to API clients
Pipedrive API clients are available on
GitHub
GitHub
. Some of the most popular repositories include:
Client-nodejs
Client-nodejs
(official)
Client-php
Client-php
(official)
Pipedrive
Pipedrive
(community built)
Python-pipedrive
Python-pipedrive
(community built)
Pipedrive-dotnet
Pipedrive-dotnet
(community built)
Pipedrive.rb
Pipedrive.rb
(community built)
How Pipedrive API works Skip link to How Pipedrive API works
How Pipedrive API works
Skip link to How Pipedrive API works
📘
Do take note that entity/entities may be called “item/items” or “type of item/items” for the end user in the Pipedrive web and mobile app.
At the base of your Pipedrive account is a customer relationship management (CRM) database of your sales pipeline, processes and relationships. As organizing sales data is essential for sales activities, Pipedrive helps to
organize and link your data together
organize and link your data together
for better visibility through the core and adjacent entities.
Core entities Skip link to Core entities
Core entities
Skip link to Core entities
Within the Pipedrive API, we have core entities that consist of multiple endpoints. These core entities represent a larger area inside Pipedrive and can be found in the left-hand side menu in the Pipedrive web app. Tied to them are adjacent entities that contain supplementary information relevant to the core entities.
2041
Pipedrive core entities ERD
The ERD above shows how core entities are connected within Pipedrive.
As leads can be converted to deals, they are sometimes used in place of each other. For example, in the case of activities, an activity can be associated with either a lead or a deal. This goes the same for products.
Persons and organizations are considered contacts and are often grouped together.
Mailbox, found in the Mail tab of the Pipedrive web app, is the email control hub inside Pipedrive that stores all the emails a user decides to keep a record of. Mail is tracked and associated with persons and deals through Pipedrive’s email sync and Smart Bcc features.
[Entity] Fields endpoints allow you to obtain the near-complete schema of the respective core entities. You can add, update and delete main and custom fields through these adjacent entities.
Read on to discover how leads, deals, persons and organizations (contacts), activities, products and users are further connected to other core and adjacent entities.
Leads Skip link to Leads
Leads
Skip link to Leads
1847
Leads ERD
Leads
Leads
are prequalified, potential deals that are kept in a separate inbox called the Leads Inbox. Leads can subsequently be converted to deals via the Pipedrive web app and added to a pipeline.
Leads can have activities, emails (mailbox) and notes attached to them. They can also have multiple LeadLabels to categorize them and be linked with one LeadSource to indicate where the lead came from.
Key aspects of leads:
Leads must always have one person (contacts) or organization (contacts) linked with them
Leads can only have one source (LeadSource). Leads created through the API have a set source “API”.
Leads can only have the same
custom fields
custom fields
(DealFields) as deals
Leads can only be converted to deals via the Pipedrive web app\
Deals Skip link to Deals
Deals
Skip link to Deals
2443
Deals ERD
Deals
Deals
are ongoing transactions pursued with a person or an organization. It’s tracked and processed through the Stages of a pipeline until it’s won or lost. Deals can be converted from leads via the Pipedrive web app.
In Pipedrive, deals contain all actions taken towards closing a sale, for example, activities, emails (mailbox), notes and files, and have their own custom fields (DealFields). Products and subscriptions can also be attached to deals.
A deal can be linked with either a person or organization (contacts) but it must always have one contact linked with them. As a deal is associated with a contact, it will pull all information from the linked contact and, likewise, associate all actions performed on the deal with the linked contact.
Persons & organizations (contacts) Skip link to Persons & organizations (contacts)
Persons & organizations (contacts)
Skip link to Persons & organizations (contacts)
2073
Persons & organizations (contacts) ERD
Persons (or people) are the specific customers of the sales process, while
organizations
organizations
are the companies that the persons work at. Persons and organizations are considered contacts and they rest in one centralized hub in the Pipedrive web app. The ERD above depicts how different core and adjacent entities can either relate to contacts as a whole or persons/organizations specifically.
Both persons and organizations can have activities, notes and files attached to them and their respective main fields and custom fields (PersonFields and OrganizationFields). Emails (Mailbox) and products can only be linked to persons while OrganizationRelationships can only be linked to organizations.
Key aspects of Persons and organizations (contacts):
A person can only be linked to one organization
A lead or a deal must always have a person or an organization linked to it
Both persons and organizations can have multiple deals open for them at the same time
Activities Skip link to Activities
Activities
Skip link to Activities
2043
Activities ERD
Activities
Activities
are any actions a user does towards the closing of a sale. There are different types of activities (ActivityTypes) that can be performed, e.g. a phone call (CallLogs), a meeting or a task. You can have custom activity types and custom fields (ActivityFields) for activities. Users can schedule activities in relation to a person, an organization or a lead/deal.
Key aspects of activities:
Associating an activity with a deal will also associate the activity with the person and/or organization linked to the deal
Currently, Files
can only be added
can only be added
to activities via the API
CallLogs Skip link to CallLogs
CallLogs
Skip link to CallLogs
CallLogs for
calls made via the Pipedrive mobile app
calls made via the Pipedrive mobile app
are also considered activities, which means they can be associated with a deal, a person and/or an organization. Do note that CallLogs differ from other activities as they only receive the information needed to describe the phone call.
Projects Skip link to Projects
Projects
Skip link to Projects
Expand image
Projects
Projects
represents projects and task management entities to assist sales processes from an after-sales activities perspective. Each project has an owner and must be placed in a phase. Projects can be attached to an organization, person or deal. Projects can also be connected with Tasks and ProjectTemplates.
Products Skip link to Products
Products
Skip link to Products
1401
Products ERD
Products
Products
are goods and/or services that your company deals with. Products can have their own custom fields (ProductFields) and be attached to deals. Persons (contacts) can be added as participants and users can be added as followers for a product. Files can also be added to products.
Users Skip link to Users
Users
Skip link to Users
1598
Users ERD
A Company within pipedrive comprises Users who may be grouped into teams. The ERD above depicts how different core and adjacent entities can relate to a company as a whole or users/teams specifically.
Goals may be related to a company, a team and/or a user. Users and teams can have their own specific PermissionSets and Roles, which are a part of the visibility groups’ feature. Users can also have their own UserSettings and UserConnections.
2 main types of webhooks can be created:
webhooks related to a company
webhooks related to a company
and
webhooks for apps
webhooks for apps
. When querying webhooks, a user can obtain the webhooks they’ve created, while apps can only see and delete webhooks that have the type set as
type= 'application'
.
...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46674
|
|
46675
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46675
|
|
46676
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide
Subscriptions API migration guide
Tutorials Show subpages for Tutorials
Tutorials
Show subpages for Tutorials
How to find the API token
How to find the API token
How to get the company domain
How to get the company domain
Enabling API for company users
Enabling API for company users
Hello World Tutorial Opens in new tab
Hello World Tutorial
Adding an Activity Opens in new tab
Adding an Activity
Adding a new custom field Opens in new tab
Adding a new custom field
Updating custom fields' values Opens in new tab
Updating custom fields' values
Deleting a custom field Opens in new tab
Deleting a custom field
Creating a Deal Opens in new tab
Creating a Deal
Getting all Deals Opens in new tab
Getting all Deals
Getting details of a Deal Opens in new tab
Getting details of a Deal
Updating a Deal Opens in new tab
Updating a Deal
Assigning a Deal to a certain User Opens in new tab
Assigning a Deal to a certain User
Merging two Deals Opens in new tab
Merging two Deals
Using Pagination to retrieve all Deal titles Opens in new tab
Using Pagination to retrieve all Deal titles
Adding a File Opens in new tab
Adding a File
Adding a remote file Opens in new tab
Adding a remote file
Adding a Filter Opens in new tab
Adding a Filter
Adding a Lead Opens in new tab
Adding a Lead
Adding an Organization Opens in new tab
Adding an Organization
Merging two Organizations Opens in new tab
Merging two Organizations
Merging two Persons Opens in new tab
Merging two Persons
Updating a Person Opens in new tab
Updating a Person
Adding a Product Opens in new tab
Adding a Product
Working with labels
Working with labels...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46676
|
|
46677
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46677
|
|
46678
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Pipelines - jiminny/app
Pipelines - jiminny/app
Feed — jiminny — Sentry
Feed — jiminny — Sentry
[JY-20906] Review of Pipedrive SDK - Jira
[JY-20906] Review of Pipedrive SDK - Jira
About the Pipedrive API
About the Pipedrive API
Close tab
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
https://pipedrive.readme.io/docs/api-versions - Google Search
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Jump to Content
Jump to Content
Pipedrive Developer Documentation
API Reference
API Reference
Tutorials
Tutorials
Changelog
Changelog
Dev Community
Dev Community
Blog
Blog
Pipedrive Developer Documentation
Pipedrive Developer Documentation
Search ⌘k
Search
OVERVIEW
OVERVIEW
Getting started
Getting started
Developer sandbox account
Developer sandbox account
Pipedrive API in Postman or Insomnia
Pipedrive API in Postman or Insomnia
Creating an app
Creating an app
Tutorials: how to build an app 🚀 Opens in new tab
Tutorials: how to build an app 🚀
Pipedrive API v2 overview
Pipedrive API v2 overview
Pipedrive API v2 migration guide
Pipedrive API v2 migration guide
CORE API CONCEPTS
CORE API CONCEPTS
About the Pipedrive API
About the Pipedrive API
Changes to the API
Changes to the API
Requests
Requests
Rate limiting
Rate limiting
Responses
Responses
Date format
Date format
Pagination
Pagination
HTTP status codes
HTTP status codes
Authentication
Authentication
Custom fields
Custom fields
MARKETPLACE
MARKETPLACE
About the Marketplace
About the Marketplace
App installation flows
App installation flows
Developer Hub Show subpages for Developer Hub
Developer Hub
Show subpages for Developer Hub
Registering a public app
Registering a public app
Registering a private app
Registering a private app
Updating approved apps
Updating approved apps
Deleting an app
Deleting an app
Client ID and client secret
Client ID and client secret
App approval process
App approval process
Tips on getting your app approved! Opens in new tab
Tips on getting your app approved!
Pipedrive Developer Partner Agreement
Pipedrive Developer Partner Agreement
APP EXTENSIONS
APP EXTENSIONS
App extensions overview
App extensions overview
Link actions
Link actions
JSON modals Show subpages for JSON modals
JSON modals
Show subpages for JSON modals
Component library
Component library
User interaction handling
User interaction handling
JSON panels Show subpages for JSON panels
JSON panels
Show subpages for JSON panels
Adding a JSON panel
Adding a JSON panel
Actions in JSON panels
Actions in JSON panels
Custom UI extensions Show subpages for Custom UI extensions
Custom UI extensions
Show subpages for Custom UI extensions
Custom floating window
Custom floating window
Custom panels
Custom panels
Custom modals
Custom modals
Custom UI for app settings
Custom UI for app settings
Video calling app extension
Video calling app extension
Messaging app extension Show subpages for Messaging app extension
Messaging app extension
Show subpages for Messaging app extension
Implementing messaging app extension
Implementing messaging app extension
Error codes and troubleshooting
Error codes and troubleshooting
APP FUNCTIONALITIES
APP FUNCTIONALITIES
App sharing: Adding apps to multiple users
App sharing: Adding apps to multiple users
OAUTH 2.0
OAUTH 2.0
OAuth 2.0 overview
OAuth 2.0 overview
OAuth authorization
OAuth authorization
Scopes and permission explanations
Scopes and permission explanations
State parameter
State parameter
Getting user data
Getting user data
Webhooks for apps
Webhooks for apps
Handling user app uninstallation
Handling user app uninstallation
OAuth status codes
OAuth status codes
Migrating existing integration users
Migrating existing integration users
TUTORIALS AND ARTICLES
TUTORIALS AND ARTICLES
Guide for Webhooks v2 Show subpages for Guide for Webhooks v2
Guide for Webhooks v2
Show subpages for Guide for Webhooks v2
List of Webhooks v2
List of Webhooks v2
Webhooks v2 migration guide
Webhooks v2 migration guide
Guide for Webhooks Show subpages for Guide for Webhooks
Guide for Webhooks
Show subpages for Guide for Webhooks
List of Webhooks
List of Webhooks
Guide for optimizing API usage
Guide for optimizing API usage
Subscriptions API migration guide...
|
Firefox
|
About the Pipedrive API — Work
|
pipedrive.readme.io/docs/core-api-concepts-about-p pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api...
|
46678
|
|
41890
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel....
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41890
|
|
41891
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
SlackFileEditViewGoHistoryActivity MonitorAll ProcessesProcess NameVirtual Machine Service for DockerPhpStormWindowServerFirefoxCP Isolated Web ContentFirefox GPU HelperFirefoxCP Isolated Web ContentFirefoxCP Isolated Web ContentSlack Helper (Renderer)language_server_macos_armcef__server Helper (Renderer)Postman Helper (Renderer)lavaFirefoxNotion Helper (Renderer)Notion Calendar Helper (Renderer)screenpipeFirefoxCP Isolated Web ContentFirefoxCP Isolated Web ContentFirefoxCP Isolated Web ContentClaude Helper (Renderer)cef_server Helper (GPU)PostmanNotion Calendar Helper (GPU)iTerm2RaycastClaude HelperFirefoxCP Isolated Web ContentFinderWindowHelpMem..Threads4,01 GB3,59 GB2,16 GB793,4 MB745,9 MB715,5 MB702,5 MB676,2 MB645,5 MB580,4 MB573,1 MB522,5 MB510,7 MB499,4 MB478,6 MB445,7 MB387,0 MB347,0 MB307,8 MB299,0 MB261,1 MB256,7 MB255,6 MB250,2 MB240,2 MB226,4 MB219,2 MB204,7 MB Ports PID MEMORY PRESSURECPUMemoryUserlukaslukas_windowserverlukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukaslukasEnelPhysical MemonMemory Used:Cached Files:Swap Used:HomeDMsActivity5Later..•More(allJiminny ...# engineering# general# jiminny-bg# platform-tickets# product_launches# random# releases# sofia-office# support# thank-yous# the_people_of jimi...• Direct messagesZ: Todor StamatovVasil Vasilev2. Stefka StoyanovaMario Georgiev&. Nikolay Ivanovdo James Graham *&. Stoyan TanevGalya DimitrovaRo Steliyan Georgiev. Petko KashinskiP. Aneliya AngelovaLukas Kovalik y...##: AppsToastJira CloudSupport Daily - in 57 m100% <78• Thu 14 May 14:03:42Describe what you are looking for* & platform-inner-team& 106 0• MessagesP Channel OverviewMore v+Today ~Steliyan Georgiev 1:40 PMМоже ли 2 ревюта? Вече съм ги прекарал презКлод:https://github.com/jiminny/prophet/pull/508https://github.com/jiminny/prophet/pull/509Благодаря! (edited)V1Nikolay Yankov 1:41 PMТрябва да добавим един нов tool -search_membersзащото резултата за екипите вlist_call_options tool-a става тежьк с всичкителистнати user-ието това ще представлява. Та, да го добавя катоподзадача в сторито за calls ?image.pngMessage & platform-inner-team+...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41891
|
|
41892
|
rireroxcalVIewMistorbookmarksProtllesloolsWindowme rireroxcalVIewMistorbookmarksProtllesloolsWindowmelpPlatform Sprint 4 02 - Platform 1P Changes to the API• JY-18091 | Update composer to:Ghttps://github.com/pipedrive/clie(SRD-6849] Recorded call doesN (SRD-6848) Sidekick SMS issue(JY-208911 Sidekick SMS issueJY-20891 add support for secor(SRD-68491 Recorded call does8 JiminnyT (SRD-68531 Moxso - Potential derly-209021 Recorded call does.nJY-20903 Update activity stageContiaure SSH access to multiole& Useful commands - Engineering -8 Dev Tools - Elastic8 liminnvCal CloudWatch | eu-west-1Ca CloudWatch I eu-west-1A CloudWetch tou-woct.IL Now Toh• Goodle gemini• Capabilities: Primarily focused onAPI v1.• Cons: Higher risk of breakage duringthe v2 transition; may require acomplete rewrite once vi isdeprecated.The "API v2" Transition & DeprecationPipedrive is actively moving away from API v1.Using the official SDK allows us to build using v2namespaces immediately, which offers betterpertormance and more modern rate-limiting.• V1 Deprecation Info: Pipedrive APIVersions & Deprecation Policy.• Key Date: Major vi features are scheduledfor sunsetting by July 2026.Imolementation Plan• Library: pipedrive/client-php•Strategy: * Register thePipedrive\Client as a singleton inAooServiceProvider• Store the API Token / OAuthcredentials in .env and config/services.php.• Prioritize using API v2 endpointswhere available to prevent futuremigration tasks.Enter a prompt for GeminiAl lt can make mistakes so double check it Your orivaev &. GeSummarize pagepipedrive DEVELOPERSM Pipedrive Developer DocumentationOVERVIEWGetting startedDeveloper sandbox accountJlloporVo Abn vestmanor insominiCreatina an appTutorials: how to build an app #Pibedrive AP| V2 overviewPipearive APl vz micration quldtCORE API CONCEPTSAbout the Pioedrive APIChanges to the APIRate limitincResnonsesDate tormatPaginationHilTP status codesAuthenticationCustom fieldsMARKETPI ACEAbout the MarketplaceAoo installation flowsDeveloper HubClient ID and client secretApp approval processTips on getting your appPipedrive Developer PartnerAPI ReferenceTutorialsChangelog<40 ll 1 Support Daily - in 57 m100% C4 &• Thu 14 May 14:03:42Dev CommunityBloaQ SearchChangBy clicking "Accept All", you agree to the storing of cookies on your device to enhance sitenavigation, analyze site usage, personalize content and serve personalizedadvertisements. Cookie Notice Privacy NoticePipedrive'sBy introduciCookies Settina:Reiect AllAccopt AlDo take not•All chanaes to the Pioedrive APl are announced via our Chanaeloa. Make sure to subscribe to stav uo todate!** Occasionalliv. we announce new APl endooints in the Beta version with the aoal of aatherina customerfeedback. Please note that Beta endpoints may be subject to breaking changes.Types of changesChanges to the Pipedrive APl can be divided into breaking and non-breaking changes.A breaking change is a backward incompatible change that may require updating your app.A non-breakina change is tvpically a new addition to the API that can be implemented at vour own pace andchoosind.We aim to announce breaking changes via our Changelog at least 60 days in advance to give youadequate time to adopt the changes.Breaking changesNon-breaking changesRemovina a resourceRemoving an endpointRemoving a parameterRemoving a response fieldModifying an endpoint's URIModifvina the name of a parameter or fieldAdding a new endpointAdding a new optional parameterAdding a new response fieldChanging the order of response fieldsChanging an error messageFixing an HTTP response codeModifvina reauired narametersAddina a reauired narametelstionality.ctionality.on to find& Copy PageTypes of changesApp extensions overview...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41892
|
|
41893
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
You said
ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
Expand
Listen
Gemini said
Gemini said
This is a critical time for Pipedrive integrations.
As of mid-2024, Pipedrive is undergoing a massive shift from
API v1 to API v2
, with a hard deprecation date for many v1 features set for
July 2026
.
View source details for citation from Make Help Center. Opens side panel.
Here is the deep-dive comparison to help you decide.
1. API v1 vs. API v2 Support
1. API v1 vs. API v2 Support
This is the most important factor for a new project in 2024/2025.
pipedrive/client-php
(Official):
Fully supports
both v1 and v2
. It recently introduced version-specific namespaces (
Pipedrive\versions\v1
and
Pipedrive\versions\v2
).
It is built to help you migrate.
Since v2 is the future (offering better performance and lower "token costs" against rate limits), this SDK is future-proof.
View source details for citation from GitHub. Opens side panel.
IsraelOrtuno/pipedrive
(Community):
This package is primarily a wrapper for
API v1
. While it is elegant, it lacks native, structured support for the new v2 endpoints. Using this today means you are building on a foundation that Pipedrive is actively trying to phase out.
2. Maintenance & Activity
2. Maintenance & Activity
Feature
pipedrive/client-php
(Official)
IsraelOrtuno/pipedrive
(Community)
Last Updated
Days/Weeks ago.
Highly active.
Months/Years ago.
Much slower pace.
Open Issues
Managed by a dedicated team at Pipedrive.
Managed by a single developer/community.
Response Time
High. Critical bugs are patched quickly.
Low. Many community packages lose steam over time.
PHP 8.x Support
Native and tested.
Generally works, but lacks modern PHP optimizations.
Feature
Last Updated
Open Issues
Response Time
PHP 8.x Support
pipedrive/client-php
(Official)
Days/Weeks ago.
Highly active.
Managed by a dedicated team at Pipedrive.
High. Critical bugs are patched quickly.
Native and tested.
IsraelOrtuno/pipedrive
(Community)
Months/Years ago.
Much slower pace.
Managed by a single developer/community.
Low. Many community packages lose steam over time.
Generally works, but lacks modern PHP optimizations.
Copy table
3. "The Laravel Way" vs. Stability
3. "The Laravel Way" vs. Stability
IsraelOrtuno's package
feels great in Laravel because of the
Facade
support and the fluent syntax:
Pipedrive::people()->findByName('John')
.
The Official SDK
is a bit "clunkier" because it's a generic PHP library. However, you can make it feel like a Laravel package in 5 minutes by creating a Service Provider.
Pro-tip:
Don't choose a package just because it has a Facade. It is much easier to write a 10-line wrapper for an official SDK than it is to fix a broken, abandoned community package when your CRM integration stops working.
4. What else should you think about?
4. What else should you think about?
A. The v2 Migration (The "July 2026" Problem)
A. The v2 Migration (The "July 2026" Problem)
Pipedrive has announced that v1 is being deprecated.
If you use the community package now, you are essentially creating technical debt. You will likely have to rewrite your entire integration in 12–18 months. By using the
Official SDK
, you can start writing your logic using
v2
namespaces immediately.
View source details for citation from Make Help Center. Opens side panel.
B. Rate Limiting (Token-based)
B. Rate Limiting (Token-based)
API v2 uses a "Token-based" rate limiting system which is much more generous than the old v1 limits.
The Official SDK handles these headers and limits much more gracefully.
View source details for citation from Pipedrive Developers. Opens side panel.
C. OAuth 2.0 vs API Token
C. OAuth 2.0 vs API Token
Official SDK:
Built with robust OAuth 2.0 support (the only way to get your app onto the Pipedrive Marketplace).
View source details for citation from GitHub. Opens side panel.
Community Wrapper:
Often relies on a simple API Token, which Pipedrive is discouraging for security reasons in favor of OAuth.
Final Recommendation
Final Recommendation
Use the Official
pipedrive/client-php
pipedrive/client-php
.
Why?
Direct v2 Access:
You won't have to rewrite your code when v1 is turned off.
Reliability:
It is maintained by the people who write the API.
Laravel Integration is easy:
You can simply bind it in your
AppServiceProvider
and use Dependency Injection:
PHP
Download code
Copy code
// app/Providers/AppServiceProvider.php
public
function
register
(
)
{
$this
->app->singleton(\Pipedrive\Client::class,
function
(
)
{
$client
=
new
\Pipedrive\Client(config(
'services.pipedrive.token'
));
// You can specify the version here or via namespaces
return
$client
;
});
}
// In your Controller/Service
public
function
store
(
Pipedrive\Client
$pipedrive
)
{
// Access v2 specifically
$pipedrive
->getV2()->getDeals()->getDetails(
123
);
}
Avoid the community package
for new, professional projects. It was great for its time, but it is not prepared for the API v2 era.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said ok give me descriptioin for the the jira ticket. Inlcude lionks for both versions and also link for info about v1 deprecation
You said
ok give me descriptioin for the the jira ticket. Inlcude lionks for both versions and also link for info about v1 deprecation
Listen
Gemini said
Gemini said
Below is a structured description for your Jira ticket. It is designed to give your team a clear technical overview of why the choice matters for long-term maintenance.
Ticket: Integrate Pipedrive CRM into Laravel Application
Ticket: Integrate Pipedrive CRM into Laravel Application
Description
Description
We need to implement a connection between our Laravel application and Pipedrive CRM. After evaluating the available PHP libraries, we are moving forward with the
Official Pipedrive PHP Client
to ensure compatibility with the upcoming API v2 transition and to avoid technical debt associated with community-maintained wrappers.
Candidate Evaluation
Candidate Evaluation
Official SDK:
pipedrive/client-php
pipedrive/client-php
Status:
High maintenance, auto-generated from OpenAPI specs.
Capabilities:
Full support for both
API v1
and
API v2
.
Pros:...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41893
|
|
41894
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
You said
ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
Expand
Listen
Gemini said
Gemini said
This is a critical time for Pipedrive integrations.
As of mid-2024, Pipedrive is undergoing a massive shift from
API v1 to API v2
, with a hard deprecation date for many v1 features set for
July 2026
.
View source details for citation from Make Help Center. Opens side panel.
Here is the deep-dive comparison to help you decide.
1. API v1 vs. API v2 Support
1. API v1 vs. API v2 Support
This is the most important factor for a new project in 2024/2025.
pipedrive/client-php
(Official):
Fully supports
both v1 and v2
. It recently introduced version-specific namespaces (
Pipedrive\versions\v1
and
Pipedrive\versions\v2
).
It is built to help you migrate.
Since v2 is the future (offering better performance and lower "token costs" against rate limits), this SDK is future-proof.
View source details for citation from GitHub. Opens side panel.
IsraelOrtuno/pipedrive
(Community):
This package is primarily a wrapper for
API v1
. While it is elegant, it lacks native, structured support for the new v2 endpoints. Using this today means you are building on a foundation that Pipedrive is actively trying to phase out.
2. Maintenance & Activity
2. Maintenance & Activity
Feature
pipedrive/client-php
(Official)
IsraelOrtuno/pipedrive
(Community)
Last Updated
Days/Weeks ago.
Highly active.
Months/Years ago.
Much slower pace.
Open Issues
Managed by a dedicated team at Pipedrive.
Managed by a single developer/community....
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41894
|
|
41895
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
You said
ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
Expand
Listen
Gemini said
Gemini said
This is a critical time for Pipedrive integrations.
As of mid-2024, Pipedrive is undergoing a massive shift from
API v1 to API v2
, with a hard deprecation date for many v1 features set for
July 2026
.
View source details for citation from Make Help Center. Opens side panel.
Here is the deep-dive comparison to help you decide.
1. API v1 vs. API v2 Support
1. API v1 vs. API v2 Support
This is the most important factor for a new project in 2024/2025.
pipedrive/client-php
(Official):
Fully supports
both v1 and v2
. It recently introduced version-specific namespaces (
Pipedrive\versions\v1
and
Pipedrive\versions\v2
).
It is built to help you migrate.
Since v2 is the future (offering better performance and lower "token costs" against rate limits), this SDK is future-proof.
View source details for citation from GitHub. Opens side panel.
IsraelOrtuno/pipedrive
(Community):
This package is primarily a wrapper for
API v1
. While it is elegant, it lacks native, structured support for the new v2 endpoints. Using this today means you are building on a foundation that Pipedrive is actively trying to phase out.
2. Maintenance & Activity
2. Maintenance & Activity
Feature
pipedrive/client-php
(Official)
IsraelOrtuno/pipedrive
(Community)
Last Updated
Days/Weeks ago.
Highly active.
Months/Years ago.
Much slower pace.
Open Issues
Managed by a dedicated team at Pipedrive.
Managed by a single developer/community.
Response Time
High. Critical bugs are patched quickly.
Low. Many community packages lose steam over time.
PHP 8.x Support
Native and tested.
Generally works, but lacks modern PHP optimizations.
Feature
Last Updated
Open Issues
Response Time
PHP 8.x Support
pipedrive/client-php
(Official)
Days/Weeks ago.
Highly active.
Managed by a dedicated team at Pipedrive.
High. Critical bugs are patched quickly.
Native and tested.
IsraelOrtuno/pipedrive
(Community)
Months/Years ago.
Much slower pace.
Managed by a single developer/community.
Low. Many community packages lose steam over time.
Generally works, but lacks modern PHP optimizations.
Copy table
3. "The Laravel Way" vs. Stability
3. "The Laravel Way" vs. Stability
IsraelOrtuno's package
feels great in Laravel because of the
Facade
support and the fluent syntax:
Pipedrive::people()->findByName('John')
.
The Official SDK
is a bit "clunkier" because it's a generic PHP library. However, you can make it feel like a Laravel package in 5 minutes by creating a Service Provider.
Pro-tip:
Don't choose a package just because it has a Facade. It is much easier to write a 10-line wrapper for an official SDK than it is to fix a broken, abandoned community package when your CRM integration stops working.
4. What else should you think about?
4. What else should you think about?
A. The v2 Migration (The "July 2026" Problem)
A. The v2 Migration (The "July 2026" Problem)
Pipedrive has announced that v1 is being deprecated.
If you use the community package now, you are essentially creating technical debt. You will likely have to rewrite your entire integration in 12–18 months. By using the
Official SDK
, you can start writing your logic using
v2
namespaces immediately.
View source details for citation from Make Help Center. Opens side panel.
B. Rate Limiting (Token-based)
B. Rate Limiting (Token-based)
API v2 uses a "Token-based" rate limiting system which is much more generous than the old v1 limits.
The Official SDK handles these headers and limits much more gracefully.
View source details for citation from Pipedrive Developers. Opens side panel.
C. OAuth 2.0 vs API Token
C. OAuth 2.0 vs API Token
Official SDK:
Built with robust OAuth 2.0 support (the only way to get your app onto the Pipedrive Marketplace).
View source details for citation from GitHub. Opens side panel.
Community Wrapper:
Often relies on a simple API Token, which Pipedrive is discouraging for security reasons in favor of OAuth.
Final Recommendation
Final Recommendation
Use the Official
pipedrive/client-php
pipedrive/client-php
.
Why?
Direct v2 Access:
You won't have to rewrite your code when v1 is turned off.
Reliability:
It is maintained by the people who write the API.
Laravel Integration is easy:
You can simply bind it in your
AppServiceProvider
and use Dependency Injection:
PHP
Download code
Copy code
// app/Providers/AppServiceProvider.php
public
function
register
(
)...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41895
|
|
41896
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources
Sources
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
You said
ok compare anythign you can think of, Support or API v1 and v2. WHen was is last time updated. Are there opened issues. Are these addressed. Whart else should i think about
Expand
Listen
Gemini said
Gemini said
This is a critical time for Pipedrive integrations.
As of mid-2024, Pipedrive is undergoing a massive shift from
API v1 to API v2
, with a hard deprecation date for many v1 features set for
July 2026
.
View source details for citation from Make Help Center. Opens side panel.
Here is the deep-dive comparison to help you decide.
1. API v1 vs. API v2 Support
1. API v1 vs. API v2 Support
This is the most important factor for a new project in 2024/2025.
pipedrive/client-php
(Official):
Fully supports
both v1 and v2
. It recently introduced version-specific namespaces (
Pipedrive\versions\v1
and
Pipedrive\versions\v2
).
It is built to help you migrate.
Since v2 is the future (offering better performance and lower "token costs" against rate limits), this SDK is future-proof.
View source details for citation from GitHub. Opens side panel.
IsraelOrtuno/pipedrive
(Community):
This package is primarily a wrapper for
API v1
. While it is elegant, it lacks native, structured support for the new v2 endpoints. Using this today means you are building on a foundation that Pipedrive is actively trying to phase out.
2. Maintenance & Activity
2. Maintenance & Activity
Feature
pipedrive/client-php
(Official)
IsraelOrtuno/pipedrive
(Community)
Last Updated
Days/Weeks ago.
Highly active.
Months/Years ago.
Much slower pace.
Open Issues
Managed by a dedicated team at Pipedrive.
Managed by a single developer/community.
Response Time
High. Critical bugs are patched quickly.
Low. Many community packages lose steam over time.
PHP 8.x Support
Native and tested.
Generally works, but lacks modern PHP optimizations.
Feature
Last Updated
Open Issues
Response Time
PHP 8.x Support
pipedrive/client-php
(Official)
Days/Weeks ago.
Highly active.
Managed by a dedicated team at Pipedrive.
High. Critical bugs are patched quickly.
Native and tested.
IsraelOrtuno/pipedrive
(Community)
Months/Years ago.
Much slower pace.
Managed by a single developer/community.
Low. Many community packages lose steam over time.
Generally works, but lacks modern PHP optimizations.
Copy table
3. "The Laravel Way" vs. Stability
3. "The Laravel Way" vs. Stability
IsraelOrtuno's package
feels great in Laravel because of the
Facade
support and the fluent syntax:
Pipedrive::people()->findByName('John')
.
The Official SDK
is a bit "clunkier" because it's a generic PHP library. However, you can make it feel like a Laravel package in 5 minutes by creating a Service Provider.
Pro-tip:
Don't choose a package just because it has a Facade. It is much easier to write a 10-line wrapper for an official SDK than it is to fix a broken, abandoned community package when your CRM integration stops working.
4. What else should you think about?
4. What else should you think about?
A. The v2 Migration (The "July 2026" Problem)
A. The v2 Migration (The "July 2026" Problem)
Pipedrive has announced that v1 is being deprecated.
If you use the community package now, you are essentially creating technical debt. You will likely have to rewrite your entire integration in 12–18 months. By using the
Official SDK
, you can start writing your logic using
v2
namespaces immediately.
View source details for citation from Make Help Center. Opens side panel.
B. Rate Limiting (Token-based)
B. Rate Limiting (Token-based)
API v2 uses a "Token-based" rate limiting system which is much more generous than the old v1 limits.
The Official SDK handles these headers and limits much more gracefully.
View source details for citation from Pipedrive Developers. Opens side panel.
C. OAuth 2.0 vs API Token
C. OAuth 2.0 vs API Token
Official SDK:
Built with robust OAuth 2.0 support (the only way to get your app onto the Pipedrive Marketplace).
View source details for citation from GitHub. Opens side panel.
Community Wrapper:
Often relies on a simple API Token, which Pipedrive is discouraging for security reasons in favor of OAuth.
Final Recommendation
Final Recommendation
Use the Official
pipedrive/client-php
pipedrive/client-php
.
Why?
Direct v2 Access:
You won't have to rewrite your code when v1 is turned off....
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41896
|
|
41897
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,
the official
pipedrive/client-php
is the safer bet.
It ensures your integration won't break when Pipedrive updates its API, and the 10 minutes of extra setup time is worth the peace of mind.
Sources...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41897
|
|
41898
|
Unnamed Group
Platform Sprint 4 Q2 - Platform Team Unnamed Group
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Changes to the API
Changes to the API
Close tab
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
JY-18091 | Update composer to support php 8.5 by nikolaybiaivanov · Pull Request #12058 · jiminny/app
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[https://github.com/pipedrive/client-php](https://github.com/pipedrive/client-php) - Google Search
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Usage | Windsurf
Usage | Windsurf
Unnamed Group
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
[JY-20891] Sidekick SMS issue - Jira
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
JY-20891 add support for secondary email by LakyLak · Pull Request #12073 · jiminny/app
Unnamed Group
[SRD-6849] Recorded call does not appear on the dashboard - Jira
[SRD-6849] Recorded call does not appear on the dashboard - Jira
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Jiminny
Unnamed Group
[SRD-6853] Moxso - Potential deal stages bug - Jira
[SRD-6853] Moxso - Potential deal stages bug - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
[JY-20903] Recorded call does not appear on the dashboard - Jira
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
JY-20903 Update activity stage when opportunity is changed by LakyLak · Pull Request #12077 · jiminny/app
Configure SSH access to multiple environment - Engineering - Confluence
Configure SSH access to multiple environment - Engineering - Confluence
Useful commands - Engineering - Confluence
Useful commands - Engineering - Confluence
Dev Tools - Elastic
Dev Tools - Elastic
Jiminny
Jiminny
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
CloudWatch | eu-west-1
Unnamed Group
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
JY-20904 Fix UpdateActivityElasticSearchDocumentCommand find activity… by LakyLak · Pull Request #12078 · jiminny/app
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
[JY-20904] Fix UpdateActivityElasticSearchDocumentCommand - Jira
Pipedrive Developers Corner | Pipedrive API sandbox
Pipedrive Developers Corner | Pipedrive API sandbox
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
daniti/pipedrive-laravel: A Pipedrive App boilerplate with Laravel
pipedrive/client-php: Pipedrive API client for PHP
pipedrive/client-php: Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
IsraelOrtuno/pipedrive: Complete Pipedrive API client for PHP
Code search results
Code search results
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
You said
I am making and audio of pipedrive integration in laravel app. These are two candidates https://github.com/pipedrive/client-php and https://github.com/IsraelOrtuno/pipedrive. Evaluate them. Which one should I use and why?
Expand
Listen
Gemini said
Gemini said
When integrating Pipedrive into a Laravel application, the choice depends on whether you prioritize
long-term stability and official support
versus
Laravel-specific developer experience
.
Here is an evaluation of the two candidates:
1. pipedrive/client-php (Official SDK)
1.
pipedrive/client-php
pipedrive/client-php
(Official SDK)
This is the official Pipedrive API client for PHP.
Pros:
Always Up-to-Date:
Since it’s maintained by Pipedrive, it supports the latest API features (like the Leads API) and security patches immediately.
Stability:
It is a professional-grade SDK intended for production environments.
Auto-generated:
It is generated from the Pipedrive OpenAPI specification, ensuring high coverage of all endpoints.
Cons:
Generic PHP:
It is not "Laravel-aware." You will need to manually set up a Service Provider or Bindings in
AppServiceProvider
to use it as a singleton across your app.
Verbose:
The syntax can be more boilerplate-heavy compared to a package designed specifically for Laravel.
2. IsraelOrtuno/pipedrive (Laravel-focused)
2.
IsraelOrtuno/pipedrive
IsraelOrtuno/pipedrive
(Laravel-focused)
This is a popular community-driven wrapper specifically designed for Laravel.
Pros:
Laravel Integration:
Includes Service Providers and Facades out of the box.
You can call it like
Pipedrive::deals()->all()
.
View source details for citation from GitHub. Opens side panel.
Eloquent-like Syntax:
It feels more "natural" to a Laravel developer.
Ease of Setup:
Configuration is handled via a standard Laravel config file and
.env
.
Cons:
Maintenance Risk:
It is maintained by the community. If Pipedrive releases a major API change, this package might lag behind the official SDK.
Incomplete Coverage:
It may not support 100% of the Pipedrive API endpoints if they haven't been manually added to the wrapper.
Comparison Table
Comparison Table
Feature
pipedrive/client-php
IsraelOrtuno/pipedrive
Origin
Official (Pipedrive)
Community
Laravel Support
Manual (Needs Binding)
Native (Facade/Provider)
API Coverage
100% (Auto-generated)
High (Manual)
Best For
Enterprise / Long-term apps
Rapid Prototyping / Small apps
Feature
Origin
Laravel Support
API Coverage
Best For
pipedrive/client-php
Official (Pipedrive)
Manual (Needs Binding)
100% (Auto-generated)
Enterprise / Long-term apps
IsraelOrtuno/pipedrive
Community
Native (Facade/Provider)
High (Manual)
Rapid Prototyping / Small apps
Copy table
Recommendation: Which should you use?
Recommendation: Which should you use?
Use
pipedrive/client-php
(The Official SDK) if:
You are building a
production-grade enterprise application
where long-term maintenance and security are critical.
You need access to the absolute latest Pipedrive features (e.g., newest CRM updates).
Note:
You can easily make this "Laravel-friendly" by creating a simple Service Provider:
PHP
Download code
Copy code
// In AppServiceProvider.php
$this
->app->singleton(Pipedrive\Client::class,
function
(
$app
)
{
return
new
Pipedrive\Client(config(
'services.pipedrive.token'
));
});
Use
IsraelOrtuno/pipedrive
if:
You want to
move fast
and prefer the "Laravel way" (Facades, easy config).
Your requirements are standard (Deals, Persons, Organizations) and you don't need niche or brand-new API endpoints.
Final Verdict:
For most professional Laravel projects,...
|
Firefox
|
Changes to the API — Work
|
pipedrive.readme.io/docs/changes-to-the-api
|
41898
|
|
68762
|
New Device Logged In From Firefox Extension - [EMA New Device Logged In From Firefox Extension - [EMAIL] - Gmail
New Device Logged In From Firefox Extension - [EMAIL] - Gmail
Ambulatory sheet - Paperless-ngx
Ambulatory sheet - Paperless-ngx
Close tab
💬1 - Apple MacBook Pro 14" Space Black M5 Max | Laptop.bg - Технологията с теб
💬1 - Apple MacBook Pro 14" Space Black M5 Max | Laptop.bg - Технологията с теб
Apple Mac Studio M4 Max | Desktop.bg - Мощни PC Гейминг конфигурации, Персонални компютри на изплащане за игри и работа
Apple Mac Studio M4 Max | Desktop.bg - Мощни PC Гейминг конфигурации, Персонални компютри на изплащане за игри и работа...
|
Firefox
|
Ambulatory sheet - Paperless-ngx — Personal
|
paperless.lakylak.xyz/documents/11/details
|
68762
|
|
68763
|
New Device Logged In From Firefox Extension - [EMA New Device Logged In From Firefox Extension - [EMAIL] - Gmail
New Device Logged In From Firefox Extension - [EMAIL] - Gmail
Ambulatory sheet - Paperless-ngx
Ambulatory sheet - Paperless-ngx
Close tab
💬1 - Apple MacBook Pro 14" Space Black M5 Max | Laptop.bg - Технологията с теб
💬1 - Apple MacBook Pro 14" Space Black M5 Max | Laptop.bg - Технологията с теб
Apple Mac Studio M4 Max | Desktop.bg - Мощни PC Гейминг конфигурации, Персонални компютри на изплащане за игри и работа...
|
Firefox
|
Ambulatory sheet - Paperless-ngx — Personal
|
paperless.lakylak.xyz/documents/11/details
|
68763
|
|
77283
|
Platform Sprint 5 Q2 - Platform Team - Scrum Board Platform Sprint 5 Q2 - Platform Team - Scrum Board - Jira
[JY-20915] Add environment-specific email domains for text relay to prevent duplicate processing - Jira
Unnamed Group
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
Close tab
NVD - cve-2025-14179
NVD - cve-2025-14179
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
Text relay
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Jiminny
Jiminny
Audi Motors | Account | Salesforce
Audi Motors | Account | Salesforce
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)...
|
Firefox
|
jiminny/app/backend-code - Vanta — Work
|
nvd.nist.gov/vuln/detail/cve-2026-7261
|
77283
|
|
77284
|
Platform Sprint 5 Q2 - Platform Team - Scrum Board Platform Sprint 5 Q2 - Platform Team - Scrum Board - Jira
[JY-20915] Add environment-specific email domains for text relay to prevent duplicate processing - Jira
Unnamed Group
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
Close tab
NVD - cve-2025-14179
NVD - cve-2025-14179
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
Text relay
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Jiminny
Jiminny
Audi Motors | Account | Salesforce
Audi Motors | Account | Salesforce
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Vanta Agent
Product updates
Comments & activity
Settings
Lukas Kovalik
Help - command K
Help...
⌘+K
Home
Home
My work
My work
Vanta Agent
Vanta Agent
Tests
Tests
Reports
Reports
Compliance
Compliance
Customer trust
Customer trust
Risk
Risk
Vendors
Vendors
Assets
Assets
Inventory
Inventory
Code changes
Code changes
Vulnerabilities
Vulnerabilities
Security alerts
Security alerts
Personnel
Personnel
Integrations
Integrations
My security tasks
My security tasks
My access requests
My access requests
Collapse
Findings by asset
Findings by asset
/
jiminny/app/backend-code
jiminny/app/backend-code
jiminny/app/backend-code...
|
Firefox
|
jiminny/app/backend-code - Vanta — Work
|
nvd.nist.gov/vuln/detail/cve-2026-7261
|
77284
|
|
77285
|
Platform Sprint 5 Q2 - Platform Team - Scrum Board Platform Sprint 5 Q2 - Platform Team - Scrum Board - Jira
[JY-20915] Add environment-specific email domains for text relay to prevent duplicate processing - Jira
Unnamed Group
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-7261
NVD - cve-2026-7261
Close tab
NVD - cve-2025-14179
NVD - cve-2025-14179
Close tab
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
Text relay
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Jiminny
Jiminny
Audi Motors | Account | Salesforce
Audi Motors | Account | Salesforce
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-7261 Detail
CVE-2026-7261
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, when SoapServer is configured with SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance is handled incorrectly, resulting in freeing the object while keeping a pointer to it, which may lead to use-after-free. This may lead to memory corruption, information disclosure, or process crashes, with confidentiality, integrity, and availability impact on the vulnerable system.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name...
|
Firefox
|
NVD - cve-2026-7261 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-7261
|
77285
|
|
77289
|
Platform Sprint 5 Q2 - Platform Team - Scrum Board Platform Sprint 5 Q2 - Platform Team - Scrum Board - Jira
[JY-20915] Add environment-specific email domains for text relay to prevent duplicate processing - Jira
Unnamed Group
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-7261
NVD - cve-2026-7261
Close tab
NVD - cve-2025-14179
NVD - cve-2025-14179
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
Text relay
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Jiminny
Jiminny
Audi Motors | Account | Salesforce
Audi Motors | Account | Salesforce
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-7261 Detail
CVE-2026-7261
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, when SoapServer is configured with SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance is handled incorrectly, resulting in freeing the object while keeping a pointer to it, which may lead to use-after-free. This may lead to memory corruption, information disclosure, or process crashes, with confidentiality, integrity, and availability impact on the vulnerable system.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
Up to (excluding)
8.2.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.3.0
Up to (excluding)
8.3.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.4.0
Up to (excluding)
8.4.21
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.5.0
Up to (excluding)
8.5.6
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
From (including)
8.3.0
From (including)
8.4.0
From (including)
8.5.0
Up to (excluding)
8.2.31
Up to (excluding)
8.3.31
Up to (excluding)
8.4.21
Up to (excluding)
8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know
Are we missing a CPE here? Please let us know
.
Change History
Change History
2 change records found
show changes...
|
Firefox
|
NVD - cve-2026-7261 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-7261
|
77289
|
|
77290
|
Platform Sprint 5 Q2 - Platform Team - Scrum Board Platform Sprint 5 Q2 - Platform Team - Scrum Board - Jira
[JY-20915] Add environment-specific email domains for text relay to prevent duplicate processing - Jira
Unnamed Group
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-7261
NVD - cve-2026-7261
Close tab
NVD - cve-2025-14179
NVD - cve-2025-14179
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
[JY-20613] Allow owner's role to be selected when setting up a trial - Jira
Text relay
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
TypeError: Jiminny\Services\Mail\TextRelayService::setHistoryPoint(): Argument #2 ($historyPoint) must be of type int, string given, called in /home/jiminny/app/Services/Mail/TextRelayService.php on line 118 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20915 fix strict casting by LakyLak · Pull Request #12134 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Jiminny
Jiminny
Audi Motors | Account | Salesforce
Audi Motors | Account | Salesforce
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-7261 Detail
CVE-2026-7261
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, when SoapServer is configured with SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance is handled incorrectly, resulting in freeing the object while keeping a pointer to it, which may lead to use-after-free. This may lead to memory corruption, information disclosure, or process crashes, with confidentiality, integrity, and availability impact on the vulnerable system.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
https://github.com/php/php-src/security/advisories/GHSA-m33r-qmcv-p97q
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
Up to (excluding)
8.2.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.3.0
Up to (excluding)
8.3.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.4.0
Up to (excluding)
8.4.21
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.5.0
Up to (excluding)
8.5.6
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
From (including)
8.3.0
From (including)
8.4.0
From (including)
8.5.0
Up to (excluding)
8.2.31
Up to (excluding)
8.3.31
Up to (excluding)
8.4.21
Up to (excluding)
8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know
Are we missing a CPE here? Please let us know
.
Change History
Change History
2 change records found
show changes
show changes
QUICK INFO
QUICK INFO
CVE Dictionary Entry:
CVE-2026-7261
CVE-2026-7261
NVD Published Date:
05/10/2026
NVD Last Modified:
05/12/2026
Source:
PHP Group
X (link is external)
X
(link is external)
facebook (link is external)
facebook
(link is external)
linkedin (link is external)
linkedin
(link is external)
youtube (link is external)
youtube
(link is external)
rss
rss
govdelivery (link is external)
govdelivery
(link is external)
HEADQUARTERS
100 Bureau Drive
Gaithersburg, MD 20899
[PHONE]
[PHONE]
Webmaster
Webmaster
|
Contact Us
Contact Us
|
Our Other Offices
Our Other Offices
Incident Response Assistance and Non-NVD Related
Technical Cyber Security Questions:
US-CERT Security Operations Center
Email:
[EMAIL]
[EMAIL]
Phone: 1-[PHONE]
Site Privacy
Site Privacy
|
Accessibility
Accessibility
|
Privacy Program
Privacy Program
|
Copyrights
Copyrights
|
Vulnerability Disclosure
Vulnerability Disclosure
|
No Fear Act Policy
No Fear Act Policy
|
FOIA
FOIA
|
Environmental Policy
Environmental Policy
|
Scientific Integrity
Scientific Integrity
|
Information Quality Standards
Information Quality Standards
|
Commerce.gov
Commerce.gov
|
Science.gov
Science.gov
|
USA.gov
USA.gov...
|
Firefox
|
NVD - cve-2026-7261 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-7261
|
77290
|
|
31512
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Transferring data from nvd.nist.gov…...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31512
|
|
31513
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31513
|
|
31514
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31514
|
|
31515
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31515
|
|
31776
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Waiting for nvd.nist.gov…...
|
Firefox
|
jiminny/app/backend-code - Vanta — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31776
|
|
31777
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Waiting for nvd.nist.gov…...
|
Firefox
|
jiminny/app/backend-code - Vanta — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31777
|
|
31778
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Transferring data from nvd.nist.gov…...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31778
|
|
31779
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
Up to (excluding)
8.2.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.3.0
Up to (excluding)
8.3.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.4.0
Up to (excluding)
8.4.21
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.5.0
Up to (excluding)
8.5.6
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
From (including)
8.3.0
From (including)
8.4.0
From (including)
8.5.0
Up to (excluding)
8.2.31
Up to (excluding)
8.3.31
Up to (excluding)
8.4.21
Up to (excluding)
8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know
Are we missing a CPE here? Please let us know
.
Change History
Change History
2 change records found
show changes
show changes
QUICK INFO
QUICK INFO
CVE Dictionary Entry:
CVE-2026-6722
CVE-2026-6722
NVD Published Date:
05/10/2026
NVD Last Modified:
05/12/2026
Source:
PHP Group
X (link is external)
X
(link is external)
facebook (link is external)
facebook
(link is external)
linkedin (link is external)
linkedin
(link is external)
youtube (link is external)
youtube
(link is external)
rss
rss
govdelivery (link is external)
govdelivery
(link is external)
HEADQUARTERS
100 Bureau Drive
Gaithersburg, MD 20899
[PHONE]
[PHONE]
Webmaster
Webmaster
|
Contact Us
Contact Us
|
Our Other Offices
Our Other Offices
Incident Response Assistance and Non-NVD Related
Technical Cyber Security Questions:
US-CERT Security Operations Center
Email:...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31779
|
|
31780
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
Up to (excluding)
8.2.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.3.0
Up to (excluding)
8.3.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.4.0
Up to (excluding)
8.4.21
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.5.0
Up to (excluding)
8.5.6
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
From (including)
8.3.0
From (including)
8.4.0
From (including)
8.5.0
Up to (excluding)
8.2.31
Up to (excluding)
8.3.31
Up to (excluding)
8.4.21
Up to (excluding)
8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know
Are we missing a CPE here? Please let us know
.
Change History
Change History
2 change records found
show changes
show changes
QUICK INFO
QUICK INFO
CVE Dictionary Entry:
CVE-2026-6722
CVE-2026-6722
NVD Published Date:
05/10/2026
NVD Last Modified:
05/12/2026
Source:
PHP Group
X (link is external)
X
(link is external)
facebook (link is external)
facebook
(link is external)
linkedin (link is external)
linkedin
(link is external)
youtube (link is external)
youtube
(link is external)
rss
rss
govdelivery (link is external)
govdelivery
(link is external)
HEADQUARTERS
100 Bureau Drive
Gaithersburg, MD 20899
[PHONE]
[PHONE]
Webmaster
Webmaster
|
Contact Us
Contact Us
|
Our Other Offices
Our Other Offices
Incident Response Assistance and Non-NVD Related
Technical Cyber Security Questions:
US-CERT Security Operations Center
Email:
[EMAIL]
[EMAIL]
Phone: 1-[PHONE]
Site Privacy
Site Privacy
|
Accessibility
Accessibility
|
Privacy Program
Privacy Program
|
Copyrights
Copyrights
|
Vulnerability Disclosure
Vulnerability Disclosure
|
No Fear Act Policy
No Fear Act Policy
|
FOIA
FOIA
|
Environmental Policy
Environmental Policy
|
Scientific Integrity
Scientific Integrity
|
Information Quality Standards
Information Quality Standards
|
Commerce.gov
Commerce.gov
|
Science.gov
Science.gov
|
USA.gov
USA.gov...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31780
|
|
31781
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31781
|
|
31782
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4 kernel.org https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd kernel.org https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538 kernel.org https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023 kernel.org https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3 kernel.org https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275 kernel.org https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2 kernel.org Change History 3 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-23450</tabTitle>” with “<selection>References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://git.kernel.org/stable/c/1e4f873879e075bbd4eb1c644d6933303ac5eba4
kernel.org
https://git.kernel.org/stable/c/1fab5ece76fb42a761178dcd0ebcbf578377b0dd
kernel.org
https://git.kernel.org/stable/c/6d5e4538364b9ceb1ac2941a4deb86650afb3538
kernel.org
https://git.kernel.org/stable/c/cadf3da46c15523fba90d80c9955f536ee3b4023
kernel.org
https://git.kernel.org/stable/c/f00fc26c8a06442b225a350fe000c0a11483e6a3
kernel.org
https://git.kernel.org/stable/c/f315277856caeafcd996c2611afc085ca2d53275
kernel.org
https://git.kernel.org/stable/c/fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
kernel.org
Change History
3 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of NVD CVE-2026-23450 References
Summary of NVD CVE-2026-23450 References
The selected text provides external references and official disclaimers regarding the vulnerability
CVE-2026-23450
.
NIST Disclaimer
NIST Disclaimer
External Links:
Links lead to non-NIST websites for informational purposes.
Endorsement:
NIST does not endorse the views, facts, or commercial products found on these external sites.
Feedback:
Comments regarding the NVD page should be directed to
[EMAIL]
.
Reference Links
Reference Links
The following source code commits from
kernel.org
are provided as technical references or solutions:
Commit 1e4f873
Commit 1e4f873
Commit 1fab5ec
Commit 1fab5ec
Commit 6d5e453
Commit 6d5e453
Commit cadf3da
Commit cadf3da
Commit f00fc26
Commit f00fc26
Commit f315277
Commit f315277
Commit fd7579f
Commit fd7579f
Change History
Change History
There are
3 change records
available for this CVE entry.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said what is is and what can I do about it
You said
what is is and what can I do about it
Listen
Show thinking
Gemini said
Gemini said
Dealing with new CVEs can definitely be a hassle, but let's cut through the jargon and break down exactly what this vulnerability is and how to get your systems secured.
What is CVE-2026-23450?
What is CVE-2026-23450?
CVE-2026-23450
is a moderate-severity vulnerability located in the
Linux kernel
, specifically within its
net/smc
(Shared Memory Communications) component.
Here is what is going wrong under the hood:
The Flaw:
There is a "race condition" in the kernel. This happens when an SMC listen socket is being closed at the exact same time it is trying to process incoming TCP connections.
The Mechanism:
Because of this timing mismatch, the kernel gets confused about the state of the socket's memory. This triggers two specific bugs in the
smc_tcp_syn_recv_sock()
function: a
NULL pointer dereference
(looking for data at an empty memory address) and a
Use-After-Free
(trying to use memory that the system has already discarded).
The Impact:
If an attacker intentionally triggers this race condition, it will almost certainly cause a kernel panic and crash the system, resulting in a Denial of Service (DoS). In rare, highly complex scenarios, it could potentially allow for unauthorized code execution.
What Can You Do About It?
What Can You Do About It?
Because this is a kernel-level memory management flaw, mitigating it requires updating your underlying operating system:
Apply Vendor Patches (Highly Recommended):
The standard and most reliable fix is to update your Linux kernel. Major distributions (like Red Hat, Ubuntu, Amazon Linux, etc.) track this CVE and release patched kernel updates through their normal security channels. Running a simple system update via your package manager (like
apt
,
yum
, or
dnf
) and rebooting is usually all it takes.
Audit Your Environment:
Not all environments are vulnerable. For instance, recent security bulletins note that certain Amazon Linux distributions are unaffected, while specific Red Hat Enterprise Linux versions are. You'll want to check your specific OS vendor's security tracker for CVE-2026-23450.
Apply the Upstream Fix:
If you compile custom kernels for your infrastructure, you need to pull the specific git commits referenced in the NVD database. The developers fixed this by implementing Read-Copy-Update (RCU) locking to ensure the system safely pins the memory in place until the socket is fully done with it.
Which Linux distribution and kernel version are you currently running in your environment so we can check if you are actively exposed?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31782
|
|
31783
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism.
The system stores pointers to PHP objects in a global map without properly incrementing their reference counts,
leading to memory corruption.
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Stop response
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Gemini replied
Summarize page
Summarize page
An official website of the United States government
Here's how you know
Here's how you know
National Institute of Standards and Technology
NVD MENU
NVD
MENU
Information Technology Laboratory
Information Technology Laboratory
Information Technology Laboratory
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
NATIONAL VULNERABILITY DATABASE
VULNERABILITIES
VULNERABILITIES
CVE-2026-6722 Detail
CVE-2026-6722
Detail
Description
Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
Metrics
CVSS Version 4.0
CVSS Version 3.x
CVSS Version 2.0
NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.
CVSS 3.x Severity and Vector Strings:
NIST:
NVD
Base Score:
9.8 CRITICAL
9.8 CRITICAL
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to
[EMAIL]
[EMAIL]
.
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
URL
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
Source(s)
PHP Group
Tag(s)
Vendor Advisory
Weakness Enumeration
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
CWE-416
Use After Free
PHP Group
CWE-ID
CWE-416
CWE-416
CWE Name
Use After Free
Source
PHP Group
Known Affected Software Configurations Switch to CPE 2.2
Known Affected Software Configurations
Switch to CPE 2.2
Switch to CPE 2.2
Configuration 1
(
hide
hide
)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
Up to (excluding)
8.2.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.3.0
Up to (excluding)
8.3.31
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.4.0
Up to (excluding)
8.4.21
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.5.0
Up to (excluding)
8.5.6
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
Show Matching CPE(s)
Show Matching CPE(s)
From (including)
8.2.0
From (including)
8.3.0
From (including)
8.4.0
From (including)
8.5.0
Up to (excluding)
8.2.31
Up to (excluding)
8.3.31
Up to (excluding)
8.4.21
Up to (excluding)
8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know
Are we missing a CPE here? Please let us know
.
Change History
Change History
2 change records found
show changes
show changes
QUICK INFO
QUICK INFO
CVE Dictionary Entry:
CVE-2026-6722
CVE-2026-6722
NVD Published Date:
05/10/2026
NVD Last Modified:
05/12/2026
Source:
PHP Group
X (link is external)
X
(link is external)
facebook (link is external)
facebook
(link is external)
linkedin (link is external)
linkedin
(link is external)
youtube (link is external)
youtube
(link is external)
rss
rss
govdelivery (link is external)
govdelivery
(link is external)
HEADQUARTERS
100 Bureau Drive
Gaithersburg, MD 20899
[PHONE]
[PHONE]
Webmaster
Webmaster
|
Contact Us
Contact Us
|
Our Other Offices
Our Other Offices
Incident Response Assistance and Non-NVD Related
Technical Cyber Security Questions:
US-CERT Security Operations Center
Email:
[EMAIL]
[EMAIL]
Phone: 1-[PHONE]
Site Privacy
Site Privacy
|
Accessibility
Accessibility
|
Privacy Program
Privacy Program
|
Copyrights
Copyrights
|
Vulnerability Disclosure
Vulnerability Disclosure
|
No Fear Act Policy
No Fear Act Policy
|
FOIA
FOIA
|
Environmental Policy
Environmental Policy
|
Scientific Integrity
Scientific Integrity
|
Information Quality Standards
Information Quality Standards
|
Commerce.gov
Commerce.gov
|
Science.gov
Science.gov
|
USA.gov
USA.gov...
|
Firefox
|
NVD - cve-2026-6722 — Work
|
nvd.nist.gov/vuln/detail/cve-2026-6722
|
31783
|