![]() The fun starts when we ask followup questions. This first request pretty much does the same thing as Spoken Results API, meaning that it returns information in form of full sentence. We also specify our location with geolocation parameter - this is one of the optional values (other are ip and units) that can provide context for the questions. First of them is directed at v1/conversation endpoint and includes a questions in the i parameter. ![]() ![]() The filtered response for above query would therefore look like so:Ĭonsidering that we want to ask multiple questions, we also have to make multiple queries. To do that - podtitle and more robust includepodid - parameters can be used, as shown above. Considering that each response can sometimes include even 10 or so pods, it’s desirable to describe what we want to receive from the API. Each of these belongs to its own section called pod, which in turn includes subpods which hold individual pieces of data. This can be for example graph, image, step-by-step solution or table. "What is pod, though?", you may ask.Įvery result from Wolfram Alpha (both website and API), generally includes multiple categories of data. One extra thing that's added to this one is includepodid parameter, which tells the API that in this case we only want Result pod to be included in the response. Apart from the input itself, the query looks very similar to the one in previous section. To make the API aware that we want to do math - in this case - solve equation, we need to prepend the actual equation with word solve. The Full Results API shown in previous section doesn’t just answer some curious questions, but it also does math (and really almost everything).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |