@simplyhomes/sos-sdk/dist/generated/src/apis/RelationsLeadPropertiesAPIV4Api.d.ts

TypeScript SDK for Simply Homes SoS API v4

/**
 * API v4
 * Swagger documentation for API v4
 *
 * The version of the OpenAPI document: 4.0
 *
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */
import * as runtime from '../runtime';
import type { V4LeadPropertyRelationsCreateRelLeadPropertyBodyDto, V4LeadPropertyRelationsCreateRelLeadPropertyResponseDto, V4LeadPropertyRelationsDeleteRelLeadPropertyResponseDto, V4LeadPropertyRelationsGetRelLeadPropertiesInViewResponseDto, V4LeadPropertyRelationsGetRelLeadPropertiesResponseDto, V4LeadPropertyRelationsGetRelLeadPropertyColumnsResponseDto, V4LeadPropertyRelationsGetRelLeadPropertyResponseDto, V4LeadPropertyRelationsUpdateRelLeadPropertyBodyDto, V4LeadPropertyRelationsUpdateRelLeadPropertyResponseDto } from '../models/index';
export interface V4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Request {
    v4LeadPropertyRelationsCreateRelLeadPropertyBodyDto: V4LeadPropertyRelationsCreateRelLeadPropertyBodyDto;
}
export interface V4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Request {
    leadId: number;
    propertyId: string;
}
export interface V4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Request {
    viewId: number;
    limit?: number;
    offset?: number;
    countOnly?: boolean;
}
export interface V4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Request {
    viewId?: number;
    limit?: number;
    offset?: number;
    countOnly?: boolean;
}
export interface V4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Request {
    columns: string;
    leadId: number;
    propertyId: string;
}
export interface V4LeadPropertyRelationsControllerGetRelLeadPropertyV4Request {
    leadId: number;
    propertyId: string;
    viewId?: number;
}
export interface V4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Request {
    leadId: number;
    propertyId: string;
    v4LeadPropertyRelationsUpdateRelLeadPropertyBodyDto: V4LeadPropertyRelationsUpdateRelLeadPropertyBodyDto;
}
/**
 * RelationsLeadPropertiesAPIV4Api - interface
 *
 * @export
 * @interface RelationsLeadPropertiesAPIV4ApiInterface
 */
