Hey @James_Carl , there’s not an association on whether a user is premium or not - premium is determined by the workspace/organization.
For example, you could have a workspace associated with your user that’s a free workspace (and not have access to features such as start dates), but you could also have a work organization you’re a member of that is a premium workspace that would allow for these features - both in the API and the web app.
As others mentioned a while back in Premium Versus Free Field - #6 by DearDaniel, the only real way to test for this is to:
- Get the list of workspaces associated with a user that you want available in your application via the User endpoint and the Workspaces endpoints.
- Try to perform a premium action in the applicable domain, and check the response code. If you get a 402 (which will be definitively 402 after next Tuesday - see Premium-Only API Error Changes for more context), then they can’t perform the action in that workspace/organization.
There are several ways to handle this: always show the feature and let the user know when it’s not available for a given domain, perform test actions when initializing a user and cache whether a workspace/org is premium for a certain amount of time, etc., and it’s really up to you for what’s the best way to go about it. In fact, several other developers (such as Instagantt) have already had to handle similar cases for Custom Fields.
As mentioned in Premium Versus Free Field - #6 by DearDaniel, we hope to make this available via the API at some point, and we apologize for the difficulty here.
As for your first question, it appears that Start Date is always a column in both Free and Premium. I wouldn’t expect that to change, but I’ll follow up with our team internally as we should ideally be more consistent about it with the API.