Prospect Account API and other API Improvements

We’ve seen a significant uptick recently in folks interested in using our API to do really neat things, such as integrating custom CRMs, CMSes, and other third party data providers. As a product manager, it has been rewarding to get more feedback from users on where next to focus our API development efforts to keep expanding the depth and breadth of data available via our API.

Today, I’m excited to share a few recent improvements we’ve made to the API based on user feedback, starting with the addition of the ability to create, update, read, and query prospect accounts. Prospect Accounts are the analog to the account object in a traditional CRM system and contain account-wide data common to all leads or contacts at the same business or company. Along with prospects and opportunities, these three objects constitute the most widely used core data objects across our user base.

Additionally, we’ve just finished doing a full audit of all our API code to make sure it complies with HTTP and REST API best practices. This resulted in some performance improvements (yay!) and one minor change regarding HTTP status codes. Here’s what’s changed, straight from our API team:

Going forward, any request resulting in an authentication or validation failure will return an HTTP 4xx status code. Previously, an HTTP 200 OK response code was being returned, which we’ve definitely had a few confused people ask about, since it’s quite inconsistent with a core REST API tenet – to honor (to the greatest extent possible) the specification of the underlying HTTP semantics (headers, response codes, HTTP verbs, etc).

Couldn’t have said it better myself!

What does this change mean for most API users? Again, from our API team:

In most cases, nothing should have to change, as long as the API client has appropriate error and response code handling. However, depending on how the API client is written or the underlying HTTP library used, there may be some small changes required to honor these HTTP 4xx response codes in exceptional circumstances. Remember, since these 4xx codes are only sent when validation fails, most clients sending valid requests should never see them, anyway.

Last but not least, full documentation of the API is available on our API developer microsite which contains all the information you need to know to get you up and running with the Pardot API. Enjoy, and keep the great API feedback coming.