export interface RelationsLeadPropertiesAPIV4ApiInterface {
    /**
     *  ## POST /v4/rel-lead-properties  ### Overview Creates a new relationship between a lead and a property. This endpoint allows you to associate leads with properties they are interested in for investment analysis and pipeline management.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Request Body The request body should contain the lead and property identifiers to create the relationship.  #### Required Fields - **leadId** (number): Lead identifier - **pid** (string): Property identifier  ### Business Use Cases - **Lead Association**: Associating leads with properties they\'re interested in - **Pipeline Management**: Building and maintaining lead-property relationship data - **Interest Tracking**: Recording which properties leads have shown interest in - **Deal Flow**: Managing the flow of leads through property evaluations - **Investment Analysis**: Connecting leads to specific investment opportunities  ### Request Body Example ```json {   \"leadId\": 123,   \"pid\": \"property-456\" } ```
     * @summary Create a new rel-lead-property
     * @param {V4LeadPropertyRelationsCreateRelLeadPropertyBodyDto} v4LeadPropertyRelationsCreateRelLeadPropertyBodyDto
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsCreateRelLeadPropertyResponseDto>>;
    /**
     *  ## POST /v4/rel-lead-properties  ### Overview Creates a new relationship between a lead and a property. This endpoint allows you to associate leads with properties they are interested in for investment analysis and pipeline management.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Request Body The request body should contain the lead and property identifiers to create the relationship.  #### Required Fields - **leadId** (number): Lead identifier - **pid** (string): Property identifier  ### Business Use Cases - **Lead Association**: Associating leads with properties they\'re interested in - **Pipeline Management**: Building and maintaining lead-property relationship data - **Interest Tracking**: Recording which properties leads have shown interest in - **Deal Flow**: Managing the flow of leads through property evaluations - **Investment Analysis**: Connecting leads to specific investment opportunities  ### Request Body Example ```json {   \"leadId\": 123,   \"pid\": \"property-456\" } ```
     * Create a new rel-lead-property
     */
    v4LeadPropertyRelationsControllerCreateRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsCreateRelLeadPropertyResponseDto>;
    /**
     *  ## DELETE /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Deletes a specific lead-property relationship by its composite key. This endpoint removes the association between a lead and a property, effectively indicating that the lead is no longer interested in that particular property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Business Use Cases - **Interest Removal**: Remove lead interest from specific properties - **Pipeline Cleanup**: Clean up outdated or irrelevant lead-property associations - **Data Management**: Maintain accurate relationship data by removing obsolete connections - **Lead Reassignment**: Remove current associations before reassigning leads to new properties - **Status Changes**: Remove relationships when leads are no longer pursuing specific properties
     * @summary Delete a specific rel-lead-property by leadId and pid
     * @param {number} leadId The unique identifier of the lead
     * @param {string} propertyId The unique identifier of the property
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsDeleteRelLeadPropertyResponseDto>>;
    /**
     *  ## DELETE /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Deletes a specific lead-property relationship by its composite key. This endpoint removes the association between a lead and a property, effectively indicating that the lead is no longer interested in that particular property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Business Use Cases - **Interest Removal**: Remove lead interest from specific properties - **Pipeline Cleanup**: Clean up outdated or irrelevant lead-property associations - **Data Management**: Maintain accurate relationship data by removing obsolete connections - **Lead Reassignment**: Remove current associations before reassigning leads to new properties - **Status Changes**: Remove relationships when leads are no longer pursuing specific properties
     * Delete a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsDeleteRelLeadPropertyResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/viewId/{viewId}  ### Overview Retrieves lead-property relationships filtered by a specific view configuration. This endpoint applies predefined filters, sorting, and column selections based on the specified view ID, providing targeted access to relationship data.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **viewId** (number, required): Unique identifier for the view configuration to apply  ### Query Parameters - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100) - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Filtered Analysis**: Apply predefined filters for specific business scenarios - **Dashboard Views**: Load preconfigured relationship views for dashboards - **Report Generation**: Generate reports based on saved view configurations - **Team Workflows**: Access team-specific relationship data views - **Performance Monitoring**: Track relationships based on specific criteria
     * @summary Get rel-lead-properties with a specific viewId
     * @param {number} viewId The unique identifier of the view
     * @param {number} [limit] The maximum number of objects to return
     * @param {number} [offset] The offset for pagination, used to skip a number of objects
     * @param {boolean} [countOnly] Whether to return only the count of objects instead of the objects themselves
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertiesInViewResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/viewId/{viewId}  ### Overview Retrieves lead-property relationships filtered by a specific view configuration. This endpoint applies predefined filters, sorting, and column selections based on the specified view ID, providing targeted access to relationship data.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **viewId** (number, required): Unique identifier for the view configuration to apply  ### Query Parameters - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100) - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Filtered Analysis**: Apply predefined filters for specific business scenarios - **Dashboard Views**: Load preconfigured relationship views for dashboards - **Report Generation**: Generate reports based on saved view configurations - **Team Workflows**: Access team-specific relationship data views - **Performance Monitoring**: Track relationships based on specific criteria
     * Get rel-lead-properties with a specific viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertiesInViewResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties  ### Overview Retrieves lead-property relationships with optional filtering, sorting, and pagination capabilities. This endpoint provides access to the associations between leads and properties in the real estate investment pipeline, enabling comprehensive relationship management and analytics.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for filtering and column selection - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100)   - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Lead Management**: Track which properties are associated with specific leads - **Property Analytics**: Analyze interest patterns and engagement across property inventory - **Pipeline Management**: Monitor lead progression through property evaluations - **Relationship Mapping**: Build comprehensive views of lead-property associations - **Performance Metrics**: Generate reports on lead-property interaction patterns - **Investment Analysis**: Connect leads to specific investment opportunities for decision making  ### Response Format Returns paginated list of lead-property relationships with metadata including total count and relationship details.
     * @summary Get relations lead properties with optional viewId
     * @param {number} [viewId] The ID of the view to use for retrieving the repository
     * @param {number} [limit] The maximum number of objects to return
     * @param {number} [offset] The offset for pagination, used to skip a number of objects
     * @param {boolean} [countOnly] Whether to return only the count of objects instead of the objects themselves
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertiesResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties  ### Overview Retrieves lead-property relationships with optional filtering, sorting, and pagination capabilities. This endpoint provides access to the associations between leads and properties in the real estate investment pipeline, enabling comprehensive relationship management and analytics.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for filtering and column selection - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100)   - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Lead Management**: Track which properties are associated with specific leads - **Property Analytics**: Analyze interest patterns and engagement across property inventory - **Pipeline Management**: Monitor lead progression through property evaluations - **Relationship Mapping**: Build comprehensive views of lead-property associations - **Performance Metrics**: Generate reports on lead-property interaction patterns - **Investment Analysis**: Connect leads to specific investment opportunities for decision making  ### Response Format Returns paginated list of lead-property relationships with metadata including total count and relationship details.
     * Get relations lead properties with optional viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertiesResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}/{columns}  ### Overview Retrieves specific columns of a lead-property relationship by its composite key. This endpoint allows selective data retrieval, returning only the specified columns for optimal performance and bandwidth usage.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property - **columns** (string, required): Comma-separated list of column names to retrieve  ### Business Use Cases - **Performance Optimization**: Retrieve only necessary data fields - **Bandwidth Conservation**: Reduce payload size for mobile or limited bandwidth scenarios - **Selective Data Access**: Access specific relationship attributes for targeted analysis - **Integration Efficiency**: Support external systems requiring only specific data points
     * @summary Get specific columns of a rel-lead-property by leadId and propertyId
     * @param {string} columns Comma-separated list of column names
     * @param {number} leadId The unique identifier of the lead
     * @param {string} propertyId The unique identifier of the property
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertyColumnsResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}/{columns}  ### Overview Retrieves specific columns of a lead-property relationship by its composite key. This endpoint allows selective data retrieval, returning only the specified columns for optimal performance and bandwidth usage.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property - **columns** (string, required): Comma-separated list of column names to retrieve  ### Business Use Cases - **Performance Optimization**: Retrieve only necessary data fields - **Bandwidth Conservation**: Reduce payload size for mobile or limited bandwidth scenarios - **Selective Data Access**: Access specific relationship attributes for targeted analysis - **Integration Efficiency**: Support external systems requiring only specific data points
     * Get specific columns of a rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertyColumnsResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Retrieves a specific lead-property relationship by its composite key (leadId and pid). This endpoint provides detailed information about a single relationship between a lead and a property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for column selection and related data inclusion  ### Business Use Cases - **Relationship Verification**: Confirm specific lead-property associations - **Detail Analysis**: Get comprehensive details about a specific relationship - **Data Validation**: Verify relationship existence and properties - **Integration Support**: Support for external system integrations requiring specific relationship data
     * @summary Get a specific rel-lead-property by leadId and propertyId
     * @param {number} leadId The unique identifier of the lead
     * @param {string} propertyId The unique identifier of the property
     * @param {number} [viewId] The ID of the view to use for retrieving the repository
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertyResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Retrieves a specific lead-property relationship by its composite key (leadId and pid). This endpoint provides detailed information about a single relationship between a lead and a property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for column selection and related data inclusion  ### Business Use Cases - **Relationship Verification**: Confirm specific lead-property associations - **Detail Analysis**: Get comprehensive details about a specific relationship - **Data Validation**: Verify relationship existence and properties - **Integration Support**: Support for external system integrations requiring specific relationship data
     * Get a specific rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertyResponseDto>;
    /**
     *  ## PATCH /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Updates a specific lead-property relationship by its composite key. Note that relationship tables typically have minimal updateable fields since they primarily manage associations between entities.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Request Body The request body should contain the fields to update. For relationship tables, this is typically empty or contains metadata fields.  ### Business Use Cases - **Relationship Metadata**: Update any metadata associated with the relationship - **Status Changes**: Modify relationship status or flags if applicable - **Audit Trail**: Update relationship audit information  ### Note This endpoint is rarely used for pure relationship tables as they typically only contain foreign keys. It\'s included for API completeness and future extensibility.
     * @summary Update a specific rel-lead-property by leadId and pid
     * @param {number} leadId The unique identifier of the lead
     * @param {string} propertyId The unique identifier of the property
     * @param {V4LeadPropertyRelationsUpdateRelLeadPropertyBodyDto} v4LeadPropertyRelationsUpdateRelLeadPropertyBodyDto
     * @param {*} [options] Override http request option.
     * @throws {RequiredError}
     * @memberof RelationsLeadPropertiesAPIV4ApiInterface
     */
    v4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsUpdateRelLeadPropertyResponseDto>>;
    /**
     *  ## PATCH /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Updates a specific lead-property relationship by its composite key. Note that relationship tables typically have minimal updateable fields since they primarily manage associations between entities.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Request Body The request body should contain the fields to update. For relationship tables, this is typically empty or contains metadata fields.  ### Business Use Cases - **Relationship Metadata**: Update any metadata associated with the relationship - **Status Changes**: Modify relationship status or flags if applicable - **Audit Trail**: Update relationship audit information  ### Note This endpoint is rarely used for pure relationship tables as they typically only contain foreign keys. It\'s included for API completeness and future extensibility.
     * Update a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsUpdateRelLeadPropertyResponseDto>;
}
/**
 *
 */
export declare class RelationsLeadPropertiesAPIV4Api extends runtime.BaseAPI implements RelationsLeadPropertiesAPIV4ApiInterface {
    /**
     *  ## POST /v4/rel-lead-properties  ### Overview Creates a new relationship between a lead and a property. This endpoint allows you to associate leads with properties they are interested in for investment analysis and pipeline management.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Request Body The request body should contain the lead and property identifiers to create the relationship.  #### Required Fields - **leadId** (number): Lead identifier - **pid** (string): Property identifier  ### Business Use Cases - **Lead Association**: Associating leads with properties they\'re interested in - **Pipeline Management**: Building and maintaining lead-property relationship data - **Interest Tracking**: Recording which properties leads have shown interest in - **Deal Flow**: Managing the flow of leads through property evaluations - **Investment Analysis**: Connecting leads to specific investment opportunities  ### Request Body Example ```json {   \"leadId\": 123,   \"pid\": \"property-456\" } ```
     * Create a new rel-lead-property
     */
    v4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsCreateRelLeadPropertyResponseDto>>;
    /**
     *  ## POST /v4/rel-lead-properties  ### Overview Creates a new relationship between a lead and a property. This endpoint allows you to associate leads with properties they are interested in for investment analysis and pipeline management.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Request Body The request body should contain the lead and property identifiers to create the relationship.  #### Required Fields - **leadId** (number): Lead identifier - **pid** (string): Property identifier  ### Business Use Cases - **Lead Association**: Associating leads with properties they\'re interested in - **Pipeline Management**: Building and maintaining lead-property relationship data - **Interest Tracking**: Recording which properties leads have shown interest in - **Deal Flow**: Managing the flow of leads through property evaluations - **Investment Analysis**: Connecting leads to specific investment opportunities  ### Request Body Example ```json {   \"leadId\": 123,   \"pid\": \"property-456\" } ```
     * Create a new rel-lead-property
     */
    v4LeadPropertyRelationsControllerCreateRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerCreateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsCreateRelLeadPropertyResponseDto>;
    /**
     *  ## DELETE /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Deletes a specific lead-property relationship by its composite key. This endpoint removes the association between a lead and a property, effectively indicating that the lead is no longer interested in that particular property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Business Use Cases - **Interest Removal**: Remove lead interest from specific properties - **Pipeline Cleanup**: Clean up outdated or irrelevant lead-property associations - **Data Management**: Maintain accurate relationship data by removing obsolete connections - **Lead Reassignment**: Remove current associations before reassigning leads to new properties - **Status Changes**: Remove relationships when leads are no longer pursuing specific properties
     * Delete a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsDeleteRelLeadPropertyResponseDto>>;
    /**
     *  ## DELETE /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Deletes a specific lead-property relationship by its composite key. This endpoint removes the association between a lead and a property, effectively indicating that the lead is no longer interested in that particular property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Business Use Cases - **Interest Removal**: Remove lead interest from specific properties - **Pipeline Cleanup**: Clean up outdated or irrelevant lead-property associations - **Data Management**: Maintain accurate relationship data by removing obsolete connections - **Lead Reassignment**: Remove current associations before reassigning leads to new properties - **Status Changes**: Remove relationships when leads are no longer pursuing specific properties
     * Delete a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerDeleteRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsDeleteRelLeadPropertyResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/viewId/{viewId}  ### Overview Retrieves lead-property relationships filtered by a specific view configuration. This endpoint applies predefined filters, sorting, and column selections based on the specified view ID, providing targeted access to relationship data.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **viewId** (number, required): Unique identifier for the view configuration to apply  ### Query Parameters - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100) - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Filtered Analysis**: Apply predefined filters for specific business scenarios - **Dashboard Views**: Load preconfigured relationship views for dashboards - **Report Generation**: Generate reports based on saved view configurations - **Team Workflows**: Access team-specific relationship data views - **Performance Monitoring**: Track relationships based on specific criteria
     * Get rel-lead-properties with a specific viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertiesInViewResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/viewId/{viewId}  ### Overview Retrieves lead-property relationships filtered by a specific view configuration. This endpoint applies predefined filters, sorting, and column selections based on the specified view ID, providing targeted access to relationship data.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **viewId** (number, required): Unique identifier for the view configuration to apply  ### Query Parameters - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100) - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Filtered Analysis**: Apply predefined filters for specific business scenarios - **Dashboard Views**: Load preconfigured relationship views for dashboards - **Report Generation**: Generate reports based on saved view configurations - **Team Workflows**: Access team-specific relationship data views - **Performance Monitoring**: Track relationships based on specific criteria
     * Get rel-lead-properties with a specific viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesInViewV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertiesInViewResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties  ### Overview Retrieves lead-property relationships with optional filtering, sorting, and pagination capabilities. This endpoint provides access to the associations between leads and properties in the real estate investment pipeline, enabling comprehensive relationship management and analytics.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for filtering and column selection - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100)   - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Lead Management**: Track which properties are associated with specific leads - **Property Analytics**: Analyze interest patterns and engagement across property inventory - **Pipeline Management**: Monitor lead progression through property evaluations - **Relationship Mapping**: Build comprehensive views of lead-property associations - **Performance Metrics**: Generate reports on lead-property interaction patterns - **Investment Analysis**: Connect leads to specific investment opportunities for decision making  ### Response Format Returns paginated list of lead-property relationships with metadata including total count and relationship details.
     * Get relations lead properties with optional viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertiesResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties  ### Overview Retrieves lead-property relationships with optional filtering, sorting, and pagination capabilities. This endpoint provides access to the associations between leads and properties in the real estate investment pipeline, enabling comprehensive relationship management and analytics.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for filtering and column selection - **limit** (number, optional): Maximum number of relationships to return (default: 20, max: 100)   - **offset** (number, optional): Number of relationships to skip for pagination (default: 0) - **countOnly** (boolean, optional): Return only the total count without relationship data  ### Business Use Cases - **Lead Management**: Track which properties are associated with specific leads - **Property Analytics**: Analyze interest patterns and engagement across property inventory - **Pipeline Management**: Monitor lead progression through property evaluations - **Relationship Mapping**: Build comprehensive views of lead-property associations - **Performance Metrics**: Generate reports on lead-property interaction patterns - **Investment Analysis**: Connect leads to specific investment opportunities for decision making  ### Response Format Returns paginated list of lead-property relationships with metadata including total count and relationship details.
     * Get relations lead properties with optional viewId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertiesV4(requestParameters?: V4LeadPropertyRelationsControllerGetRelLeadPropertiesV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertiesResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}/{columns}  ### Overview Retrieves specific columns of a lead-property relationship by its composite key. This endpoint allows selective data retrieval, returning only the specified columns for optimal performance and bandwidth usage.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property - **columns** (string, required): Comma-separated list of column names to retrieve  ### Business Use Cases - **Performance Optimization**: Retrieve only necessary data fields - **Bandwidth Conservation**: Reduce payload size for mobile or limited bandwidth scenarios - **Selective Data Access**: Access specific relationship attributes for targeted analysis - **Integration Efficiency**: Support external systems requiring only specific data points
     * Get specific columns of a rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertyColumnsResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}/{columns}  ### Overview Retrieves specific columns of a lead-property relationship by its composite key. This endpoint allows selective data retrieval, returning only the specified columns for optimal performance and bandwidth usage.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property - **columns** (string, required): Comma-separated list of column names to retrieve  ### Business Use Cases - **Performance Optimization**: Retrieve only necessary data fields - **Bandwidth Conservation**: Reduce payload size for mobile or limited bandwidth scenarios - **Selective Data Access**: Access specific relationship attributes for targeted analysis - **Integration Efficiency**: Support external systems requiring only specific data points
     * Get specific columns of a rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyColumnsV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertyColumnsResponseDto>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Retrieves a specific lead-property relationship by its composite key (leadId and pid). This endpoint provides detailed information about a single relationship between a lead and a property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for column selection and related data inclusion  ### Business Use Cases - **Relationship Verification**: Confirm specific lead-property associations - **Detail Analysis**: Get comprehensive details about a specific relationship - **Data Validation**: Verify relationship existence and properties - **Integration Support**: Support for external system integrations requiring specific relationship data
     * Get a specific rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsGetRelLeadPropertyResponseDto>>;
    /**
     *  ## GET /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Retrieves a specific lead-property relationship by its composite key (leadId and pid). This endpoint provides detailed information about a single relationship between a lead and a property.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Query Parameters - **viewId** (number, optional): Apply specific view configuration for column selection and related data inclusion  ### Business Use Cases - **Relationship Verification**: Confirm specific lead-property associations - **Detail Analysis**: Get comprehensive details about a specific relationship - **Data Validation**: Verify relationship existence and properties - **Integration Support**: Support for external system integrations requiring specific relationship data
     * Get a specific rel-lead-property by leadId and propertyId
     */
    v4LeadPropertyRelationsControllerGetRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerGetRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsGetRelLeadPropertyResponseDto>;
    /**
     *  ## PATCH /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Updates a specific lead-property relationship by its composite key. Note that relationship tables typically have minimal updateable fields since they primarily manage associations between entities.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Request Body The request body should contain the fields to update. For relationship tables, this is typically empty or contains metadata fields.  ### Business Use Cases - **Relationship Metadata**: Update any metadata associated with the relationship - **Status Changes**: Modify relationship status or flags if applicable - **Audit Trail**: Update relationship audit information  ### Note This endpoint is rarely used for pure relationship tables as they typically only contain foreign keys. It\'s included for API completeness and future extensibility.
     * Update a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Raw(requestParameters: V4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V4LeadPropertyRelationsUpdateRelLeadPropertyResponseDto>>;
    /**
     *  ## PATCH /v4/rel-lead-properties/{leadId}/{pid}  ### Overview Updates a specific lead-property relationship by its composite key. Note that relationship tables typically have minimal updateable fields since they primarily manage associations between entities.  ### Authentication - **x-api-key**: Required API key for authentication - **organization-id**: Required organization identifier in header  ### Path Parameters - **leadId** (number, required): Unique identifier for the lead - **pid** (string, required): Unique identifier for the property  ### Request Body The request body should contain the fields to update. For relationship tables, this is typically empty or contains metadata fields.  ### Business Use Cases - **Relationship Metadata**: Update any metadata associated with the relationship - **Status Changes**: Modify relationship status or flags if applicable - **Audit Trail**: Update relationship audit information  ### Note This endpoint is rarely used for pure relationship tables as they typically only contain foreign keys. It\'s included for API completeness and future extensibility.
     * Update a specific rel-lead-property by leadId and pid
     */
    v4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4(requestParameters: V4LeadPropertyRelationsControllerUpdateRelLeadPropertyV4Request, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V4LeadPropertyRelationsUpdateRelLeadPropertyResponseDto>;
}
//# sourceMappingURL=RelationsLeadPropertiesAPIV4Api.d.ts.map