Mark Michon

Happy to accept a PR that updates the integration's config. 👍

Not sure why this is happening. I'm seeing it too when testing a new account, but it certainly worked fine in the past. Perhaps something with changes to their auth...

I'm not sure if there is a particularly good solution to this out of the box, as for most (perhaps all) Pizzly users they would lose the current app state...

I don't believe it is possible in the current setup. The initial auth would need an additional step, and refreshing looks like a whole new set of issues in regard...

Thanks for the PR. You can see more on the format that integrations require [on this page of the docs](https://github.com/Bearer/Pizzly/blob/master/docs/integrations.md). Once you get the json formatted, add it to the...

@anuragphadke Seems useful. Haven't had a chance to test it yet though. Will hopefully get to it today or tomorrow.

Yeah both the js and node clients will likely need some updates to accommodate your implementation, which is why initially I was thinking it would be easier to take the...

Just to clarify what I mean, the integration would look like a normal one, but with a simplified config file: ```json // e.g. google-unified.json { "name": "Google", "auth": { "authorizationURL":...

@anuragphadke Yeah google is quite inconsistent with their APIs. Perhaps taking the approach that the shopify integration uses would be best. Note the `baseURL` line in the request config and...

Hey, you're correct. The language is somewhat unclear in the wiki. Only the secret key is used for the endpoints, and the publishable key is intended only to be used...