Namsor

NamSor API v2

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…

AI & machine learning#openapi#text

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

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 you can't find here? We have many more features coming soon. Let us know, we'll do our best to add it!

Endpoints 84

personal

  • GET[USES 20 UNITS PER NAME COUPLE] Infer several classifications for a cross border interaction between names (ex. remit, travel, intl com)/api2/json/corridor/:countryIso2From/:firstNameFrom/:lastNameFrom/:countryIso2To/:firstNameTo/:lastNameTo
  • POST[USES 20 UNITS PER NAME PAIR] Infer several classifications for up to 100 cross border interaction between names (ex. remit, travel, intl com)/api2/json/corridorBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely country of residence of a personal full name, or one surname. Assumes names as they are in the country of residence OR the country of origin./api2/json/country/:personalNameFull
  • POST[USES 10 UNITS PER NAME] Infer the likely country of residence of up to 100 personal full names, or surnames. Assumes names as they are in the country of residence OR the country of origin./api2/json/countryBatch
  • GET[USES 20 UNITS PER NAME] Infer the likely ethnicity/diaspora of a personal name, given a country of residence ISO2 code (ex. US, CA, AU, NZ etc.)/api2/json/diaspora/:countryIso2/:firstName/:lastName
  • POST[USES 20 UNITS PER NAME] Infer the likely ethnicity/diaspora of up to 100 personal names, given a country of residence ISO2 code (ex. US, CA, AU, NZ etc.)/api2/json/diasporaBatch
  • GETInfer the likely gender of a just a fiven name, assuming default 'US' local context. Please use preferably full names and local geographic context for better accuracy./api2/json/gender/:firstName
  • GETInfer the likely gender of a name./api2/json/gender/:firstName/:lastName
  • POSTInfer the likely gender of up to 100 names, detecting automatically the cultural context./api2/json/genderBatch
  • GETInfer the likely gender of a full name, ex. John H. Smith/api2/json/genderFull/:fullName
  • POSTInfer the likely gender of up to 100 full names, detecting automatically the cultural context./api2/json/genderFullBatch
  • GETInfer the likely gender of a full name, given a local context (ISO2 country code)./api2/json/genderFullGeo/:fullName/:countryIso2
  • POSTInfer the likely gender of up to 100 full names, with a given cultural context (country ISO2 code)./api2/json/genderFullGeoBatch
  • GETInfer the likely gender of a name, given a local context (ISO2 country code)./api2/json/genderGeo/:firstName/:lastName/:countryIso2
  • POSTInfer the likely gender of up to 100 names, each given a local context (ISO2 country code)./api2/json/genderGeoBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely country of origin of a personal name. Assumes names as they are in the country of origin. For US, CA, AU, NZ and other melting-pots : use 'diaspora' instead./api2/json/origin/:firstName/:lastName
  • POST[USES 10 UNITS PER NAME] Infer the likely country of origin of up to 100 names, detecting automatically the cultural context./api2/json/originBatch
  • GETInfer the likely first/last name structure of a name, ex. John Smith or SMITH, John or SMITH; John. /api2/json/parseName/:nameFull
  • GETInfer the likely first/last name structure of a name, ex. John Smith or SMITH, John or SMITH; John. For better accuracy, provide a geographic context./api2/json/parseName/:nameFull/:countryIso2
  • POSTInfer the likely first/last name structure of a name, ex. John Smith or SMITH, John or SMITH; John./api2/json/parseNameBatch
  • POSTInfer the likely first/last name structure of a name, ex. John Smith or SMITH, John or SMITH; John. Giving a local context improves precision. /api2/json/parseNameGeoBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely religion of a personal full name. NB: only for INDIA (as of current version)./api2/json/religionFull/:countryIso2/:subDivisionIso31662/:personalNameFull
  • POST[USES 10 UNITS PER NAME] Infer the likely religion of up to 100 personal full names. NB: only for India as of currently./api2/json/religionFullBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely origin of a name at a country subclassification level (state or regeion). Initially, this is only supported for India (ISO2 code 'IN')./api2/json/subclassification/:countryIso2/:firstName/:lastName
  • POST[USES 10 UNITS PER NAME] Infer the likely origin of a list of up to 100 names at a country subclassification level (state or regeion). Initially, this is only supported for India (ISO2 code 'IN')./api2/json/subclassificationBatch
  • GET[USES 10 UNITS PER NAME] Infer a US resident's likely race/ethnicity according to US Census taxonomy W_NL (white, non latino), HL (hispano latino), A (asian, non latino), B_NL (black, non latino). Optionally add header X-OPTION-USRACEETHNICITY-TAXONOMY: USRACEETHNICITY-6CLASSES for two additional classes, AI_AN (American Indian or Alaskan Native) and PI (Pacific Islander)./api2/json/usRaceEthnicity/:firstName/:lastName
  • POST[USES 10 UNITS PER NAME] Infer up-to 100 US resident's likely race/ethnicity according to US Census taxonomy. Output is W_NL (white, non latino), HL (hispano latino), A (asian, non latino), B_NL (black, non latino). Optionally add header X-OPTION-USRACEETHNICITY-TAXONOMY: USRACEETHNICITY-6CLASSES for two additional classes, AI_AN (American Indian or Alaskan Native) and PI (Pacific Islander)./api2/json/usRaceEthnicityBatch
  • GET[USES 10 UNITS PER NAME] Infer a US resident's likely race/ethnicity according to US Census taxonomy, using (optional) ZIP5 code info. Output is W_NL (white, non latino), HL (hispano latino), A (asian, non latino), B_NL (black, non latino). Optionally add header X-OPTION-USRACEETHNICITY-TAXONOMY: USRACEETHNICITY-6CLASSES for two additional classes, AI_AN (American Indian or Alaskan Native) and PI (Pacific Islander)./api2/json/usRaceEthnicityZIP5/:firstName/:lastName/:zip5Code
  • POST[USES 10 UNITS PER NAME] Infer up-to 100 US resident's likely race/ethnicity according to US Census taxonomy, with (optional) ZIP code. Output is W_NL (white, non latino), HL (hispano latino), A (asian, non latino), B_NL (black, non latino). Optionally add header X-OPTION-USRACEETHNICITY-TAXONOMY: USRACEETHNICITY-6CLASSES for two additional classes, AI_AN (American Indian or Alaskan Native) and PI (Pacific Islander)./api2/json/usZipRaceEthnicityBatch

