Using the API
Frequently Asked Questions
Tutorials
BMPI Operations
- Add or Update Record
- Add or Update Record (Blinded)
- Get Person by Record
- Get Person by ID
- Match Demographics
- Match Demographics (Blinded)
- Delete Record
- Add Match Guidance
- Remove Match Guidance
Local Hashing Service
Metrics
Add or Update Record (Blinded)
POST /mpi/v1/blindedRecord/{source}/{identifier}
Adds a new record to the BMPI or updates a previously created one in privacy-preserving (blinded) mode. Returns the record’s assigned person ID, along with any changes to the BMPI resulting from the addition or update. The response also contains advisories of any ignored or invalid fields that may impact matching.
To use this method you must have a local hashing service installed and use the hash demographics operation to get hashed data for the BMPI. See Privacy-Preserving (Blinded) Mode for details.
Partial updates are not supported; an update will completely replace the existing record. See Understanding Matching for details.
Contents
Path Parameters
The system from which the record demographics were sourced.
The unique identifier of the record within the source. This will be stored directly in the BMPI (not hashed or encrypted), so consider what kind of identifiers are suitable to your use case.
Body Data
The B64 encoded hash provided by the local hashing service.
The version number provided by the local hashing service.
Response Data
The primary person matched in this operation.
The stable identifier for this person used across records (“Person ID”).
The constituent records that represent this person.
A source system with an internal means of identifying individuals.
The unique identifier of the record within the source. This will be stored directly in the BMPI (not hashed or encrypted), so consider what kind of identifiers are suitable to your use case.
The BMPI version of the person. As records are added or removed, this number will be incremented.
One of: Active or Retired. A record is retired when the original record has been superceded by new record(s).
If the person’s constituent records were merged into another person, this will contain the id for that person.
If the person’s constituent records were split into two or more persons, this will contain the ids for those persons.
Other persons that were changed in the process of adding/updating this record.
The stable identifier for this person used across records (“Person ID”).
The constituent records that represent this person.
A source system with an internal means of identifying individuals.
The unique identifier of the record within the source. This will be stored directly in the BMPI (not hashed or encrypted), so consider what kind of identifiers are suitable to your use case.
The BMPI version of the person. As records are added or removed, this number will be incremented.
One of: Active or Retired. A record is retired when the original record has been superceded by new record(s).
If the person’s constituent records were merged into another person, this will contain the id for that person.
If the person’s constituent records were split into two or more persons, this will contain the ids for those persons.
