We want to be able to easily get all klantcontacten for a BSN / vestigingsnummer. At the moment it seems the way to do that is to:
list all Betrokkenen for a Partij nummer
list all klantcontacten for a betrokken UUID
The problem with this approach is that both requests above return paginated responses that has to be streamed or just loaded in memory. In turn this means a lot of requests and increased complexity for the client.
What we think can help here is a query parameter to klantcontacten endpoint that can do queries on Partij (not sure about the namiing but perhaps: hadBetrokkenen.wasPartij__nummer)
Toegevoegde waarde / Added value
Reduced
complexity on client side (code complexity, memory, cpu)
number of roundtrips (we save several betrokkenen calls)
Aanvullende opmerkingen / Additional context
We're trying to list all interactions for a person/organization and display this in paginated dashboard.
In general we're looking for contactmomenten API replacement in the current 2.1 klantinteracties API
Thema / Theme
Klantinteracties API
Omschrijving / Description
We want to be able to easily get all klantcontacten for a BSN / vestigingsnummer. At the moment it seems the way to do that is to:
Betrokkenen
for aPartij
nummerklantcontacten
for a betrokken UUIDThe problem with this approach is that both requests above return paginated responses that has to be streamed or just loaded in memory. In turn this means a lot of requests and increased complexity for the client.
What we think can help here is a query parameter to
klantcontacten
endpoint that can do queries onPartij
(not sure about the namiing but perhaps:hadBetrokkenen.wasPartij__nummer
)Toegevoegde waarde / Added value
Reduced
betrokkenen
calls)Aanvullende opmerkingen / Additional context
We're trying to list all interactions for a person/organization and display this in paginated dashboard. In general we're looking for contactmomenten API replacement in the current 2.1 klantinteracties API