API requests in postinstall lifecycle endpoint

I am developing a private add-on for my organization and want to make a few api calls when it is installed.

I’ve tried using both the lifecycle api key and the authToken in the payload of the postinstall lifecycle endpoint, but I keep getting {‘message’: ‘Token is not valid’, ‘code’: 4017}

Are tokens valid when the postinstall lifecycle call is made?

Hello Jesudas, the token that is provided by Clockify in the installation response is usable and non expirable. Can you please send us the curl request that you’re making so we can check it out?

Here’s a sample request that I tried in the development account: https://developer.clockify.me/api/v1/workspaces/68a8a5747083da78f61a9509/member-profile/695ec8c00c421928c2889c8f

The header: X-Addon-Token = body.authToken (this is from the body of the request made to the postinstall body)

This returns:

{‘code’: 401, ‘message’: ‘Token is not valid’}

Hello there,

If you use this call - https://api.clockify.me/api/v1/workspaces/{workspaceId}/member-profile/{userId}

Do you get any different results?