hledger/hledger-api/doc/hledger-api.1.m4.md
2017-01-04 10:50:16 -08:00

1.6 KiB

author date title
author
monthyear hledger-api(1) hledger-api version

web({{ docversionlinks({{hledger-api}}) toc }})

man({{ # NAME

hledger-api - web API server for the hledger accounting tool

SYNOPSIS

hledger-api [OPTIONS]
hledger-api --swagger
hledger api -- [OPTIONS]

DESCRIPTION

hledgerdescription }})

hledger-api is a simple web API server, intended to support client-side web apps operating on hledger data. It comes with a series of simple client-side app examples, which drive its evolution.

Like hledger, it reads files For more about this see hledger(1), hledger_journal(5) etc.

The server listens on IP address 127.0.0.1, accessible only to local requests, by default. You can change this with --host, eg --host 0.0.0.0 to listen on all addresses. Note there is no other access control, so you will need to hide hledger-api behind an authenticating proxy if you want to restrict access. You can change the TCP port (default: 8001) with -p PORT.

If invoked as hledger-api --swagger, instead of starting a server the API docs will be printed in Swagger 2.0 format.

OPTIONS

Note: if invoking hledger-api as a hledger subcommand, write -- before options as shown above.

-d --static-dir=DIR
serve files from a different directory (default: .)
-p --port=PORT
use a different TCP port (default: 8001)
--swagger
print API docs in Swagger 2.0 format, and exit

hledger general options:

generaloptions

man({{

ENVIRONMENT

LEDGER_FILE

FILES

Reads files

BUGS

The need to precede options with -- when invoked from hledger is awkward.

}})