API - CID lookup

[Timothy Roden]

The ZLA website was pulling from the following feed on the old website: http://www.vatusa.net/feeds/cidlookup.php?a=14&key=&cid=.

Is it possible to create an endpoint in the new API that will return the same information as the old feed?

[Daniel Hawton]

No. As I have said several times through development you will need to use the new API.

[Timothy Roden]

As I said in the issue - is it possible to create an endpoint in the new API that will allow access to the same data as was available in this old endpoint?

[Daniel Hawton]

And as I said, no. The API uses a completely different auth system and different middleware that is only available for the API subdomain. The API documentation has been out since Feb with a notice it was coming out with a finalized documentation in April.

The old API and its format is incompatible and is not available. You'd have to rewrite your request and the system that reads the feed anyway, might as well just use the system that's been documented for 6 months now.

The old API is permanently retired. We don't use ID numbers for facilities anymore as they already have unique identifiers, the keys are different, signing is different, requests are formatted different and they must go to the API subdomain to reach the appropriate middle ware. So, again, no.

[Daniel Hawton]

Additionally, the database was completely rewritten and redesigned so the code isn't transferable. The old db was broken and constantly breaking.

[Timothy Roden]

So there's no way to add an endpoint to the new API that returns:

• First name
• Last name
• Email
• Rating
• Facility

?

[Daniel Hawton]

All that is given through the API. As some of that is private info, security protocol must be followed. Use the API.