We Have a Document Management System(DMS) which is .Net WebAPI Used to share Documents Between our employees,and stores the documents in our DB Can we implemet the workflows
1)
A authorised admin uploads a document into the API with names and Emails of signers and send it to them for signing and get the signed document and store it in our DB
through docusign
You can create a DocuSign envelope using the DocuSign eSignature API where you can specify signers ("recipients"), documents and fields ("tabs") that recipients need to take action on in those documents.
This is the API reference for the API call to create an envelope: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/
This is an example How-To guide for a simple signature request using the various SDKs (including C#):
https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-email-remote/
You are able to download documents from DocuSign through the API as well: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocuments/get/
This is an example How-To guide for downloading envelope documents using the SDKs: https://developers.docusign.com/docs/esign-rest-api/how-to/download-envelope-documents/
You can download the Quickstart example project in a language of your preference, which includes those How-To examples if you wanted to test it out: https://developers.docusign.com/docs/esign-rest-api/quickstart/
Or you can check out the Sample Apps here to see some example use cases: https://developers.docusign.com/sample-apps/
There are generally a few more concepts/terminology to be familiar with when working with the DocuSign APIs (such as how to authenticate). You can check out this page which has links to some of these general topics: https://developers.docusign.com/platform/
Related
I have added a non-renewable subscription for one of my projects. We also started implementing the Google play developer API to get the subscription latest status from the Play Store. For that we have done the below steps as per this blog:
Linked the developer account to a new Google Cloud Project.
Enabled the Google Play Developer API for the Google Cloud Project.
Created a service account and created a key for the service account.
I have below clarifications related to this implementation:
I tried to Grant Access for the following permissions: But the corresponding checkmark is not clickable.
View financial data, orders, and cancellation survey responses
Manage orders and subscriptions
The 3rd step as per the blog is to Authorize an API key, but I didn't get a clear idea of that.
We are going to implement this API on the back end side as a corn job, do we need to generate a JWT token for accessing this API? Is this possible to call without a Token? I found 2 types of implementations from this blog, which one is easy and secure?
"Your application can complete these tasks either by using the Google APIs client library for your language or by directly interacting with the OAuth 2.0 system using HTTP."
From where we get the get API path and other details. I found a similar get API from AppStore like this. Is the play store providing a similar kind of get API?
We need the latest purchase status API and for that what parameters do we need to pass?
I can't figure out what public data means in Google Docs API guides.
Reading the Google Docs API guide authorizing section, we find that for public data the OAuth 2.0 is not necessary, then I tried using patchupdate to update a document which is shared to edit for anyone with the link, and I could not get it to work because the API returns an authentication error.
So the questions are, what is API key for and what does Google mean with public data?
I understand that you refer to the «If the request doesn't require authorization (such as a request for public data), then the application must provide either the API key or an OAuth 2.0 token, or both» part. It says that you should use either an API key or an OAuth 2.0 token (or both), whatever is more convenient for your project. In this guide you can learn more about how to communicate with Google APIs using OAuth 2.0. Meanwhile in this documentation you can see the approach used with API keys. Please don't hesitate to ask me to clarify myself.
I am confused about the features, functionality, and boundaries of a Google API project. A single Google API project can have many credentials.
If your apps will all be using the same APIs, why would you want to create separate projects?
When or under what conditions should you create additional credentials fo the same project?
Base on Google Doc: Before you can send requests to Google Apps Activity API, you need to tell Google about your client and activate access to the API. You do this by using the Google Developers Console to create a project, which is a named collection of settings and API access information.
As above, Each API project is a named collection of settings and API access information. You can read this
In working with the .NET client library we found that the Email Settings API was not available in it or any of the other client libraries. After communicating with the developers of the .NET library on how the library is generated we noticed that the Email Settings API is not listed in the API discovery service as part of the Admin SDK. The .NET client library relies on the discovery document as does the PHP client. Both the Directory API and the Reports API are.
I noticed that in the documentation for the Email Settings API that calls are still made to apps-apis.google.com:
https://apps-apis.google.com/a/feeds/emailsettings/2.0/
rather than to www.googleapis.com like the other Admin SDK APIs do:
https://www.googleapis.com/admin/directory/v1/
https://www.googleapis.com/groups/v1/groups/
https://www.googleapis.com/admin/reports/
I'm guessing that this is the underlying reason for why this particular API is not included. Is there a timetable for getting the Email Settings API moved to the googleapis service?
There are two types of Google APIs. Gdata APIs and discovery APIs.
The Gdata APIs are old APIs a lot of them have actually been shut down. The client libraries for them to my knowledge where not auto generated.
if you check the documentation for the email settings api there is some sample code for .net.
using Google.GData.Apps.GoogleMailSettings;
The key here is that its a Gdata, its a Gdata api. Which means that like you said its not supported by the current Google .net client library which only supports discovery APIs.
After doing some searching in the code for the Gdata client library. Yes it exists but it hasn't been developed on in ages. There is some code in there for Google email settings There should be a nuget package for it but I have not been able to find it.
The only thing that i have cound that might lead us to the corect nuget package is this
Install-Package Google.GData.Apps
I don't have an admin account so I cant help you test it. However I can probably give you some hints on getting it working. You should be able to track me down from my stack profile if you need help or just post another question on stack. I should spot it.
As per google places API documentation, no authentication is required for using the API. Is that how even check-ins to a place works? number of check-ins to a place are application dependent or aggregation of all check-ins across all registered apps.
Why checks-ins API is not provided via Google Places Javascript API
Using the Google Places API requires you to authenticate each request using an API Key.
Any Places API Check-In Requests sent using the Places API will only affect subsequent Places API Search Request for the API Key used to issue the Check-Ins.
As the Places Library of the Google Maps JavaScript API v3 does not require authentication to use, Check-Ins are not part of the library.