Print historical API usage 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.
What this operation does
Print historical API usage.
- GETReads data · admin
v2.namsor.com/api2/json/apiUsageHistory
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which NamSor operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other NamSor operations
- Return a score for matching a list of Japanese names in KANJI exPOST · changes data
- Romanize a list of Chinese name to Pinyin, exPOST · changes data
- [USES 10 UNITS PER NAME] Infer the likely origin of a list of upPOST · changes data
- [USES 10 UNITS PER NAME] Infer the likely Indian state of UnionPOST · changes data
- Infer the likely gender of up to 100 namesPOST · changes data
- [USES 10 UNITS PER NAME] Infer the likely country of origin of upPOST · changes data
- [USES 10 UNITS PER NAME] Infer the likely country of residence ofPOST · changes data
- [USES 20 UNITS PER NAME PAIR] Infer several classificationsPOST · changes data
Questions
- Can HumDay print historical api usage 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.