Hi,

Can I suggest that rather than altering the current API endpoint - which will break implementations out there which currently rely on non-associative arrays - that you instead bump the version number, i.e. something like:

https://unogs-unogs-v2.p.mashape.com/api.cgi?t=deleted&cl=US&st=1&q={query}
or
https://unogs-unogs-v1.p.mashape.com/api-v2.cgi?t=deleted&cl=US&st=1&q={query}

This would ensure that legacy code doesn’t break (for a period of time until the previous call is fully deprecated) and that new code can be written and tested using the new API endpoint to aid a smooth migration.

Thanks,

…Brin