Does anybody know whether it is possible use the Flickr's API to register a new account? We would like to use our website to allow user to register with us and Flickr at the same time.
I don't see anything applicable in the list of methods at http://www.flickr.com/services/api/. All of the calls in the flickr.people.* category are finds and gets.
Related
First of all, I apologize for eventual noob questions, we are very new to the DocuSign API and are currently trying to wrap our heads around which is the most correct way of accessing the API.
I will start with an overview of our use case. We recently purchased a DocuSign prod. Account with an Organization enabled.
We have a Partner which uses a CMS Tooling which integrates with said DocuSign Account. This Tool allows for the Backoffice to create envelopes with documents inside and a url which leads to the signin ceremony through the Templates that we create inside the DocuSign Account. This url is afterwards send to the customer for them to sign the documents in the envelope. This Part is working and is currently being used.
Now what we want to achieve on our side, we have a nextJS web-app which allows the same customers (Which are the receivers of the created envelopes in the step above, same e-mail in both steps) to sign-in our web-app. We want to show the customer in a dashboard, if there are envelopes for him open that he can sign and if this is the case we want to show him the url which leads to the signin ceremony.
We were able to see that as soon as an envelope for a certain User is created through the CMS Tooling, we can see that envelope in our DocuSign Prod Account.
Now our thought process was, to show our customer his open envelopes, we just fetch all open envelopes in our DocuSign Account which match the customers E-Mail.
Is there anything wrong with this process or are we overlooking something?
And if it is okay to proceed this way which of the OAuth Flows is the correct one to use for this case?
From my understanding, the JWT Flow seems like the most reasonable one? Since the Customers that need to sign the documents, will not have any DocuSign accounts.
What have you tried to solve the issue?
We tried using the direct API Access, which worked when set up correctly but since we didn't have a OAuth Flow in place the Access token is only valid for restricted amount of time obviously and has to be refreshed. Hence we have to think first about how to grant access correctly
I would love to hear, what the right approach would be to achieve our desired result.
Once again Apologies for this kind of question, just trying to have a better understanding before we start building :)
Best regards!
According to the use case you mentioned using JWT Grant is fine as users of your integration will use a single system account to log in, you should use JWT Grant.
I would recommend going with the below link to know more regards different use cases and check the knowledge
https://developers.docusign.com/platform/auth/choose/
https://developers.docusign.com/platform/auth/oauth2-requirements-migration/
I am successful of fetching my own data using Instagram Graph Api but unable to find a way to get other person's data.
Official document clearly state that metadata of basic data for other Instagram businesses and creators are obtainable but not been able to find any code or document about it.
If anybody know how to do it I would love to know.
Even providing me a link to document or web page that have said information is hugely appriciated.
official document
https://developers.facebook.com/docs/instagram-api
This is described in the Business Discovery documentation. See also the API reference.
The tricky part is that you need to provide your account ID in the URL. (Basically, your account's node is used to access the business_discovery edge.)
You provide the target account's username in the field parameter, for example:
https://graph.facebook.com/v3.2/YOUR_ACCOUNT_ID?fields=business_discovery.username(bluebottle){followers_count,media_count}&access_token={access-token}
Where bluebottle is the username of the account you want data for.
Mind that this really works with business and creators accounts, so you won't obtain data for any random account this way.
I am trying to create a functionality using the Stripe API (not Stripe Connect) to let users add customers. If I understand this correctly, all customers will be added to my Stripe account. Is there a way I can distinguish which user added which customer, so that I can list all customers under one specific user?
I know Stripe Connect solves this problem, but it's not appropriate for my use case.
Thanks in advance.
About the only way you'll be able to do this - beyond tracking it in your own application's database, which you should definitely do - is to add Metadata to the Customers.
That said, you may want to reach out to Support and have them confirm that your use case makes sense; they may also have an alternative suggestion for you.
As #floatingLomas said, you can use the metadata field to store user info when creating a new customer (https://stripe.com/docs/api/customers/create), but as far as I know there's no specific API call to retrieve customers by metadata.
I mean, if your concern is to know who created a specific customer, it will be enough to retrieve that specific customer and look at its metadata field, but if you're looking for a solution which allow you to find all the customers added by a specific user, then I would suggest to create in your app a database table which keep track of that and do your searches through that.
I'm working on testing our application and have the need to simulate signing of a document via the API. These aren't real documents I just need to be able to set the signing the order in a specific order but I don't receive emails for recipients until the previous one has signed. So is it possible to use the DocuSign API to sign a "Sign Here" tab? Or do I have any other options?
I haven't been able to find any clear information on this topic although I fear the answer is not. Looking through DocuSign's REST API there's a couple of endpoints that suggests I might be able to do this but I'm not quite sure it's referencing what I'm looking to do. The following endpoint has a GET and PUT function but not sure it's what I want.
{{baseUrl}}/envelopes/{{envelopeId}}/recipients/{{recipientId}}/signature_image
No, the DocuSign API does not have a functionality for 'robo-signing'.
If the goal is to check routing order, you could change a Signer to a Carbon Copy recipient: CC roles are immediately completed.
For reference, the signature_image API calls allow you to view or change a user's adopted signatures. They shouldn't be used to apply a signature to a document.
So here is what i am trying to do :
I built a bot with api.ai for my business that is hosted on my webpage and my Facebook page right now. Bot works well.
I want to push it to the next step by allowing my customers to make querys on my calendar, ask to book a specific time, see if available, if not offer other time similar, then make a booking.
I have been reading this thread and the great answer attached to it but i think my case is a bit different.
I was wondering if the bot could always have a token so every guests won't have to Auth to query the calendar ?
Obviously i am new to this, i have been reading the guide of google calendar api and api.ai but i don't really see how to do that yet. I guess there is a way to store a token somewhere and then just trigger the query with some specific intents but not to sure how.
I have also done the node.js quickstart guide of the G-calendar api, and it works fine if that helps.
Thanks for your help !
You will probably want to use a Service Account that is permitted to the calendar in question. Service Accounts are similar to regular accounts, but they are expected to do server-to-server communication only, so the method to create an auth token is a little different to keep it secure.
See https://developers.google.com/identity/protocols/OAuth2ServiceAccount for more information about using Service Accounts.
In general, you'll be using a shared secret to create and sign a JSON Web Token (JWT) you send to Google's servers. You'll get back an access token which you'll then use to call the Calendar API. The access token expires in about an hour, at which point you'll need to repeat the process.
There are libraries available to do much of this for you. For example, if you're using the node.js library https://github.com/google/google-api-nodejs-client, then it will take care of this for you (although you need to modify the key file - see the documentation for details).