Caller ID Made Simple

Randall,<p>This looks remarkably easy to use. Just a small tip: On opencname's home page, you suggest users try the following API call:<p><pre><code> $ curl https://api.opencnam.com/v1/phone/2024561111 US GOVERNMENT </code></pre> I tried it and received a different result:<p><pre><code> $ curl https://api.opencnam.com/v1/phone/2024561111 DIST OF COLUMBI </code></pre> Perhaps you should update your home page to reflect this?

This is the first API that I've encountered that works with cellphone numbers. I can see this being integrated into Android for incoming calls from unknown cellphone numbers.

I would ONLY be willing to use this if it returned better data than Twilio's CNAM lookups (costs $0.01) for a cheaper overall price.<p>So far, I've tested my number, and a few others, that I know have CNAM data that this service only provides a STATE for. Hopefully it will get better but it's not there yet for me.

I tried 6 numbers of friends and only one returned a result. Are many numbers not callerid-able, or is the api just bogged down?

This is awesome! I had a couple of free hours, so I hacked together a little Ruby app that validates a telephone number and full name pair. This could be used for sign-up security, etc. You can find the repo here: <a href="https://github.com/EricR/sinatra-cnam-lookup" rel="nofollow">https://github.com/EricR/sinatra-cnam-lookup</a>

For what it's worth, and for all those asking questions about Canadian numbers, caller id name is handled differently in Canada than in the states. When a carrier sends an outgoing call, they include the caller id name in the SS7 IAM (Initial Message), unlike the states where the receiving carrier has to do a database lookup on the number to retrieve the name. This likely explains why a lot of Canadian numbers are not returning any results, or incorrect results.<p>Personally, I think the Canadian system of including the name in the IAM works a lot better than having to do a DB lookup.

I wonder if the providers of this service have thought about crowd-sourcing the caller-id information, like <a href="http://mrnumber.com/" rel="nofollow">http://mrnumber.com/</a> whose free tier harvests number-&#62;name mapping from users address books...

I definitely find it interesting.<p>As somehow it pulls up my (not) apparently unlisted home phone; also, it pulls up family members names for cellphones which are under my name on the contract.<p>So I am definitely interested in finding out where this data is being taken from?

This may be common knowledge but in the browser address bar do <a href="https://api.opencnam.com/v1/phone/2024561111?format=text" rel="nofollow">https://api.opencnam.com/v1/phone/2024561111?format=text</a>

I've wondered why twilio doesn't have this feature. Good stuff!

This is cool, but fix the double request thing if you're going to have a free version...

It seems odd that it only returns a province/state when just the area code provides more information than that. Example: any (647) or (416) area code will always be from Toronto, but numbers for both just return ONTARIO.

Please make it more obvious that this only works for US phone numbers

NANPA (US+Canada) only :(

It just says "wireless caller" for my number. Does it usually provide more information? I don't know how useful this is otherwise.

The drawing - is that Goemon from Rupan/Lupin series by any chance?