web api - delete, revoke, deactivate user's activation

Hey Alex,

Sure, we should have them written by Wednesday morning.

Hey Alex,

We've added the functions:

1. limelm.pkey.deactivate
2. limelm.pkey.delete
3. limelm.pkey.revoke

Wyatt,

Thank you.You are great!

Alex

Hi Wyatt

Any opportunity of logging the time and date a REVOKE command is initiated ? It would be useful to have this information populated on the web api.. In direct comparison to when Activated..

This is coming with the new "activity" api (in a couple of days).

Thanks Wyatt

Another API request, certain customers request a Monthly list of Product Keys and Activation Features provided for their information / records.

Would it be possible to not only Export the List of Product Keys into a *.csv file, but also include the email address information field , Feature Field, Time & Date activated, Time & Date Revoked associated with the product key ?

Many Thanks

Hey Steve,

The limelm.pkey.getDetails api already gets all the information for a product key. You can use that function in tandem with limelm.pkey.find to get all the product key details for a particular email address.

We have been considering providing the ability for end users to create their own LimeLM account -- where they can enter their purchase product key and get all the details for their key(s). Would something like this work for you?

There are certain ISV's who have reseller accounts. These resellers would like a monthly copy of up to date customer activations. From an online limeLM administrator perspective I was just suggesting That the existing "Export Product Keys" function could Export all of the Product Keys (not filtered) including additional info (as suggested in previous post) into a .csv file. This .csv file could then be used to extract associated resellers activations etc. Just a thought

With regard to a Lime LM account for end user customers? I think this could work if the LimeLM administrator interface had control to turn on or turn off the customers account. The obvious problem would be that the customer would see a LimeLM Branded api. Are you considering allowing Branding of api?

From an online limeLM administrator perspective I was just suggesting That the existing "Export Product Keys" function could Export all of the Product Keys (not filtered) including additional info

Ok, we'll work on that.

Are you considering allowing Branding of api?

Yes. But I was just throwing out an idea. We're trying to solve the "licensing problem" for both software developers and the end-user. Giving the end-user a way to view and manager their product keys would be an extra advantage for some types of customers (medium & large corporations).

We're still playing with ideas, though. Nothing is in stone, so to speak.