What is changing?

1. We’re adding a new Labels field (label_ids), with the type set for the following Persons and Organizations API endpoints. The Labels field can store up to 100 values per entity.
• GET /v1/deals/{id}/participants
• GET /v1/organizations
• GET /v1/organizations/{id}
• GET /v1/organizations/{id}/persons
• POST /v1/organizations
• PUT /v1/organizations/{id}
• PUT /v1/organizations/{id}/merge
• GET /v1/persons
• GET /v1/persons/{id}
• POST /v1/persons
• PUT /v1/persons/{id}
• PUT /v1/persons/{id}/merge

    <li>The endpoints <code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields" target="blank">GET /v1/personFields</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields" target="blank">GET /v1/organizationFields</a></code> will return the definition of these fields</li>

    <li>The old <code>Label</code> field and the new <code>Labels</code> field are updated synchronously based on these rules:</li>
          
          <ul>
            <li>When the <code>Labels</code> field is updated, the <code>Label</code> field value will be set to the first value of the <code>Labels</code> field.</li>
            <li>When the <code>Label</code> field is updated, the <code>Labels</code> field value will be overwritten by the <code>Label</code> field value.</li>
          </ul>
  </ol>
  
  <p><b>Why is this changing?</b></p>
  <p>We’re changing the behavior of the existing Label field to prevent data inconsistency between the old and new fields.</p>


  <p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

	</div>