Cursor-based replication for organizations appears incompatible with api key-based authentication

[nickhamlin]

We've been using this tap successfully (v1.5.3) to load zendesk data using API key based authentication. However, the most recent version of the tap started failing when trying to replicate organization data (among other tables) and returned an error message to the tune of Extraction failed (1): KeyError: 'access_token'. Reverting to v1.5.3 gets everything working again.

While I haven't had a chance to investigate further, I'm wondering if that new cursor-based replication might require the access_token auth approach such that those of us using an API key (who wouldn't have an access_token key kicking around in whatever dict was causing that error) are unable to use that approach. Happy to provide more info if helpful in troubleshooting here!

[crystaljg]

same issue here!

[bprice89]

I am still having this same issue, API key still does not work

[mfs-homero-merino]

The error is in the CursorBasedExportStream class in the get_objects function. When calling the http.get_incremental_export, the code tries to access the "access_token" key from the config file regardless the authentication method.