Loading Profile...
Add the following URLs to Soocial's API?
I already sent this to the support monkey, sorry for repeating myself but this seemed like a better place to post this, anyways.
Would it be possible to add the following URLs to Soocial's API?
contacts.vcf would return all the contacts in one large vCard file. contacts.txt (or maybe .csv) would return all the contacts, but only the first name, last name, and ID. So:
Would it be possible to add the following URLs to Soocial's API?
- /api/contacts.vcf
- /api/contacts.txt
- /api/contacts/ID.vcf
contacts.vcf would return all the contacts in one large vCard file. contacts.txt (or maybe .csv) would return all the contacts, but only the first name, last name, and ID. So:
and contacts/ID.vcf would return that contact as a vcard. This would also be a PUT-capable spot, allowing the developer/client app to HTTP PUT a vcard and have it overwrite that one contact. (I thought about having contacts.vcf a put-capable url, and it makes it easy for someone to screw up if that means overwriting the user's whole contact list.) The vcard retrivial shouldn't take a long time as you already give the vcard in the XML returned from the API, so I don't think it would be too long for it to be implemented, but the PUT side may take a bit longer. Oh well :)
1002,Smith,John
1003,Doe,Jane
etc
I’m confident that these ideas will help future Soocial client developers
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
The best point from the company
-
Hi Colin,
Thanks for the idea and my apologies for this somewhat late reply.
GET /contacts.vcf and GET /contacts/<id>.vcf are already available via the API, just do a call to .vcf instead of .xml and you should get your vcards.
This isn't documented in the API documentation if i recall correctly, I'll update that asap.
The PUT's are an interesting idea that I'll look into, I'm not sure what the direct implications of enable that would be so I'm not promising anything on that yet.
I'm not very fond of the .csv idea, but I might change my mind if you can give a scenario where that would prove useful.
cheers and keep your ideas coming!
Simon
</id>
I’m happy with smart cookies
The company and 1 other person think
this is one of the best points
-
Inappropriate?Hi Colin,
Thanks for the idea and my apologies for this somewhat late reply.
GET /contacts.vcf and GET /contacts/<id>.vcf are already available via the API, just do a call to .vcf instead of .xml and you should get your vcards.
This isn't documented in the API documentation if i recall correctly, I'll update that asap.
The PUT's are an interesting idea that I'll look into, I'm not sure what the direct implications of enable that would be so I'm not promising anything on that yet.
I'm not very fond of the .csv idea, but I might change my mind if you can give a scenario where that would prove useful.
cheers and keep your ideas coming!
Simon
</id>
I’m happy with smart cookies
The company and 1 other person think
this is one of the best points
1 Comment Add a comment
This is one of the best points
-
The CSV idea was put up for just a quick grab of names (i.e. for a rapid gui to get the names and load the rest of the information as the user requests it). The PUT idea is a bit more dangerous, and will need figuring out. Otherwise I may just have to write a .vcf -> Soocial XML Contact (not hard, just something more to do).
EMPLOYEE