social

  • GET[USES 11 UNITS PER NAME] Infer the likely country and phone prefix, given a personal name and formatted / unformatted phone number./api2/json/phoneCode/:firstName/:lastName/:phoneNumber
  • POST[USES 11 UNITS PER NAME] Infer the likely country and phone prefix, of up to 100 personal names, detecting automatically the local context given a name and formatted / unformatted phone number./api2/json/phoneCodeBatch
  • GET[USES 11 UNITS PER NAME] Infer the likely phone prefix, given a personal name and formatted / unformatted phone number, with a local context (ISO2 country of residence)./api2/json/phoneCodeGeo/:firstName/:lastName/:phoneNumber/:countryIso2
  • POST[USES 11 UNITS PER NAME] Infer the likely country and phone prefix, of up to 100 personal names, with a local context (ISO2 country of residence)./api2/json/phoneCodeGeoBatch
  • GET[CREDITS 1 UNIT] Feedback loop to better infer the likely phone prefix, given a personal name and formatted / unformatted phone number, with a local context (ISO2 country of residence)./api2/json/phoneCodeGeoFeedbackLoop/:firstName/:lastName/:phoneNumber/:phoneNumberE164/:countryIso2

chinese

  • GETIdentify Chinese name candidates, based on the romanized name ex. Wang Xiaoming/api2/json/chineseNameCandidates/:chineseSurnameLatin/:chineseGivenNameLatin
  • POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname), ex. Wang Xiaoming/api2/json/chineseNameCandidatesBatch
  • POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname) ex. Wang Xiaoming./api2/json/chineseNameCandidatesGenderBatch
  • GETIdentify Chinese name candidates, based on the romanized name ex. Wang Xiaoming - having a known gender ('male' or 'female')/api2/json/chineseNameGenderCandidates/:chineseSurnameLatin/:chineseGivenNameLatin/:knownGender
  • GETReturn a score for matching Chinese name ex. 王晓明 with a romanized name ex. Wang Xiaoming/api2/json/chineseNameMatch/:chineseSurnameLatin/:chineseGivenNameLatin/:chineseName
  • POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname), ex. Wang Xiaoming/api2/json/chineseNameMatchBatch
  • GETInfer the likely gender of a Chinese full name ex. 王晓明/api2/json/genderChineseName/:chineseName
  • POSTInfer the likely gender of up to 100 full names ex. 王晓明/api2/json/genderChineseNameBatch
  • GETInfer the likely gender of a Chinese name in LATIN (Pinyin)./api2/json/genderChineseNamePinyin/:chineseSurnameLatin/:chineseGivenNameLatin
  • POSTInfer the likely gender of up to 100 Chinese names in LATIN (Pinyin)./api2/json/genderChineseNamePinyinBatch
  • GETInfer the likely first/last name structure of a name, ex. 王晓明 -> 王(surname) 晓明(given name)/api2/json/parseChineseName/:chineseName
  • POSTInfer the likely first/last name structure of a name, ex. 王晓明 -> 王(surname) 晓明(given name)./api2/json/parseChineseNameBatch
  • GETRomanize the Chinese name to Pinyin, ex. 王晓明 -> Wang (surname) Xiaoming (given name)/api2/json/pinyinChineseName/:chineseName
  • POSTRomanize a list of Chinese name to Pinyin, ex. 王晓明 -> Wang (surname) Xiaoming (given name)./api2/json/pinyinChineseNameBatch

