Api authorisation

Closes #63 
Hey @devcritter. This is currently happening at the database level. What happens is a DB request to only pull the `limit` amount is made. So if I set the `limit` to 100 then only 100 records are returned to node. The `sort` is on timestamp -1 (DESC) so records are ordered from the latest to oldest. What the `skip` does is start at a specific point in the database. 

So say the limit is 100, page 1 will start from `skip` 0 and return the first 100 results (1 - 100), page 2 will start `skip` 100 and bring back the next 100 records (101 - 200). The new results of records are then added to the transaction scope and into the table. The main reason why I did it this way it to prevent a very long initial load of transactions. If this is the wrong way of doing let me know and ill work on correcting it