{"id":7,"date":"2014-10-21T22:41:16","date_gmt":"2014-10-22T05:41:16","guid":{"rendered":"http:\/\/biz197.inmotionhosting.com\/~blogsi8\/2014\/10\/21\/20141021api-development-at-sift-science\/"},"modified":"2019-01-22T18:37:50","modified_gmt":"2019-01-23T02:37:50","slug":"api-development-at-sift-science","status":"publish","type":"post","link":"https:\/\/engineering.sift.com\/api-development-at-sift-science\/","title":{"rendered":"API Development at Sift Science"},"content":{"rendered":"

At Sift Science, APIs are incredibly important. We spend a lot of time\u00a0improving upon our existing APIs and thinking about how to design even better ones. A couple of weeks ago at the\u00a0San Francisco API Craft Meetup<\/a>, I gave\u00a0a talk\u00a0on how we built the API that powers our new Sift console.<\/p>\n

At its inception, the Sift console was an internal Rails app built for\u00a0investigating model issues. As we made the console accessible to our users, we rewrote it as a single-page JavaScript app driven by a set\u00a0of private, undocumented APIs. For the third iteration of our console, we took an API-driven approach. The new APIs that drive the console are powerful and\u00a0comprehensive enough to allow our users to build their own interfaces\u00a0atop their data. The console is just another consumer of\u00a0these underlying APIs.<\/p>\n

Some of the technologies we utilized to build it include:<\/p>\n