japanese

  • GETInfer the likely gender of a Japanese name in LATIN (Pinyin)./api2/json/genderJapaneseName/:japaneseSurname/:japaneseGivenName
  • POSTInfer the likely gender of up to 100 Japanese names in LATIN (Pinyin)./api2/json/genderJapaneseNameBatch
  • GETInfer the likely gender of a Japanese full name ex. 王晓明/api2/json/genderJapaneseNameFull/:japaneseName
  • POSTInfer the likely gender of up to 100 full names/api2/json/genderJapaneseNameFullBatch
  • POSTIdentify japanese name candidates in KANJI, based on the romanized name (firstName = japaneseGivenName; lastName=japaneseSurname) with KNOWN gender, ex. Yamamoto Sanae/api2/json/japaneseNameGenderKanjiCandidatesBatch
  • GETIdentify japanese name candidates in KANJI, based on the romanized name ex. Yamamoto Sanae/api2/json/japaneseNameKanjiCandidates/:japaneseSurnameLatin/:japaneseGivenNameLatin
  • GETIdentify japanese name candidates in KANJI, based on the romanized name ex. Yamamoto Sanae - and a known gender./api2/json/japaneseNameKanjiCandidates/:japaneseSurnameLatin/:japaneseGivenNameLatin/:knownGender
  • POSTIdentify japanese name candidates in KANJI, based on the romanized name (firstName = japaneseGivenName; lastName=japaneseSurname), ex. Yamamoto Sanae/api2/json/japaneseNameKanjiCandidatesBatch
  • GETRomanize japanese name, based on the name in Kanji./api2/json/japaneseNameLatinCandidates/:japaneseSurnameKanji/:japaneseGivenNameKanji
  • POSTRomanize japanese names, based on the name in KANJI/api2/json/japaneseNameLatinCandidatesBatch
  • GETReturn a score for matching Japanese name in KANJI ex. 山本 早苗 with a romanized name ex. Yamamoto Sanae/api2/json/japaneseNameMatch/:japaneseSurnameLatin/:japaneseGivenNameLatin/:japaneseName
  • POSTReturn a score for matching a list of Japanese names in KANJI ex. 山本 早苗 with romanized names ex. Yamamoto Sanae/api2/json/japaneseNameMatchBatch
  • GET[CREDITS 1 UNIT] Feedback loop to better perform matching Japanese name in KANJI ex. 山本 早苗 with a romanized name ex. Yamamoto Sanae/api2/json/japaneseNameMatchFeedbackLoop/:japaneseSurnameLatin/:japaneseGivenNameLatin/:japaneseName
  • GETInfer the likely first/last name structure of a name, ex. 山本 早苗 or Yamamoto Sanae/api2/json/parseJapaneseName/:japaneseName
  • POSTInfer the likely first/last name structure of a name, ex. 山本 早苗 or Yamamoto Sanae /api2/json/parseJapaneseNameBatch

