AI marchex-service

A micro-service for wrapping interactions with the Marchex API.

GET requests to the routes should provide help/usage information. All programmatic interactions
should be conducted with other http methods (primarily POST at this time).

Every post request needs to contain the following headers:

Headers:
litecrypt-secret: encrypted secret
litecrypt-user: encrypted api user (for Marchex)
litecrypt-password: encrypted password (for Marchex api user)

Where the plaintext values should be encrypted in the AI litecrypt pattern. User and password 
are those values for the Marchex API user. Secret is the automatit service secret. 

For those interactions that are querying a specific entity (account/call) the identifier for that 
entity will be provided as the first uri-segment following the route segment(s). E.g. for the /calls/ route 
the full url would be:

https://[base url]/calls/[account]

Further arguments (if required) will mostly be passed in the POST request's body. Example:

Body:
{
    groupId: ?<string> group id to filter the results by
}

The currently supported routes/service interactions:
/call/[call id] - detailed information about a specific call
/calls/[account] - list of calls made against an account constrained by a specific range
/accounts - a list of all accounts the Marchex API user has access to
/groups/[account] - a list of groups in the specified account (for most accounts a group is equivalent to a facility)
/phone-numbers/[account] - a list of call tracking numbers in an account