All threads / Pattern for Managing Third Party Integrations

Ask A Question

Notifications

You’re not receiving notifications from this thread.

Subscribe

Pattern for Managing Third Party Integrations

Report spam
Matt Walston asked in Rails

I'm building a small internal app that is essentially glue between several open APIs. Namely, QuickBooks, G Suite, Stripe, and Twilio. Authorizing these third party integrations, maintaining tokens, refreshing tokens and providing an oauth2 client for these services has been a little disorganized. I've been able to find very little in terms of patterns or architectual guidance for organizing these integrations. Can anyone suggest an OSS project that's done this well or an article?

Bump! Interested in seeing if someone has an answer to this?

Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 43,517+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Ruby on Rails tutorials, guides, and screencasts for web developers learning Ruby, Rails, Javascript, Turbolinks, Stimulus.js, Vue.js, and more. Icons by Icons8

    Twitter GitHub

    Support

    Company

    Legal

    © 2021 GoRails, LLC. All rights reserved.