Accounting and updates

[Bert Sinnema]

First off, i was wondering if singly can post updates to services. I can't find it in the docs.

Second, i don't understand the accounting fully.  When requesting the access_token i get a access_token and a account value. Where is this for? 

I think and hope that the account value has to do with the browser session and therefore we can asume it is the same user who wants to connect another service to his/her account? But the downside is that i don't see a session that i can kill so when a second person wants to login to my website simply gets added to the wrong account. I noticed you can pass an account value. can this also be an automatic generated value?

Cheers!

[Justin Parker]

Hey Bert,

Currently, posting updates is done through the proxy for each individual service. See the documentation at https://singly.com/proxy. In this way you are using the service's own interface to post updates, but we manage all of the access tokens.

We are working on a much better way of doing this that will allow more flexibility and ease of use in posting to multiple services, which should be available in a matter of weeks!

The "account value" comes from the original service that the user is authenticating with, so it can't be changed. You can use it mostly to delete individual services from the list of accounts Singly is managing.

The Singly access token is what you should associate with the user's account or session. The Singly access token will be constant no matter what services the user has authenticated. You can then use the /profiles endpoint to see what those services are.

Please ask any other questions you have. Our documentation is in its evolutionary phases, so all feedback is great helping us determine what is confusing!

Thanks,

Justin

[Justin Parker]

Sorry, I want to clarify one thing that I misstated:

The access token is normally constant, but it is possible for it to eventually be invalidated or change. The correct token to store is the Singly ID that is returned in the authentication process, and can also be retrieved as the id in the /profiles endpoint.

Justin

[Bert Sinnema]

Awesome. i am getting the hang of Singly now thanks to you and Kristján on Github. I am developping MicroCV on Symfony2 with the DoctrineMongoBundle

I am creating a SinglyService and some ProxyServices for Singly integration on Symfony2. i'll make sure i will share them with your team. this might be helpful for the Symfony2 community.

Cheers!

[Kristján Pétursson]

Hooray for libraries! Definitely send over links to anything you put out and we'll point people over to them. If you end up with a simple demo application, I'd love to use it as a base for a PHP Getting Started guide like we have for Ruby, Node and iOS: https://singly.com/getting_started_ruby

--
You received this message because you are subscribed to the Google Groups "Singly API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/singlyapi/-/BgViRUzBTYQJ.

To post to this group, send email to sing...@googlegroups.com.
To unsubscribe from this group, send email to singlyapi+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singlyapi?hl=en.

[Kristján Pétursson]

Thought I'd come back and update this thread - sharing back to the original services now works (experimental) for simple status messages. Check out https://singly.com/docs/sharing and tell us what you think!