Skip to content
Other

namsor.com

NamSor API v2 sandbox and mock API

NamSor API v2 : enpoints to process personal names (gender, cultural origin or ethnicity) in all alphabets or languages. By default, enpoints use 1 unit per name (ex. Gender), but Ethnicity classification uses 10 to 20 units per name depending on taxonomy. Use GET methods for small tests, but prefer POST methods for higher throughput (batch processing of up to 100 names at a time). Need something Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
84
Collections
-
Event types
-
Start this simulation
example request
curl https://your-namsor.slurry.io/NamSorAPIv2/api2/json/apiKeyInfo \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.0.24.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 84.

  • GET/api2/json/anonymize/{source}/{anonymized}/{token}
  • GET/api2/json/apiKeyInfo
  • GET/api2/json/apiServices
  • GET/api2/json/apiStatus
  • GET/api2/json/apiUsage
  • GET/api2/json/apiUsageHistory
  • GET/api2/json/apiUsageHistoryAggregate
  • GET/api2/json/castegroupIndianFull/{subDivisionIso31662}/{personalNameFull}
  • POST/api2/json/castegroupIndianFullBatch
  • GET/api2/json/chineseNameCandidates/{chineseSurnameLatin}/{chineseGivenNameLatin}
  • POST/api2/json/chineseNameCandidatesBatch
  • POST/api2/json/chineseNameCandidatesGenderBatch
NamSor API v2 sandbox and mock API | Slurry