1
0
mirror of https://github.com/aclindsa/ofxgo.git synced 2024-12-26 06:53:21 -05:00
Golang library for querying and parsing OFX
Go to file
Aaron Lindsay 59a29e18a5 profile: Save message set name somewhere other than XMLName
Of course the same information is available there, but having it brought
out as its own field seems more convenient and intuitive for users.
2017-04-03 19:56:16 -04:00
cmd/ofx Rename Response/Request Profile -> Prof 2017-04-03 19:50:16 -04:00
bank_test.go Rename files to more closely correspond to their message set tags 2017-03-31 15:05:59 -04:00
bank.go Rename files to more closely correspond to their message set tags 2017-03-31 15:05:59 -04:00
client.go Check HTTPS is always used 2017-04-01 21:33:56 -04:00
common.go Rename Response/Request Profile -> Prof 2017-04-03 19:50:16 -04:00
creditcard_test.go Add tests for credit card requests and responses 2017-03-31 16:22:33 -04:00
creditcard.go Add tests for credit card requests and responses 2017-03-31 16:22:33 -04:00
doc.go Improve documentation 2017-03-26 21:02:20 -04:00
invstmt_test.go Add investment statement tests 2017-04-01 21:17:32 -04:00
invstmt.go Add open orders to investment statment responses 2017-04-01 11:05:40 -04:00
leaf_elements.go Add missing leaf elements with numbers 2017-04-03 19:54:32 -04:00
profile.go profile: Save message set name somewhere other than XMLName 2017-04-03 19:56:16 -04:00
README.md Improve documentation 2017-03-26 21:02:20 -04:00
request_test.go request_test: Point out first difference in marshalled string 2017-03-31 20:16:44 -04:00
request.go Rename Response/Request Profile -> Prof 2017-04-03 19:50:16 -04:00
response_test.go Generalize response parsing code 2017-03-31 11:54:43 -04:00
response.go Rename Response/Request Profile -> Prof 2017-04-03 19:50:16 -04:00
seclist.go Rename files to more closely correspond to their message set tags 2017-03-31 15:05:59 -04:00
signon.go Don't require UIDs to be 36 characters 2017-03-29 09:23:15 -04:00
signup_test.go Generalize response parsing code 2017-03-31 11:54:43 -04:00
signup.go Generalize response parsing code 2017-03-31 11:54:43 -04:00
types_test.go Trim spaces when unmarshalling UIDs 2017-04-03 19:46:10 -04:00
types.go Trim spaces when unmarshalling UIDs 2017-04-03 19:46:10 -04:00
util.go Switch to own clone of xml encoding library 2017-03-22 20:59:40 -04:00

ofxgo

A library for querying OFX servers and parsing the responses and an example command-line client.

Goals

The main purpose of this project is to provide a library to make it easier to query financial information with OFX from the comfort of Golang, without having to marshal/unmarshal to SGML or XML. The library does not intend to abstract away all of the details of the OFX specification, which would be very difficult to do well. Instead, it exposes the OFX SGML/XML hierarchy as structs which mostly resemble it.

Because the OFX specification is rather... 'comprehensive,' it can be difficult for those unfamiliar with it to figure out where to start. To that end, I have created a sample command-line client which uses the library to do simple tasks (currently it does little more than list accounts and query for balances and transactions). My hope is that by studying its code, new users will be able to figure out how to use the library much faster than staring at the OFX specification (or this library's API documentation). The command-line client also serves as an easy way for me to test/debug the library with actual financial institutions, which frequently have 'quirks' in their implementations. The command-line client can be found in the cmd/ofx directory of this repository.

Library documentation

Documentation can be found with the go doc tool, or at https://godoc.org/github.com/aclindsa/ofxgo

Using the command-line client

To install the command-line client and test it out, you may do the following:

$ go get -v github.com/aclindsa/ofxgo/cmd/ofx && go install -v github.com/aclindsa/ofxgo/cmd/ofx

Once installed (at ~/go/bin/ofx by default, if you haven't set $GOPATH), the command's usage should help you to use it (./ofx --help for a listing of the available subcommands and their purposes, ./ofx subcommand --help for individual subcommand usage).