I can't seem to find a definitive answer on this, but I'm wondering whether the member ID for a LinkedIn user is always made of numbers. The documentation seems to indicate that that is the case, but I don't see a description that explicitly states that the member ID is only numbers.
Can anyone confirm this and link to the documentation that says this?
Thanks!
If you are talking about the Member Id that is returned via the API when making a GET https://api.linkedin.com/v1/people/~:(id), then that value can be made up of numbers or letters.
Related
I'm working on a simple app to programmatically retrieve ads performance within Linkedin. I have general API experience but this is the first time i get my feet wet with the Linkedin API.
One example from Linkedin API documentation suggest something that would get me started:
GET https://api.linkedin.com/v2/adAnalyticsV2?q=analytics&dateRange.start.month=1&dateRange.start.day=1&dateRange.start.year=2016&timeGranularity=MONTHLY&pivot=CREATIVE&campaigns=urn:li:sponsoredCampaign:112466001
I am encountering two problems:
First this example implies that you already know the campaign ID. However I am unable to find a way to retrieve a list of campaign ID's for a given account.
Second, if I manually pull a campaign ID, I receive an error: "{"serviceErrorCode":2,"message":"Too many fields requested. Maximum possible fields to request: 20","status":400}". Pretty clear error.
A little research tells me that by adding the parameter "&fields=" I will be able to limit my query to less than 20 field (I really need only a dozen anyway) but I can't find and documentation regarding the names of the fields available.
Any help or pointer will be appreciated.
please refer the link below scroll down where you ill see the field names mentioned as metrics , these are the fields.
https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/ads-reporting?tabs=http#analytics-finder
I'm using https://geocode.search.hereapi.com/v1/geocode?q to search for address in USA.
When I give q=765 Rive I get lot of address but the moment when I give 765 River My results are very restricted and I get only very less responses and which does not include lot of addresses I got in the previous q search.
Please check now. When I trying with the postman .It is giving the same number count in the response.
https://geocode.search.hereapi.com/v1/geocode?q=765 Rive&apikey={your_api_key}
https://geocode.search.hereapi.com/v1/geocode?q=765 River&apikey={your_api_key}
And Please follow below document, which explains how we can formulate a qualified query.
https://developer.here.com/documentation/geocoding-search-api/dev_guide/topics-api/code-geocode-qualified.html
I seems that "text" argument of the answerCallbackQuery API request is not optional, even though the documentation states it is:
Text String Optional Text of the notification. If not specified,
nothing will be shown to the user, 0-200 characters
It also says:
NOTE: After the user presses a callback button, Telegram clients will
display a progress bar until you call answerCallbackQuery. It is,
therefore, necessary to react by calling answerCallbackQuery even if
no notification to the user is needed (e.g., without specifying any of
the optional parameters)
That is exactly what I'm trying to do, but alas I receive the error "Bad Request: MESSAGE_EMPTY" if "text" property is omitted. I can't believe that I'm the only one who has stumbled over this problem. Therefore I strongly suspect that I'm doing something wrong here. Can you please help?
I don't want notification to be shown on click because the reaction to click is going to be sent as the message, briefly after the click. Also it seems that other bots have no such problem, for example the BotFather.
Also, does anyone know a forum or another place where I can get a support regarding the API?
I think it is optional for text parameter yet.
I tried this request, and no error shown.
You can join #BotTalk group which is created by Telegram Support Force, and ask if others have same problem.
It seems that it was a temporary bug that was fixed in the same day.
Thanks to Sean for advising #BotTalk where problem was resolved.
Background
I'm writing an Alexa Skill and looking to get pieces of information from the user.
The following conversation for example:
Alexa: What month were you born at?
User: April
Alexa: Good. And what was your favorite movie?
User: April
The problem
Given the following utterances:
GetMonthIntent {month}
GetMovieIntent {movie}
Once a user answers April for the second time, the GetMonthIntent might be triggered.
What I have tried
Asking the user to specify which piece of information is giving by using the following utterances:
GetMonthIntent Month {month}
GetMovieIntent Movie {movie}
The question
What is the right way to make Alexa wait for a single term answer based on the current context?
In the same vein as the other answers here, you should take a look at the newest Node.JS library here, which handles state out of the box:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs#making-skill-state-management-simpler
You could define:
State_Launch
State_Month
State_Movie
And then return the proper error response if anything other than the GetMovieIntent or GetMonthIntent (etc.) intents are called in the wrong state.
You would have to do data validation on the server side to make sure the "month" is a valid one, and movies are even harder to validate unless you have a list of expected values. That is, if you care to parse them for use beyond repeating back.
Unfortunately, there is no solution. There is no way to specify the 'context' in which a user reply should be interpreted, so you have to tell the user "what was your favorite movie? Please say 'my favorite movie is' and then the name of the movie".
Here are two ASK feature requests that I think would address your issue:
https://forums.developer.amazon.com/content/idea/41062/creating-something-to-help-with-more-structured-qu.html
https://forums.developer.amazon.com/content/idea/55525/allow-a-response-to-specify-a-set-of-expected-inte.html
Personally I think this is fairly important so I voted for those, but they are not near the top.
I ran into this same problem when I created the "Who's on First? Baseball Skit" skill. I handled this by:
Create a sequence number for each response given by Alexa
Write this number to the "session" in the response.
The session is then passed back to your skill by Alexa in the next request.
Read the sequence number from the request to know what the previous question was.
If a given intent could be the answer to multiple questions (eg. month and movie in your case) then use the sequence number to determine which it is.
This should give you ideas on how to deal with repeated answers. The session is quite easy to use. Other options include writing the userId and status to a database like DynamoDB, but I find that the session works in most cases.
Yesterday I registered with HERE to experiment on Traffic/Flow data.
I registered with both the 'Public Basic plan' as well as the '90-day evaluation'. I managed to perform some basic query's and also got results but the next step was to understand the output.
The official way to get descriptions on the output data is described here:
https://developer.here.com/rest-apis/documentation/traffic/topics/additional-parameters.html.
I simply substituted my credentials in the the https://traffic.cit.api.here.com/traffic/6.0/xsd/flow.xsd?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE} URL and pasted in my browser. But the only result I get for every xsd is:
"error:These credentials do not authorize access. Please contact your customer representative or submit a request here developer.here.com/contact-us to upgrade your account. You can also get valid credentials by registering for a free trial license on developer.here.com.,error_description:NA" . So apparently I am authorized to use the api but not authorized to get information on how to interpret the results...?
I already found out the many abbreviation are explained on Interpreting HERE Maps real-time traffic tags but I found a few that weren't described, like <SSS> and <SS>.
Thanks in advance.
UPDATE: Apparently I was already voted down on the question. What am I doing wrong?
The Description of SS/SSS tag is here:
The SS (SUB_SEGMENT) will be provided if the current traffic data is
more precise than the road defined. When there are SS elements, the
elements will be ordered by driving direction. If there are SS
elements, the lengths (LE) of all SS elements will add up to the
length of the roadway represented from the corresponding CF section.