HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
balanced
balanced-api
Ruby2012–2014
balanced / balanced-api

balanced-api

Balanced API specification.

15Distinct people
50Mentions
0Explicit recommenders
220GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Balanced API specification.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month50 dated mentions

Observed mentions: 2012-08-17 19:37:53 UTC to 2014-07-22 19:16:43 UTC.

02468102012-08-01 00:00:00 UTC to 2012-09-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsAug 20122012-09-01 00:00:00 UTC to 2012-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-10-01 00:00:00 UTC to 2012-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2012-11-01 00:00:00 UTC to 2012-12-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2012-12-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-01-01 00:00:00 UTC to 2013-02-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2013-02-01 00:00:00 UTC to 2013-03-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2013-03-01 00:00:00 UTC to 2013-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-04-01 00:00:00 UTC to 2013-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-05-01 00:00:00 UTC to 2013-06-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-06-01 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-07-01 00:00:00 UTC to 2013-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 20132013-08-01 00:00:00 UTC to 2013-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-01 00:00:00 UTC to 2013-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-01 00:00:00 UTC to 2013-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-11-01 00:00:00 UTC to 2013-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-12-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2014-02-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2014-02-01 00:00:00 UTC to 2014-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-03-01 00:00:00 UTC to 2014-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-04-01 00:00:00 UTC to 2014-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-05-01 00:00:00 UTC to 2014-06-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2014-06-01 00:00:00 UTC to 2014-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-01 00:00:00 UTC to 2014-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 2014

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20122012-08-01 00:00:00 UTC2012-09-01 00:00:00 UTC321
Sep 20122012-09-01 00:00:00 UTC2012-10-01 00:00:00 UTC000
Oct 20122012-10-01 00:00:00 UTC2012-11-01 00:00:00 UTC000
Nov 20122012-11-01 00:00:00 UTC2012-12-01 00:00:00 UTC725
Dec 20122012-12-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
Jan 20132013-01-01 00:00:00 UTC2013-02-01 00:00:00 UTC303
Feb 20132013-02-01 00:00:00 UTC2013-03-01 00:00:00 UTC1019
Mar 20132013-03-01 00:00:00 UTC2013-04-01 00:00:00 UTC101
Apr 20132013-04-01 00:00:00 UTC2013-05-01 00:00:00 UTC202
May 20132013-05-01 00:00:00 UTC2013-06-01 00:00:00 UTC202
Jun 20132013-06-01 00:00:00 UTC2013-07-01 00:00:00 UTC202
Jul 20132013-07-01 00:00:00 UTC2013-08-01 00:00:00 UTC000
Aug 20132013-08-01 00:00:00 UTC2013-09-01 00:00:00 UTC000
Sep 20132013-09-01 00:00:00 UTC2013-10-01 00:00:00 UTC000
Oct 20132013-10-01 00:00:00 UTC2013-11-01 00:00:00 UTC000
Nov 20132013-11-01 00:00:00 UTC2013-12-01 00:00:00 UTC101
Dec 20132013-12-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
Jan 20142014-01-01 00:00:00 UTC2014-02-01 00:00:00 UTC707
Feb 20142014-02-01 00:00:00 UTC2014-03-01 00:00:00 UTC101
Mar 20142014-03-01 00:00:00 UTC2014-04-01 00:00:00 UTC202
Apr 20142014-04-01 00:00:00 UTC2014-05-01 00:00:00 UTC101
May 20142014-05-01 00:00:00 UTC2014-06-01 00:00:00 UTC404
Jun 20142014-06-01 00:00:00 UTC2014-07-01 00:00:00 UTC000
Jul 20142014-07-01 00:00:00 UTC2014-08-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Balanced API Specification This repository contains an executable specification of the Balanced API. The goal of this repository is two-fold. First, to ensure that the API is working according to the spec. Second, to provide a place to have discussions around the API as a product. An Executable Specification Specifications don't matter if they're not followed. Therefore, this specification is executable, so we can ensure conformance to the spec. There are more details in the README file inside the features directory, but to run these tests yourself, simply: $ git clone https://github.com/balanced/balanced-api.git $ cd balanced-api $ bundle $ bin/rake cucumber This requires Ruby. We run the changes with Ruby 2.0, but other versions will probably work as well. Let us know if you have any problems running these specs, and we'd be happy to help. If you're working on a new scenario, the 'focus' task is useful. Tag a scenario with @focus, and then run bin/rake focus. It will only run that single scenario. Discussions around changes Speaking of issues, that's the second purpose of this repository. If you would like to see a new feature implemented in the Balanced API, please open an issue and we'll discuss it. For example, one of our biggest requests is to support non-USD currencies. Here is the issue with the discussion, and when we support this feature, we close the issue via a pull request that implements the specification, and then everyone on the issue gets notified. Sometimes, Issues are great for collecting feedback, as well. For example, all implementation of the current framework was done via PR, and some issues need more explanation around use cases by those who want the feature, like Bitcoin support. We try to do as much 'internal' discussion in these issues as well, it's not just for public feedback. If you want to know what we're thinking, just search for a relevant issue! Edit field descriptions for scenarios Field descriptions are from balanced.rev1.json, which are generated from balanced-api. The "forms" used in balanced-docs are assembled from parameters supplied in the scenarios in balanced-api. Those scenarios should be updated to include the fields missing the specific scenario section and a newly generated balanced.rev1.json be committed into the docs. To generate balanced.rev1.json in balanced-api run: bundle exec rake features:all DO NOT run bundle exec rake parallel:features doing so causes the file to overwrite itself.
Read the full README on GitHub

What Hacker News says

10 sources
for Nick Kishfy: I'd be curious what you think of Balanced's product development strategy: We have an undisputed product leader (our CEO), but we got so much demand for a feature (ACH debits) that we built it, not exactly as our customers wanted, and after originally telling them know. Essentially, we used an issues thread and a public repo on Github to test our assumptions with our developer community. I'd be curious to hear your thoughts. You can read the whole thing here: https://github.com/balanced/balanced-api/issues/2 I also left this comment on the original blog post: http://blog.mojotech.com/post/44224044723/more-features-wont...
In MORE FEATURES WON’T SAVE Your PRODUCT
It's just part of being an open company, read more here: http://blog.gittip.com/post/26350459746/the-first-open-compa... We crowdsource feedback for a lot of things we do @ Balanced. For example, we've openly discussed pricing (https://github.com/balanced/balanced-api/issues/48), etc. Everything's on https://github.com/balanced/balanced-api. We're trying a different approach to payments, for once. Openness and transparency.
In Nothing is certain, except death and taxes .. and chargebacks
(I'm a Balanced employee) My personal views are my own and NOT Balanced on this topic. I agree, I think bitcoin is a great solution -- for some things. More and more I feel that it's the right strategy going forward. We actually have an open github issue to support it: https://github.com/balanced/balanced-api/issues/204. You should take a look and read the comments there -- they're very interesting. Something I'm trying to figure out though is something along the lines of this comment: https://github.com/balanced/balanced-api/issues/204#issuecom.... How can we tackle on risk in a reasonable way? Jon Matonis, CEO of Hushmail, wrote a pretty interesting article on Bitcoin for Forbes, where he mentions Balanced: http://www.forbes.com/sites/jonmatonis/2012/11/26/payments-s... but he just didn't answer or ask the _right_ questions. Another rea
Read the rest
son - there just hasn't been enough demand for it.
In Nothing is certain, except death and taxes .. and chargebacks

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.