indian

  • GET[USES 10 UNITS PER NAME] Infer the likely Indian name castegroup of a personal full name./api2/json/castegroupIndianFull/:subDivisionIso31662/:personalNameFull
  • POST[USES 10 UNITS PER NAME] Infer the likely Indian name castegroup of up to 100 personal full names. /api2/json/castegroupIndianFullBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely religion of a personal Indian full name, provided the Indian state or Union territory (NB/ this can be inferred using the subclassification endpoint)./api2/json/religionIndianFull/:subDivisionIso31662/:personalNameFull
  • POST[USES 10 UNITS PER NAME] Infer the likely religion of up to 100 personal full Indian names, provided the subclassification at State or Union territory level (NB/ can be inferred using the subclassification endpoint)./api2/json/religionIndianFullBatch
  • GET[USES 10 UNITS PER NAME] Infer the likely Indian state of Union territory according to ISO 3166-2:IN based on the name./api2/json/subclassificationIndian/:firstName/:lastName
  • POST[USES 10 UNITS PER NAME] Infer the likely Indian state of Union territory according to ISO 3166-2:IN based on a list of up to 100 names./api2/json/subclassificationIndianBatch

admin

  • GETActivate/deactivate anonymization for a source./api2/json/anonymize/:source/:anonymized/:token
  • GETRead API Key info./api2/json/apiKeyInfo
  • GETList of classification services and usage cost in Units per classification (default is 1=ONE Unit). Some API endpoints (ex. Corridor) combine multiple classifiers./api2/json/apiServices
  • GETPrints the current status of the classifiers. A classifier name in apiStatus corresponds to a service name in apiServices./api2/json/apiStatus
  • GETPrint current API usage./api2/json/apiUsage
  • GETPrint historical API usage./api2/json/apiUsageHistory
  • GETPrint historical API usage (in an aggregated view, by service, by day/hour/min)./api2/json/apiUsageHistoryAggregate
  • GETActivate/deactivate learning from a source./api2/json/learnable/:source/:learnable/:token
  • GETPrint basic source statistics./api2/json/regions
  • GETGet the current software version/api2/json/softwareVersion
  • GETPrint the taxonomy classes valid for the given classifier./api2/json/taxonomyClasses/:classifierName

general

  • GETInfer the likely type of a proper noun (personal name, brand name, place name etc.)/api2/json/nameType/:properNoun
  • POSTInfer the likely common type of up to 100 proper nouns (personal name, brand name, place name etc.)/api2/json/nameTypeBatch
  • GETInfer the likely type of a proper noun (personal name, brand name, place name etc.)/api2/json/nameTypeGeo/:properNoun/:countryIso2
  • POSTInfer the likely common type of up to 100 proper nouns (personal name, brand name, place name etc.)/api2/json/nameTypeGeoBatch

API details

Base URL
https://v2.namsor.com/NamSorAPIv2
Authentication
An API key in the X-API-KEY header
Operations
84 operations on 84 pathsGET 49POST 35
Main resources
personal 29japanese 15chinese 14admin 11indian 6social 5general 4
Response formats
application/json
Description format
OpenAPI 3.0.1, API version 2.0.24
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the NamSor API v2 in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the NamSor API v2 collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the X-API-KEY header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “[USES 20 UNITS PER NAME COUPLE] Infer several classifications for a cross border interaction between names (ex. remit, travel, intl com)” (GET /api2/json/corridor/:countryIso2From/:firstNameFrom/:lastNameFrom/:countryIso2To/:firstNameTo/:lastNameTo), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the NamSor API v2?

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… It is listed under AI & machine learning and has 84 endpoints.

Who publishes the NamSor API v2?

It is listed from Namsor's public API description (an OpenAPI document), not published by Namsor on Swastik Codes. Anyone who controls namsor.com can claim the profile by adding a DNS TXT record.

What is the base URL of the NamSor API v2?

Requests go to https://v2.namsor.com/NamSorAPIv2. Endpoint paths are added to this base URL.

How do I authenticate with the NamSor API v2?

With an API key in the X-API-KEY header.

How many endpoints does the NamSor API v2 have?

84 operations on 84 paths (49 GET, 35 POST). The largest groups are personal, japanese, chinese, admin.

Is forking the NamSor API v2 free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.