Automate NamSor

What NamSor is

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

API host: v2.namsor.com

What HumDay can do in NamSor

35 documented operations change something in NamSor.

• POSTReturn a score for matching a list of Japanese names in KANJI ex./api2/json/japaneseNameMatchBatch
• POSTRomanize a list of Chinese name to Pinyin, ex./api2/json/pinyinChineseNameBatch
• 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)./api2/json/subclassificationBatch
• 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
• POSTInfer the likely gender of up to 100 names, detecting automatically the cultural context./api2/json/genderBatch
• 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
• POST[USES 10 UNITS PER NAME] Infer the likely country of residence of up to 100 personal full names, or surnames./api2/json/countryBatch
• POST[USES 20 UNITS PER NAME PAIR] Infer several classifications for up to 100 cross border interaction between names (ex./api2/json/corridorBatch
• 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./api2/json/diasporaBatch
• POSTInfer the likely common type of up to 100 proper nouns (personal name, brand name, place name etc.)/api2/json/nameTypeBatch
• POSTInfer the likely gender of up to 100 names, each given a local context (ISO2 country code)./api2/json/genderGeoBatch
• POSTInfer the likely first/last name structure of a name, ex./api2/json/parseNameBatch
• 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…/api2/json/phoneCodeBatch
• POSTInfer the likely gender of up to 100 full names, detecting automatically the cultural context./api2/json/genderFullBatch
• POSTInfer the likely common type of up to 100 proper nouns (personal name, brand name, place name etc.)/api2/json/nameTypeGeoBatch
• POSTInfer the likely first/last name structure of a name, ex./api2/json/parseNameGeoBatch
• 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
• POST[USES 10 UNITS PER NAME] Infer the likely religion of up to 100 personal full names./api2/json/religionFullBatch
• POSTInfer the likely gender of up to 100 full names, with a given cultural context (country ISO2 code)./api2/json/genderFullGeoBatch
• POST[USES 10 UNITS PER NAME] Infer up-to 100 US resident's likely race/ethnicity according to US Census taxonomy./api2/json/usRaceEthnicityBatch
• POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname), ex./api2/json/chineseNameMatchBatch
• POSTInfer the likely first/last name structure of a name, ex./api2/json/parseChineseNameBatch
• POSTInfer the likely gender of up to 100 full names ex./api2/json/genderChineseNameBatch
• POSTInfer the likely first/last name structure of a name, ex./api2/json/parseJapaneseNameBatch
• POSTInfer the likely gender of up to 100 Japanese names in LATIN (Pinyin)./api2/json/genderJapaneseNameBatch
• 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 u…/api2/json/religionIndianFullBatch
• 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./api2/json/usZipRaceEthnicityBatch
• POST[USES 10 UNITS PER NAME] Infer the likely Indian name castegroup of up to 100 personal full names./api2/json/castegroupIndianFullBatch
• POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname), ex./api2/json/chineseNameCandidatesBatch
• POSTInfer the likely gender of up to 100 full names/api2/json/genderJapaneseNameFullBatch
• POSTInfer the likely gender of up to 100 Chinese names in LATIN (Pinyin)./api2/json/genderChineseNamePinyinBatch
• POSTIdentify Chinese name candidates, based on the romanized name (firstName = chineseGivenName; lastName=chineseSurname) ex./api2/json/chineseNameCandidatesGenderBatch
• POSTIdentify japanese name candidates in KANJI, based on the romanized name (firstName = japaneseGivenName; lastName=japaneseSurname), ex./api2/json/japaneseNameKanjiCandidatesBatch
• POSTRomanize japanese names, based on the name in KANJI/api2/json/japaneseNameLatinCandidatesBatch
• POSTIdentify japanese name candidates in KANJI, based on the romanized name (firstName = japaneseGivenName; lastName=japaneseSurname) with KNOWN gender, ex./api2/json/japaneseNameGenderKanjiCandidatesBatch

