HumDay

[USES 20 UNITS PER NAME] Infer the likely ethnicity/diaspora of a in NamSor

A documented NamSor operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

[USES 20 UNITS PER NAME] Infer the likely ethnicity/diaspora of a personal name, given a country of residence ISO2 code (ex.

  • GETReads data · personalv2.namsor.com/api2/json/diaspora/{countryIso2}/{firstName}/{lastName}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which NamSor operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other NamSor operations

All 84 NamSor operations

Questions

Can HumDay [uses 20 units per name] infer the likely ethnicity/diaspora of a in NamSor?
Yes. This operation is published in NamSor's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Does this change anything in my NamSor account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in NamSor.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your NamSor account.

Where this came from

Read from a published API description for NamSor at v2.namsor.com/NamSorAPIv2/api2/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.