Data returned to Alexa skill


#1

I am working on an Alexa skill that executes a GET from an Airtable base where the record contains a field whose field type is Attachment. The GET in the Alexa skill assigns whatever is passed from Airtable to a variable. I don’t have a means of displaying the Alexa variable to see the contents. From the API documentation, I understand an attachment field will pass a field ID, the URL of the object and the file name of the object. Could someone provide an example of what is passed from the API using the following example:

AudioField=api_response.records.0.fields.AirtableAudioFile;

After execution, what is the contents of AudioField? Audiofield = ‘xxxxyyyyzzzz’

Thanks in advance for your reply!


#2

You should be able to see that information in the API docs.

If you visit your base, then in the upper right there is a ‘Help’ menu with an API documentation link. Click that and it will show exact data from your base and what it looks like.


#3

Thanks for your reply. Yes. I have found this and have see the actual data as it resides in my base. I was wanting to know how this data is passed through the GET API. Are all three pieces of information (id, url and filename), passed at once with some sort of delimiter between each so that the desired information can be parsed once it is received? I am working on an Alexa skill and do not have a means of displaying this data received by the Alexa skill. If you are familiar with how this data is passed, I would be anxious to hear. Thanks.


#4

Hmm, are you sure you went to the API documentation for your base? It shows you exactly what you get from the GET command. It doesn’t change anything. The data in the api documentation is making an actual api call and showing you exactly what you get returned.


#5

The API documentation is very helpful. I believe it is on my side of the API. The service I am using (Storyline) is not parsing the returned data object to provide only the URL to the object. My application does not care about the id of the field or the file name of the object. I will work with Storyline on getting this fixed. Thanks for all your comments.


#6

The API documentation is very helpful. I believe it is on my side of the API. The service I am using (Storyline) is not parsing the returned data object to provide only the URL to the object. My application does not care about the id of the field or the file name of the object. I will work with Storyline on getting this fixed. Thanks for all your comments.