First things first, if you’re a developer, I highly suggest you check out this dev blog post on http://dev.dwolla.com/. This post is meant to be more of an introduction of sorts for all of our non-technical business development, product and design friends looking to learn if a Dwolla integration is right for their company, app or project.
One of the most beautiful and powerful things about Dwolla is its web-driven and open structure, or its ability to play nicely with a host of other Internet technologies. Bundled into a series of accessible end points, Dwolla’s network and technologies are available to all in what’s called an API, or Application Programming Interface (great explanatory video of open vs. closed for us laymen). This API allows the network to connect to social platforms, plug-in to existing software and embed itself into new applications. It’s what makes Dwolla compatible with the 21st century and is what’s fueling a lot of our growth.
Today, our API is getting a new home to lay its head and rest its feet. Introducing, the Integration Portal. Best thing? It’s designed with two kinds of users in mind, the non-technical and the technical.
Why do this? One of the biggest misunderstandings about API portals is that their purpose is only for developers. That’s just not true. Integrations start with a spark of curiosity, “Would this work for my company?” Technical or not, who asks that question is irrelevant at that point; how it’s answered is what determines the outcome.
It all starts by inferring one simple question: Do you code?
“I can <code>” takes you to our new and improved developer playground. Clicking “I don’t code” won’t teach you how to code (do checkout treehouse or Code Academy) or show you exactly how to integrate Dwolla into your individual project, but it will be able to provide an easy-to-understand rundown of Dwolla and what an integration could mean for your company.
We have a lot of cool ideas and surprises planned for this project, but we’d love to hear your feedback in the comments section. What are we missing? How can we make this even better?