> For the complete documentation index, see [llms.txt](https://help.hummingbird.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hummingbird.co/features/crm-entity-merging/api-interaction.md).

# API Interaction

You have uncluttered your CRM by merging duplicates - congrats! Now, what happens with future API events?

Unlike most CRMs where Secondary Profiles cease to exist and return errors when API updates are attempted, a Compliance CRM cannot just ignore new data that could impact compliance activities.

The Hummingbird CRM will continue to accept new data not only for the Primary Profile in a merge, but for all Constituent Members of that profile.

## How does this work?

Let's consider a scenario where two alerts are received (Alert 1 and Alert 2), with IDs of `PersonA` and `PersonB`, and two Person profiles are created. On closer inspection, these records are determined to be the same person and are merged into one profile, where the record containing the ID of PersonA is set as the Primary profile, resulting in Person AB.

<figure><img src="/files/XRg400aIS7WcNm8DuTyA" alt=""><figcaption><p>Merging in action</p></figcaption></figure>

After this merge, very important information is sent in Alert 3 (referencing ID `PersonA`) and Alert 4 (referencing ID `PersonB`). Most CRMs would return an error for the new information referencing `PersonB`. However, the Hummingbird API will intelligently route the alert for `PersonB` to the merged Profile, incorporating new data with a Primary designation if the field is currently empty, incorporate new data with a Secondary designation if there is currently a value in that field, and ignore duplicate data.

<figure><img src="/files/UiCpxpBCsBgJ6fOM59u3" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.hummingbird.co/features/crm-entity-merging/api-interaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.