I’m at the very early stages of planning the development of a tap for ClickUp. My super high level plan would be to use the SDK to build a REST based tap using the ClickUp API (https://clickup.com/api). That sound reasonable? Does the SDK help at all with pagination and rate limiting requirements imposed by ClickUp’s API? Any rough estimate on how long this would take a decent python developer to accomplish? Thanks!

I've built about 7 taps with the SDK now and it takes me between 30 minutes and 2 hours to build most of them. The first time can take a bit until you understand the logic of the SDK, but for most of the problems I've encountered (pagination, parent-child, etc.), there is an out of the box approach to tackling it that saves time.

Thanks @stephen_bailey I appreciate the feedback. Glad to hear I’m thinking in the right direction.

I don't think the SDK has rate limiting built in yet, actually starting work on clickup next week. It really depends on the API, some you can get up and running in a usable capacity in as fast as Stephen mentioned. For someone new to the SDK I'd say at least 4 hours, when I was new to python it was 8 hours for me to get something simple to work but again I was brand new to python. Where APIs get harder is when you have a bunch of streams, parent and child relationships and some have incremental stream capability. Then you have to figure out the right balance of that with the API limits you have. The other hard stuff that takes a while is decent documentation, tests, CI (testing multiple versions of python), Discovery process (Sometimes easy if you can hard code it, if you need to dynamically make this it really depends on the API). ie for click up you have custom fields. I sent you a DM as I'm actually trying to put a clickup tap together right now, and maybe you would like to join with the group that's pitching in to make this happen