What HumDay can read from NamSor

These are the operations a schedule or a trigger can watch.

• GETInfer the likely gender of a just a fiven name, assuming default 'US' local context./api2/json/gender/{firstName}
• GETInfer the likely first/last name structure of a name, ex./api2/json/parseName/{nameFull}
• GETInfer the likely gender of a full name, ex./api2/json/genderFull/{fullName}
• GETInfer the likely type of a proper noun (personal name, brand name, place name etc.)/api2/json/nameType/{properNoun}
• GET[USES 10 UNITS PER NAME] Infer the likely country of residence of a personal full name, or one surname./api2/json/country/{personalNameFull}
• GETInfer the likely first/last name structure of a name, ex./api2/json/parseChineseName/{chineseName}
• GETInfer the likely gender of a Chinese full name ex./api2/json/genderChineseName/{chineseName}
• GETRomanize the Chinese name to Pinyin, ex./api2/json/pinyinChineseName/{chineseName}
• GETInfer the likely first/last name structure of a name, ex./api2/json/parseJapaneseName/{japaneseName}
• GETInfer the likely gender of a Japanese full name ex./api2/json/genderJapaneseNameFull/{japaneseName}
• GETInfer the likely gender of a name./api2/json/gender/{firstName}/{lastName}
• GET[USES 10 UNITS PER NAME] Infer the likely country of origin of a personal name./api2/json/origin/{firstName}/{lastName}
• GETInfer the likely first/last name structure of a name, ex./api2/json/parseName/{nameFull}/{countryIso2}
• GETInfer the likely gender of a full name, given a local context (ISO2 country code)./api2/json/genderFullGeo/{fullName}/{countryIso2}
• GETInfer the likely type of a proper noun (personal name, brand name, place name etc.)/api2/json/nameTypeGeo/{properNoun}/{countryIso2}
• GET[USES 10 UNITS PER NAME] Infer a US resident's likely race/ethnicity according to US Census taxonomy WNL (white, non latino), HL (hispano latino), A (asian, non latino), BNL (blac…/api2/json/usRaceEthnicity/{firstName}/{lastName}
• 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}
• GETInfer the likely gender of a Japanese name in LATIN (Pinyin)./api2/json/genderJapaneseName/{japaneseSurname}/{japaneseGivenName}
• 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 subclassificati…/api2/json/religionIndianFull/{subDivisionIso31662}/{personalNameFull}
• GET[USES 10 UNITS PER NAME] Infer the likely Indian name castegroup of a personal full name./api2/json/castegroupIndianFull/{subDivisionIso31662}/{personalNameFull}
• GETIdentify Chinese name candidates, based on the romanized name ex./api2/json/chineseNameCandidates/{chineseSurnameLatin}/{chineseGivenNameLatin}
• GETInfer the likely gender of a Chinese name in LATIN (Pinyin)./api2/json/genderChineseNamePinyin/{chineseSurnameLatin}/{chineseGivenNameLatin}
• GETIdentify japanese name candidates in KANJI, based on the romanized name ex./api2/json/japaneseNameKanjiCandidates/{japaneseSurnameLatin}/{japaneseGivenNameLatin}
• GETRomanize japanese name, based on the name in Kanji./api2/json/japaneseNameLatinCandidates/{japaneseSurnameKanji}/{japaneseGivenNameKanji}
• GET[USES 20 UNITS PER NAME] Infer the likely ethnicity/diaspora of a personal name, given a country of residence ISO2 code (ex./api2/json/diaspora/{countryIso2}/{firstName}/{lastName}
• GETInfer the likely gender of a name, given a local context (ISO2 country code)./api2/json/genderGeo/{firstName}/{lastName}/{countryIso2}
• 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}
• GET[USES 10 UNITS PER NAME] Infer a US resident's likely race/ethnicity according to US Census taxonomy, using (optional) ZIP5 code info./api2/json/usRaceEthnicityZIP5/{firstName}/{lastName}/{zip5Code}
• GET[USES 10 UNITS PER NAME] Infer the likely origin of a name at a country subclassification level (state or regeion)./api2/json/subclassification/{countryIso2}/{firstName}/{lastName}
• GET[USES 10 UNITS PER NAME] Infer the likely religion of a personal full name./api2/json/religionFull/{countryIso2}/{subDivisionIso31662}/{personalNameFull}
• GETList of classification services and usage cost in Units per classification (default is 1=ONE Unit)./api2/json/apiServices
• GETReturn a score for matching Chinese name ex./api2/json/chineseNameMatch/{chineseSurnameLatin}/{chineseGivenNameLatin}/{chineseName}
• GETReturn a score for matching Japanese name in KANJI ex./api2/json/japaneseNameMatch/{japaneseSurnameLatin}/{japaneseGivenNameLatin}/{japaneseName}
• GETIdentify Chinese name candidates, based on the romanized name ex./api2/json/chineseNameGenderCandidates/{chineseSurnameLatin}/{chineseGivenNameLatin}/{knownGender}
• GETIdentify japanese name candidates in KANJI, based on the romanized name ex./api2/json/japaneseNameKanjiCandidates/{japaneseSurnameLatin}/{japaneseGivenNameLatin}/{knownGender}
• GET[CREDITS 1 UNIT] Feedback loop to better perform matching Japanese name in KANJI ex./api2/json/japaneseNameMatchFeedbackLoop/{japaneseSurnameLatin}/{japaneseGivenNameLatin}/{japaneseName}
• 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}
• GETPrint basic source statistics./api2/json/regions
• GETPrint current API usage./api2/json/apiUsage
• GETPrints the current status of the classifiers./api2/json/apiStatus
• GETRead API Key info./api2/json/apiKeyInfo
• GETPrint historical API usage./api2/json/apiUsageHistory
• GETGet the current software version/api2/json/softwareVersion
• GETPrint historical API usage (in an aggregated view, by service, by day/hour/min)./api2/json/apiUsageHistoryAggregate
• 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 resid…/api2/json/phoneCodeGeoFeedbackLoop/{firstName}/{lastName}/{phoneNumber}/{phoneNumberE164}/{countryIso2}
• GETPrint the taxonomy classes valid for the given classifier./api2/json/taxonomyClasses/{classifierName}
• GET[USES 20 UNITS PER NAME COUPLE] Infer several classifications for a cross border interaction between names (ex./api2/json/corridor/{countryIso2From}/{firstNameFrom}/{lastNameFrom}/{countryIso2To}/{firstNameTo}/{lastNameTo}
• GETActivate/deactivate learning from a source./api2/json/learnable/{source}/{learnable}/{token}
• GETActivate/deactivate anonymization for a source./api2/json/anonymize/{source}/{anonymized}/{token}

How automating NamSor works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live NamSor account.
4. Grant access, then go live. You approve the specific NamSor operations it may use — and only those.

Automate NamSor with these

• OpenAI273 operations
• MotaWord219 operations
• Anthropic144 operations
• Contract P Contract.fit134 operations
• Salesforce Einstein Vision and Einstein Language45 operations
• Semantria41 operations
• FunTranslations36 operations
• Formapi35 operations
• Handwrytten30 operations
• Neutrinoapi Neutrino27 operations
• Oxforddictionaries Oxford Dictionaries26 operations
• Cloudmersive ocrapi18 operations

Categories

• Text and language

Questions about NamSor automation

Can HumDay connect to NamSor?

Yes. HumDay reads NamSor's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 84 operations are documented.

Do I need to write code to automate NamSor?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your NamSor account.

What can HumDay do in NamSor?

35 of the 84 documented operations change something in NamSor, and 49 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my NamSor account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to NamSor is held behind that approval.

Where this came from

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