pipedrive 36.0.1 → 36.1.0

package/dist/versions/v1/api/leads-api.d.ts

@@ -11,7 +11,7 @@
  */
 import type { Configuration } from '../configuration';
 import type { AxiosInstance } from 'axios';
-import { RequestArgs, BaseAPI } from '../base';
+import { RequestArgs, BaseAPI, ApiResponse } from '../base';
 import { AddLeadRequest } from '../models';
 import { GetLeadIdResponse } from '../models';
 import { GetLeadResponse } from '../models';
@@ -123,6 +123,14 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     addLead(AddLeadRequest?: AddLeadRequest): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadResponse>>;
+    /**
+     * Same as `addLead`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Add a lead
+     * @param {AddLeadRequest} [AddLeadRequest]
+
+     * @throws {RequiredError}
+     */
+    addLeadWithHttpInfo(AddLeadRequest?: AddLeadRequest): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadResponse>>>;
     /**
      * Deletes a specific lead.
      * @summary Delete a lead
@@ -131,6 +139,14 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     deleteLead(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadIdResponse>>;
+    /**
+     * Same as `deleteLead`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Delete a lead
+     * @param {string} id The ID of the lead
+
+     * @throws {RequiredError}
+     */
+    deleteLeadWithHttpInfo(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadIdResponse>>>;
     /**
      * Returns multiple archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all archived leads
@@ -145,6 +161,20 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getArchivedLeads(limit?: number, start?: number, owner_id?: number, person_id?: number, organization_id?: number, filter_id?: number, sort?: 'id' | 'title' | 'owner_id' | 'creator_id' | 'was_seen' | 'expected_close_date' | 'next_activity_id' | 'add_time' | 'update_time'): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadsResponse>>;
+    /**
+     * Same as `getArchivedLeads`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Get all archived leads
+     * @param {number} [limit] For pagination, the limit of entries to be returned. If not provided, 100 items will be returned.
+     * @param {number} [start] For pagination, the position that represents the first result for the page
+     * @param {number} [owner_id] If supplied, only leads matching the given user will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;owner_id&#x60; when supplied.
+     * @param {number} [person_id] If supplied, only leads matching the given person will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;person_id&#x60; when supplied.
+     * @param {number} [organization_id] If supplied, only leads matching the given organization will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;organization_id&#x60; when supplied.
+     * @param {number} [filter_id] The ID of the filter to use
+     * @param {'id' | 'title' | 'owner_id' | 'creator_id' | 'was_seen' | 'expected_close_date' | 'next_activity_id' | 'add_time' | 'update_time'} [sort] The field names and sorting mode separated by a comma (&#x60;field_name_1 ASC&#x60;, &#x60;field_name_2 DESC&#x60;). Only first-level field keys are supported (no nested keys).
+
+     * @throws {RequiredError}
+     */
+    getArchivedLeadsWithHttpInfo(limit?: number, start?: number, owner_id?: number, person_id?: number, organization_id?: number, filter_id?: number, sort?: 'id' | 'title' | 'owner_id' | 'creator_id' | 'was_seen' | 'expected_close_date' | 'next_activity_id' | 'add_time' | 'update_time'): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadsResponse>>>;
     /**
      * Returns details of a specific lead. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals.
      * @summary Get one lead
@@ -153,6 +183,14 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getLead(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadResponse>>;
+    /**
+     * Same as `getLead`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Get one lead
+     * @param {string} id The ID of the lead
+
+     * @throws {RequiredError}
+     */
+    getLeadWithHttpInfo(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadResponse>>>;
     /**
      * Lists the users permitted to access a lead.
      * @summary List permitted users
@@ -161,6 +199,14 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getLeadUsers(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<UserIds>>;
+    /**
+     * Same as `getLeadUsers`, but resolves with the response body together with the HTTP status and headers.
+     * @summary List permitted users
+     * @param {string} id The ID of the lead
+
+     * @throws {RequiredError}
+     */
+    getLeadUsersWithHttpInfo(id: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<UserIds>>>;
     /**
      * Returns multiple not archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all leads
@@ -176,6 +222,21 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     getLeads(limit?: number, start?: number, owner_id?: number, person_id?: number, organization_id?: number, filter_id?: number, updated_since?: string, sort?: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadsResponse>>;
+    /**
+     * Same as `getLeads`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Get all leads
+     * @param {number} [limit] For pagination, the limit of entries to be returned. If not provided, 100 items will be returned.
+     * @param {number} [start] For pagination, the position that represents the first result for the page
+     * @param {number} [owner_id] If supplied, only leads matching the given user will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;owner_id&#x60; when supplied.
+     * @param {number} [person_id] If supplied, only leads matching the given person will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;person_id&#x60; when supplied.
+     * @param {number} [organization_id] If supplied, only leads matching the given organization will be returned. However, &#x60;filter_id&#x60; takes precedence over &#x60;organization_id&#x60; when supplied.
+     * @param {number} [filter_id] The ID of the filter to use
+     * @param {string} [updated_since] If set, only leads with an &#x60;update_time&#x60; later than or equal to this time are returned. In ISO 8601 format, e.g. 2025-01-01T10:20:00Z.
+     * @param {string} [sort] The field names and sorting mode separated by a comma (&#x60;field_name_1 ASC&#x60;, &#x60;field_name_2 DESC&#x60;). Only first-level field keys are supported (no nested keys). Supported fields: id, title, owner_id, creator_id, label_ids, value, source_name, was_seen, expected_close_date, next_activity_id, add_time, update_time, visible_to, and custom fields.
+
+     * @throws {RequiredError}
+     */
+    getLeadsWithHttpInfo(limit?: number, start?: number, owner_id?: number, person_id?: number, organization_id?: number, filter_id?: number, updated_since?: string, sort?: string): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadsResponse>>>;
     /**
      * Searches all leads by title, notes and/or custom fields. This endpoint is a wrapper of <a href=\"https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem\">/v1/itemSearch</a> with a narrower OAuth scope. Found leads can be filtered by the person ID and the organization ID.
      * @summary Search leads
@@ -191,6 +252,21 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     searchLeads(term: string, fields?: Set<'custom_fields' | 'notes' | 'title'>, exact_match?: boolean, person_id?: number, organization_id?: number, include_fields?: Set<'lead.was_seen'>, start?: number, limit?: number): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadSearchResponse>>;
+    /**
+     * Same as `searchLeads`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Search leads
+     * @param {string} term The search term to look for. Minimum 2 characters (or 1 if using &#x60;exact_match&#x60;). Please note that the search term has to be URL encoded.
+     * @param {Set<'custom_fields' | 'notes' | 'title'>} [fields] A comma-separated string array. The fields to perform the search from. Defaults to all of them.
+     * @param {boolean} [exact_match] When enabled, only full exact matches against the given term are returned. It is &lt;b&gt;not&lt;/b&gt; case sensitive.
+     * @param {number} [person_id] Will filter leads by the provided person ID. The upper limit of found leads associated with the person is 2000.
+     * @param {number} [organization_id] Will filter leads by the provided organization ID. The upper limit of found leads associated with the organization is 2000.
+     * @param {Set<'lead.was_seen'>} [include_fields] Supports including optional fields in the results which are not provided by default
+     * @param {number} [start] Pagination start. Note that the pagination is based on main results and does not include related items when using &#x60;search_for_related_items&#x60; parameter.
+     * @param {number} [limit] Items shown per page
+
+     * @throws {RequiredError}
+     */
+    searchLeadsWithHttpInfo(term: string, fields?: Set<'custom_fields' | 'notes' | 'title'>, exact_match?: boolean, person_id?: number, organization_id?: number, include_fields?: Set<'lead.was_seen'>, start?: number, limit?: number): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadSearchResponse>>>;
     /**
      * Updates one or more properties of a lead. Only properties included in the request will be updated. Send `null` to unset a property (applicable for example for `value`, `person_id` or `organization_id`). If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals. See an example given in the <a href=\"https://pipedrive.readme.io/docs/updating-custom-field-value\" target=\"_blank\" rel=\"noopener noreferrer\">updating custom fields’ values tutorial</a>.
      * @summary Update a lead
@@ -200,6 +276,15 @@ export declare const LeadsApiFp: (configuration?: Configuration) => {
      * @throws {RequiredError}
      */
     updateLead(id: string, UpdateLeadRequest?: UpdateLeadRequest): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<GetLeadResponse>>;
+    /**
+     * Same as `updateLead`, but resolves with the response body together with the HTTP status and headers.
+     * @summary Update a lead
+     * @param {string} id The ID of the lead
+     * @param {UpdateLeadRequest} [UpdateLeadRequest]
+
+     * @throws {RequiredError}
+     */
+    updateLeadWithHttpInfo(id: string, UpdateLeadRequest?: UpdateLeadRequest): Promise<(axios?: AxiosInstance, basePath?: string) => Promise<ApiResponse<GetLeadResponse>>>;
 };
 /**
  * LeadsApi - factory interface
@@ -214,6 +299,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     addLead(requestParameters?: LeadsApiAddLeadRequest): Promise<GetLeadResponse>;
+    addLeadWithHttpInfo(requestParameters?: LeadsApiAddLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
     /**
      * Deletes a specific lead.
      * @summary Delete a lead
@@ -222,6 +308,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     deleteLead(requestParameters: LeadsApiDeleteLeadRequest): Promise<GetLeadIdResponse>;
+    deleteLeadWithHttpInfo(requestParameters: LeadsApiDeleteLeadRequest): Promise<ApiResponse<GetLeadIdResponse>>;
     /**
      * Returns multiple archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all archived leads
@@ -230,6 +317,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     getArchivedLeads(requestParameters?: LeadsApiGetArchivedLeadsRequest): Promise<GetLeadsResponse>;
+    getArchivedLeadsWithHttpInfo(requestParameters?: LeadsApiGetArchivedLeadsRequest): Promise<ApiResponse<GetLeadsResponse>>;
     /**
      * Returns details of a specific lead. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals.
      * @summary Get one lead
@@ -238,6 +326,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     getLead(requestParameters: LeadsApiGetLeadRequest): Promise<GetLeadResponse>;
+    getLeadWithHttpInfo(requestParameters: LeadsApiGetLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
     /**
      * Lists the users permitted to access a lead.
      * @summary List permitted users
@@ -246,6 +335,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     getLeadUsers(requestParameters: LeadsApiGetLeadUsersRequest): Promise<UserIds>;
+    getLeadUsersWithHttpInfo(requestParameters: LeadsApiGetLeadUsersRequest): Promise<ApiResponse<UserIds>>;
     /**
      * Returns multiple not archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all leads
@@ -254,6 +344,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     getLeads(requestParameters?: LeadsApiGetLeadsRequest): Promise<GetLeadsResponse>;
+    getLeadsWithHttpInfo(requestParameters?: LeadsApiGetLeadsRequest): Promise<ApiResponse<GetLeadsResponse>>;
     /**
      * Searches all leads by title, notes and/or custom fields. This endpoint is a wrapper of <a href=\"https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem\">/v1/itemSearch</a> with a narrower OAuth scope. Found leads can be filtered by the person ID and the organization ID.
      * @summary Search leads
@@ -262,6 +353,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     searchLeads(requestParameters: LeadsApiSearchLeadsRequest): Promise<GetLeadSearchResponse>;
+    searchLeadsWithHttpInfo(requestParameters: LeadsApiSearchLeadsRequest): Promise<ApiResponse<GetLeadSearchResponse>>;
     /**
      * Updates one or more properties of a lead. Only properties included in the request will be updated. Send `null` to unset a property (applicable for example for `value`, `person_id` or `organization_id`). If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals. See an example given in the <a href=\"https://pipedrive.readme.io/docs/updating-custom-field-value\" target=\"_blank\" rel=\"noopener noreferrer\">updating custom fields’ values tutorial</a>.
      * @summary Update a lead
@@ -270,6 +362,7 @@ export declare const LeadsApiFactory: (configuration?: Configuration, basePath?:
      * @throws {RequiredError}
      */
     updateLead(requestParameters: LeadsApiUpdateLeadRequest): Promise<GetLeadResponse>;
+    updateLeadWithHttpInfo(requestParameters: LeadsApiUpdateLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
 };
 /**
  * Request parameters for addLead operation in LeadsApi.
@@ -517,6 +610,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     addLead(requestParameters?: LeadsApiAddLeadRequest): Promise<GetLeadResponse>;
+    /**
+     * Same as `addLead`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiAddLeadRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    addLeadWithHttpInfo(requestParameters?: LeadsApiAddLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
     /**
      * Deletes a specific lead.
      * @summary Delete a lead
@@ -526,6 +628,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     deleteLead(requestParameters: LeadsApiDeleteLeadRequest): Promise<GetLeadIdResponse>;
+    /**
+     * Same as `deleteLead`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiDeleteLeadRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    deleteLeadWithHttpInfo(requestParameters: LeadsApiDeleteLeadRequest): Promise<ApiResponse<GetLeadIdResponse>>;
     /**
      * Returns multiple archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all archived leads
@@ -535,6 +646,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     getArchivedLeads(requestParameters?: LeadsApiGetArchivedLeadsRequest): Promise<GetLeadsResponse>;
+    /**
+     * Same as `getArchivedLeads`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiGetArchivedLeadsRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    getArchivedLeadsWithHttpInfo(requestParameters?: LeadsApiGetArchivedLeadsRequest): Promise<ApiResponse<GetLeadsResponse>>;
     /**
      * Returns details of a specific lead. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals.
      * @summary Get one lead
@@ -544,6 +664,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     getLead(requestParameters: LeadsApiGetLeadRequest): Promise<GetLeadResponse>;
+    /**
+     * Same as `getLead`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiGetLeadRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    getLeadWithHttpInfo(requestParameters: LeadsApiGetLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
     /**
      * Lists the users permitted to access a lead.
      * @summary List permitted users
@@ -553,6 +682,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     getLeadUsers(requestParameters: LeadsApiGetLeadUsersRequest): Promise<UserIds>;
+    /**
+     * Same as `getLeadUsers`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiGetLeadUsersRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    getLeadUsersWithHttpInfo(requestParameters: LeadsApiGetLeadUsersRequest): Promise<ApiResponse<UserIds>>;
     /**
      * Returns multiple not archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields\' structure from deals.
      * @summary Get all leads
@@ -562,6 +700,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     getLeads(requestParameters?: LeadsApiGetLeadsRequest): Promise<GetLeadsResponse>;
+    /**
+     * Same as `getLeads`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiGetLeadsRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    getLeadsWithHttpInfo(requestParameters?: LeadsApiGetLeadsRequest): Promise<ApiResponse<GetLeadsResponse>>;
     /**
      * Searches all leads by title, notes and/or custom fields. This endpoint is a wrapper of <a href=\"https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem\">/v1/itemSearch</a> with a narrower OAuth scope. Found leads can be filtered by the person ID and the organization ID.
      * @summary Search leads
@@ -571,6 +718,15 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     searchLeads(requestParameters: LeadsApiSearchLeadsRequest): Promise<GetLeadSearchResponse>;
+    /**
+     * Same as `searchLeads`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiSearchLeadsRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    searchLeadsWithHttpInfo(requestParameters: LeadsApiSearchLeadsRequest): Promise<ApiResponse<GetLeadSearchResponse>>;
     /**
      * Updates one or more properties of a lead. Only properties included in the request will be updated. Send `null` to unset a property (applicable for example for `value`, `person_id` or `organization_id`). If a lead contains custom fields, the fields\' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field\'s value hasn\'t been set for the lead, it won\'t appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals. See an example given in the <a href=\"https://pipedrive.readme.io/docs/updating-custom-field-value\" target=\"_blank\" rel=\"noopener noreferrer\">updating custom fields’ values tutorial</a>.
      * @summary Update a lead
@@ -580,4 +736,13 @@ export declare class LeadsApi extends BaseAPI {
      * @memberof LeadsApi
      */
     updateLead(requestParameters: LeadsApiUpdateLeadRequest): Promise<GetLeadResponse>;
+    /**
+     * Same as `updateLead`, but resolves with the response body together with the HTTP status and headers.
+     * Error rejections keep their usual shape and additionally carry `$response: { status, headers }`.
+     * @param {LeadsApiUpdateLeadRequest} requestParameters Request parameters.
+
+     * @throws {RequiredError}
+     * @memberof LeadsApi
+     */
+    updateLeadWithHttpInfo(requestParameters: LeadsApiUpdateLeadRequest): Promise<ApiResponse<GetLeadResponse>>;
 }