As part of the push to support integrations, Pine now supports the standardized OAuth workflow for creating public integrations.
Briefly, this involves:
Creating an application with the public workflow.
Redirect user installation requests to Pine’s authorization URL.
Handling the redirection for users who have approved your application from Pine’s authorization URL. A
codewill be appended to this redirect URL.Exchange the authorization code for an access token.
If you’re experimenting with integrations, I go into far more depth here.
Okay, there will be one more changelog related to integrations, which should take me a couple of weeks to complete. Once that’s done, I’ll return to core application development and publish some research ideas that have started to accumulate.
Until then!