A number of my specials have no campaign details associated to it. However, to be able to post a page update in Foursquare it requires a campaign Id, therefore I am no longer able to post a page update with a special attached.
My Special ID is 50ab336490e745590ae17e57 and that I can pull its details via API call. But when retrieving list of all campaigns, the special doesn't exist/not associated to any campaign.
And Add a page update requires CampaignID
https://developer.foursquare.com/docs/pageupdates/add
Has there been a change in Foursquare API? Thanks, please help.
Make sure that you are making the request to the campaigns/list and specials/detail endpoint with the same user who created the campaign and special. This information is only available to the manager of the special.
Related
I am using the DocuSign REST Api and noticed that the lifetime of a URL obtained using the EnvelopeViews API (https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeViews/createRecipient) is only a few minutes. However, I have gotten emails in the past with DocuSign links. How are these links able to be added to an email (and therefore have a longer lifetime)?
Is there a separate API that can be used to get a longer-life link like the one in the email?
For example, here is an email that has a Review Document DocuSign link:
Good question. Here's what you can do.
Your application wants to let Larry sign a document using the
EnvelopeViews::createRecipient API call.
Your application should store the details needed for the API call in your app's database. Something like: envelopeId, signerEmail, clientUserId.
Create a guid for the database record and add it to the database record.
Now you can look up the database record via either the row's key or
via the guid. Ensure that the guid database column is indexed.
Now create a signing url that you will send to Larry. Something like:
https://myapplication.example.com/docusign-ceremony/[guid]
Send the url to Larry
When Larry clicks on the URL:
Your app is invoked
Look up the guid in the url in your database. You should find the
record that you stored there.
Retrieve all of the record's info: envelopeId, signerEmail,
clientUserId.
Call the EnvelopeViews::createRecipient API call with the data
and get back the signing ceremony url (that must be used within
5 minutes)
Redirect the user's browser to the url.
They'll sign the document(s) and then be re-directed back to your
application.
Done.
And guess what? This is pretty much what DocuSign does itself.
The response from Larry K above is correct, you would need to handle this on your side.
These are all the parameters that you can send as part of the request body for the POST {vx}/accounts/{accountid}/envelopes/{envelopeid}/views/recipient API endpoint and there are no options to set the expiration time for the recipient view that you create.
You could look into using PowerForms to see if they fit your needs. With PowerForms you can create a URL that users can click and it will allow them to fill out a specific DocuSign envelope. This might not fit your needs if you need to pre-fill some of the fields with information related to the specific recipient but it might be worth looking at.
PowerForms Documentation:
https://www.docusign.com/features-and-benefits/features/powerforms
Please correct me if I'm wrong but I think that your goal is creating the recipient view URL, creating an email formatted in a specific way and sending that email to the recipients.
If you use the branding feature you could specify the format for your email (if you want to use a specific message) and just send the envelope to your recipients. Once the recipients receive the email they'll see the message in the format that you specified and the link for accessing the envelope would be a regular DocuSign link that doesn't expire.
The link below shows how to create Brands in your account. Specifically signing brands would allow you to set the email content.
If you have multiple email formats you could create multiple brands and just specify the brandId when creating the envelope.
I hope this helps.
Branding:
https://support.docusign.com/guides/ndse-admin-guide-configure-branding
Please help. I would like to verify if webhooks from Graph API can retrieve the following fields:
1. Organization
2. Position
3. Department
4. Manager
If not, is it only limited to webhook events indicated in this link, https://developers.facebook.com/docs/messenger-platform/webhook#response ?
the webhook sends only the fields specified in the link that you have posted.
To retrieve all the others information, you can use the Graph APIs.
I've read over Stripe's API and couldn't find a way to find if a country is supported by Stripe.
e.g: I have an user who is going to receive a payment and he is from a country, I need to check if he can use Stripe to receive this payment based on his country.
Thanks
Stripe's Country Specs API should do what you need:
https://stripe.com/docs/api#list_country_specs
Their documentation includes sample code and sample responses for multiple languages.
No such info as I know in api, but there are not so many countries they support at he moment to accept payments. https://support.stripe.com/questions/what-countries-does-stripe-support
So you can add them into a global variable to your app and update it whenever a new country will be in the list. A settings page in admin panel may be, so you can easily update the list.
I am trying to figure out the best possible way to manage a system where we will be sending out different documents via the api through one account. These documents will need to be handled by different departments. Is there a way in the api to share the envelope with a particular group/user? My other idea was to create multiple department API users and depending on which document I am sending will use that departments API user and associate that API user with the department user. It seems like a more complex solution but I know it would work.
Thanks,
Dan
I'm not sure why your question was downvoted without a reason, so I'll throw out my 2cents.
Question 1: Is there a way in the api to share the envelope with a particular group/user?
You can share all of a user's envelopes with group/user, but not specific envelopes. I do not suggest building a workflow around this.
Idea 2: Create multiple department API users and depending on which document I am sending will use that departments API user and associate that API user with the department user.
This is the best solution for scalability and customizibility, remember that an API user does not need to be an admin to create an envelope. In this case, it would be better if that user was not an admin, so they are limited to access only the envelopes that you'd want them to access.
I'm not sure what language your integration is in, but you should be able to store all of the credentials in an array/hash and just call the specific entry for username/password per workflow.
You didn't post what requirements you need for these workflows, so this is a very high level generic question and answer. You may want to go back to the drawing table and figure out your hard requirements. The solution above may not fit all of your requirements, especially if your security team has specific requirements that they need to have followed.
example requirements
Envelopes need to be created through the API
All envelopes must reside on the same account
Envelopes can't be seen by other departments
Envelopes need to be modified by department DepartmentName after Envelope Creation
The API needs access to view the status of these documents
I have obtained the 4sq checkin id from twitter streaming api and I want to get the details of the checkin such as userid, time, venueid etc.
However, when I check the 4sq api, I find that the related endpoint requires an acting user. So can anybody suggest what could be an alternative way to get this information? (especially user_id)
Thanks!!
Right now there is no alternative way:
The Checkin endpoint requires authentication, it will return the data you are looking for.
Foursquare requires you to act as a user (via OAuth) to get user related information.
The only thing that does not require authentication is the Venues Platform, but you cannot get information about checkins from it, just number of people who checked in a place.