avt-fresh 0.0.4

No project description provided

AVT Fresh!

This is a wrapper of the roly-poly, not 100% ergonomic Freshbooks web API. It is far from comprehensive: It was created for the specific client- and invoice-related needs of Averbach Transcription.

There are "band-aids" here to work around some of the API's shortcomings.

The Goodies

Invoices

get, get_one, create, send, update and delete are the bread and butter functions here.

The get... functions return some handy NamedTuple instances with helpful attributes, notably FreshbooksInvoice.lines which have Decimal values where you would hope to find them. Also some lookups for addressing the FreshbooksLines you may be interested in.

Then you have helpers get_all_draft_invoices, get_all_invoices_for_org_name, get_all_invoices_for_client_id, and get_draft_invoices_for_client_id.

Create an Invoice

The signature of invoice.create is like so:

def create(
    client_id: int,
    notes: str,
    lines: list[dict],
    status: str | int,
    contacts: list[dict] | None = None,
    po_number=None,
    create_date=None,
) -> dict:

lines

The dictionaries must contain entries for name, description, unit_cost, and qty. The values must be JSON-serializable, so no Decimals for example (all strings is fine).

contacts

Each of these dictionaries should simply be {'contactid': <contactid>}.

status

Status can be any of the v3_status values as a str or 1 or 4 (draft/paid).

Clients

get_all_clients, get_one, create, and delete are available here.

Once more the get... functions return NamedTuple instances with some helpful attributes, notably FreshbooksClient.contacts and a couple of related lookups (.contact_id_email_lookup and .email_contact_id_lookup).

Then, update_contacts, delete_contact, add_contacts, get_freshbooks_client_from_client_id, get_freshbooks_client_from_email, and get_freshbooks_client_from_org_name.

Install

pip install avt-fresh

Prerequisites/Configuration

Make yourself a nice little .env file in your home directory or wherever you're going to be calling this library's code. It needs to contain:

FRESHBOOKS_API_CLIENT_ID='blah'
FRESHBOOKS_API_CLIENT_SECRET='blah'
FRESHBOOKS_REDIRECT_URI="https://blah.com/blah"
FRESHBOOKS_ACCOUNT_ID="blah"

You can get and set these goodies here. Well, all of them except FRESHBOOKS_ACCOUNT_ID, which you can see (there's got to be another way??) by clicking on one of your invoices and grabbing the substring here: https://my.freshbooks.com/#/invoice/<THIS THING>-1234567.

Don't tell anyone but FRESHBOOKS_REDIRECT_URI can be pretty much anything! See Initializing below 👇.

Security

Which brings me to an important point. Currently it's going to save your OAuth tokens in the ever-so-insecure path of ~/freshbooks_oauth_token.json. TODO: don't do this anymore. ¯_(ツ)_/¯

Initializing

When you first call one of the functions which touches the Freshbooks API, you'll be prompted in the terminal like so:

Please go here and get an auth code: https://my.freshbooks.com/#/developer, then enter it here:

If you don't have an app there, create a really basic one. Name and description can be whatever, and you can skip the URL fields.

Application Type: "Private App" Scopes: admin:all:legacy

Add a redirect URI, it can actually be pretty much anything.

Finally, once you have an app on that developer page, click into it and click "go to authentication" page. Freshbooks will pop open a tab and go to your redirect URI, appending ?code=blahblahblah to it. Grab the "blah blah blah" value and paste it into the prompt.

You should only have to do this once in each environment you use this library in.

Hardcoded Stuff / TODOs

Here are some quirks and TODOs. PRs are welcome!:

Currently all invoices will have Stripe added as a payment option. There's no option to skip this, and there's no other payment methods available in this library.

Also, only Python 3.10 is supported at the moment.

Then, when it comes to invoice statuses, we're only using v3_status strings, not the numbers. What's more, when you create an invoice we're only supporting two possible statuses: "draft" and "paid".

The create, update, and delete functions return dictionaries rather than an instance of the appropriate NamedTuple. This would be a great improvement!

The docs need improvement for sure: For now, have a peek at the source code, which includes pretty comprehensive type hints at the very least.

There are no tests! Is the other thing. Although this code has been used in production in at least one company with some success.