Hi ​@devin.tiemens,

Just to check: are you trying to import the API’s Open API documentation in its original 3.1.0 spec? It seems that way from your screenshot.

This tutorial was based on a case we worked on with this API, where we ran into the issue that the Import Swagger feature is only compatible with Open API spec until 3.0.0. The error message we encountered was slightly different though, if I remember correctly. 
 

Apparently, they converted the Open API documentation from the original 3.1.0 to the 3.0.0 spec beforehand, for editing purposes. Might be worth trying out. 
 

It’s a really brilliant feature when everything works as expected, but not every API offers the documentation in this way unfortunately. 

Hi ​@devin.tiemens 

I heard from the person doing the video that what ​@Stijn Verhoeff explains is what was done to make it work.

Thanks for your reply. Is it possible to get the 3.0.0 documentation to try it?

Hi ​@devin.tiemens 

You change the code in it to be 3.0.0 instead of 3.1.0. I do have the code from the last time. You can’t attach JSON files to this, so I changed it to txt. You need to change it back to a JSON file to properly use it.

Thanks Thomas, this works!

​@Thomas Lind Dear Thomas,

I downloaded the CheckWxApi_V3.txt file, and when I paste the contents into the ‘code editor’ box or use the ‘local file path’ option and point to the downloaded file, in both cases I get a ‘the request timed out’ error.

Am I doing something wrong or did something change?

Regards,

Pieter

Hi ​@PieterQ 

I can’t import the first video, so this is attempt two.

https://use.vg/DOPip6

You should be able to see how it is done in this vidgrid video.

Hi ​@Thomas Lind ,

Thank you so much, video looks great!

Unfortunately, it does not work at my side, I followed exactly what was shown.

I was wondering: the Import gets active if you choose the ingest instance. Does that mean the ingest server is doing something? We are running in Azure, so maybe it's a firewall issue?

I also noticed the table flattening option throws a timeout error, and also the ‘test connection’.

So could it be a firewall issue? And what settings are needed on the Azre VM/Firewall to communicate with the TimeXtender portal (if that is indeed needed).

Kind regards,

Pieter

Hi ​@PieterQ 

Yes similar to if you try to generate a XLST code, it uses a ingest instance to do the call.

Have you tried to create other REST data sources in this setup and are you able to use the table builder there, it should be the same sort of thing.

Hi ​@Thomas Lind 

Both the table builder (‘get schema’) as the ‘test connection’ throw a timeout error.

Looks like the ingest instance cannot be reached (which is in Azure)? But why??

Hi ​@PieterQ 

Send a request to Zendesk support. I think that would be better.

You can also just send an email to support@timextender.com.

I will be able to make more specific requests.