The best thing would be to fetch those values straight from the configuration and put them in the RAML automatically via ERBing the RAML files and doing some preprocessing.. but that's a longer story.
Ideally we'd de-duplicate by having hit charge numbers configured in one place and reflected in the docs automatically.
Seems low priority though, because it would be quite a lot of work for a small amount of de-duplication. It would be complicated by some features which cause variable hit charges e.g. nextbuses (It's not just one number assigned to each endpoint)
Follow on from https://github.com/transportapi/api-console/issues/10 Just rescuing Martin's comment as a new issue (low priority)
Ideally we'd de-duplicate by having hit charge numbers configured in one place and reflected in the docs automatically.
Seems low priority though, because it would be quite a lot of work for a small amount of de-duplication. It would be complicated by some features which cause variable hit charges e.g. nextbuses (It's not just one number assigned to each endpoint)