Our App is in the alpha stage, the beta is coming soon.

Icon
Expense tracking and forecasting

Costs to Expect


Our App is currently in the alpha stage, it is being tested by Mrs Costs to Expect prior to testing by a wider group, we hope to release this year

What is it?

Costs to Expect is a service focused on tracking and forecasting expenses, our goal is to simplify your budgeting.

There are three core products within the Costs to Expect service; the Open Source RESTful API, this App and our Open Source website showing the costs to raise our children to adulthood.

Our API is the backbone of the service, everything depends upon it. Our API is available to anyone who wants to use it. Our focus is expenses however the API is being developed in such a way as to allow us to expand our features as our service matures.

Sign in View our API


Our Products

There are multiple products within the Costs to Expect service; below is a short overview if each of our products.

Our App

Our App is the commercial offering for Costs to Expect, we are working towards the public alpha, our aim is to make tracking and forecasting expenses as simple as possible.

Our API

Our Open Source REST API, available under the MIT license, the API drives the entire service.

Our Website

Our website is a long-term social project. My wife and I are tracking all the expenses to raise our child to adulthood.

Our Blog

Our blog acts as a central repository to list all updates, explains why we are doing what we are and acts as a place for us to talk about our products and the service.


API requests

Our App relies on the Costs to Expect API. The API is Open Source, in keeping with that, we show how we use the API.

The requests table details the GET and OPTIONS requests that were made to the API, the responses from those requests is what was used to generate this page.

Your Bearer was included with each of the API requests; the response from each request is personal to you.

Other than ensuring the Costs to Expect API is up and running we haven't needed to reach out to the API to generate this page.