Open Cellular Usage API

Forums › IT Pro and developers › Open Cellular Usage API

codyc1515

1598 posts

Uber Geek
Inactive user

# 93482 22-Nov-2011 16:18

Hi all,

I have spent the most part of today developing what I have called the "Open Cellular Usage API". It allows you to see in json and xml:

Prepaid Balance/Money Owing
Phone Number (when using a username to sign in)
Voice minutes left, allocated and expiry dates
Texts left, allocated and expiry dates
Data in MB left, allocated and expiry dates

This could come in handy for developing, say, a My Telecom app that somebody wanted in a different thread. More information on how to use the API is available here: http://www.codycooper.co.nz/usage-api/

Cheers,
Cody

Zeon

3496 posts

Uber Geek

Trusted

# 548527 22-Nov-2011 16:22

Very cool, well done! Too bad the providers themselves don't have APIs....

Speedtest 2019-10-14

freitasm

BDFL - Memuneh
64656 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 548530 22-Nov-2011 16:27

Interesting idea, and good one for creating it. However, people would need a lot of "trust" to use that, seeing they have to send their passwords to an app and that will in turn pass it on to your site.

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

shadou

30 posts

Geek

# 548535 22-Nov-2011 16:43

Not much of an API without the codez. Super concerned about what you are doing with logins/passwords.

If you had a version of this available that I could run locally *I* might actually test it. Good luck with your scam! =(

johnr

19282 posts

Uber Geek
Inactive user

# 548538 22-Nov-2011 16:50

shadou: Not much of an API without the codez. Super concerned about what you are doing with logins/passwords.

If you had a version of this available that I could run locally *I* might actually test it. Good luck with your scam! =(

I don't believe Codyc is doing this to scam anyone,

freitasm

BDFL - Memuneh
64656 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 548540 22-Nov-2011 16:52

I wouldn't say scam, but seeing how Cody has previously been so worried about people collecting information on the Internet, making a service like this available without proper privacy policy in place and full source code disclouse is a bit out of the norm.

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

possum888

22 posts

Geek

# 548543 22-Nov-2011 16:54

Here's a couple of things I'd suggest:

SSL encryption: I don't think many people would be happy sending their passwords over a plaintext connection. Even though it's only your mobile usage, it's still a password and needs to be protected.
Legality: make sure you have permission to 'screen scrape' the providers websites.
Privacy Policy: write one of these up so people know if and/or how you are storing their data. How do I know that you aren't storing my mobile number and password in a database?

Other than those points I think it's a really great idea!

codyc1515

1598 posts

Uber Geek
Inactive user

# 548561 22-Nov-2011 17:32

possum888: Here's a couple of things I'd suggest:
SSL encryption: I don't think many people would be happy sending their passwords over a plaintext connection. Even though it's only your mobile usage, it's still a password and needs to be protected.
Legality: make sure you have permission to 'screen scrape' the providers websites.
Privacy Policy: write one of these up so people know if and/or how you are storing their data. How do I know that you aren't storing my mobile number and password in a database?
Other than those points I think it's a really great idea!

SSL encryption: This is not possible on the current, personal server that I am using but is a possibility in the future. Security was one of the things that I thought about when making it, I think what I will probably do is allow people to send a shared key with the query and encrypt the details using a secret key and aes encryption.
Legality: Who might I contact to get permission to do this? johnr?
Privacy Policy: I am not storing data, except standardized logs (like any other server, containing IP, etc.). I am not storing your details in a database.

codyc1515

1598 posts

Uber Geek
Inactive user

# 548610 22-Nov-2011 18:59

codyc1515:
possum888: Here's a couple of things I'd suggest:
SSL encryption: I don't think many people would be happy sending their passwords over a plaintext connection. Even though it's only your mobile usage, it's still a password and needs to be protected.
Legality: make sure you have permission to 'screen scrape' the providers websites.
Privacy Policy: write one of these up so people know if and/or how you are storing their data. How do I know that you aren't storing my mobile number and password in a database?
Other than those points I think it's a really great idea!

SSL encryption: This is not possible on the current, personal server that I am using but is a possibility in the future. Security was one of the things that I thought about when making it, I think what I will probably do is allow people to send a shared key with the query and encrypt the details using a secret key and aes encryption.
Legality: Who might I contact to get permission to do this? johnr?
Privacy Policy: I am not storing data, except standardized logs (like any other server, containing IP, etc.). I am not storing your details in a database.

I've since clarified all of the data usage with a simple Privacy Policy. I have also added in some instructions for encrypting the transmission of data.

codyc1515

1598 posts

Uber Geek
Inactive user

# 552312 1-Dec-2011 16:09

I have since pushed over all of the latest changes:

It is now available for download from: http://code.google.com/p/open-cellular-usage-api/
It is licensed under the 2-clause BSD license ("Simplified BSD License" or "FreeBSD License")
It now has a read me file explaining how the various files work
It also includes example pages that are returned from the carriers once the API has been authenticated for:

Vodafone NZ

PrePaid
Contract

Telecom NZ

PrePaid
Contract (Don't have one to test on, so may not work correctly)

2degrees (Don't have one to test on, so does not work)

PrePaid
Contract

Hopefully all of this should speed up adoption of the project and resolves the whole "trust" issue.