Configure an AlgaPSA API User
TopLeft reads and updates your AlgaPSA tickets, projects and clients with an API key. Set up a user for it, make the key and connect TopLeft.
TopLeft reads your AlgaPSA tickets, projects, clients, people and time, and writes changes made in TopLeft back to AlgaPSA. It connects through the AlgaPSA REST API with an API key, over TLS. This works with hosted AlgaPSA and with a self-hosted appliance.
Before you start
- An AlgaPSA administrator, to set up the user and its role.
- Your AlgaPSA address:
https://algapsa.comfor hosted, or your appliance's own address. A self-hosted appliance must be reachable from the internet, because TopLeft calls its API from TopLeft's servers. - At least one time period in AlgaPSA's time period settings covering the dates you'll log time against. Without one, AlgaPSA refuses every time entry, from TopLeft or anywhere else.
Set up a user for TopLeft
An AlgaPSA API key acts with the permissions of the user who made it. AlgaPSA also files the time, notes and files TopLeft writes under that user. Make a user just for TopLeft, so its work is easy to tell apart from your team's.
- In AlgaPSA, add a user named TopLeft.
- Give it a role that can read and change tickets, projects and project tasks, task comments, clients, contacts, time entries and time periods, and read boards, statuses, priorities, categories, services, users and teams.
- Sign in to AlgaPSA as that user and open the profile page at
/msp/profile. - Under API Keys, make a key. AlgaPSA shows it once, so copy it now.
Connect TopLeft
- Enter your AlgaPSA address and the key on the TopLeft setup page.
- TopLeft checks the key against each kind of record it needs and lists any it can't read. Widen the role in AlgaPSA and check again until the list is clear.
- Pick the boards and projects your team works from, and invite your team.
Let each tech use their own key
Without their own key, a tech's time and notes are filed in AlgaPSA under the TopLeft user, with a line in the note saying who wrote it. To have their work filed under their own name, each tech makes a key on their AlgaPSA profile page and saves it in their TopLeft account settings, under Your AlgaPSA key. TopLeft shows the last four characters of the key it is using.
Webhook
AlgaPSA tells TopLeft about each change through a webhook, so cards update within seconds. Without it, changes still arrive with the regular sync, just later.
An administrator sets it up on the PSA API page in TopLeft settings, with Set up the webhook. If AlgaPSA refuses, the page shows the address, method and events to enter in AlgaPSA by hand, under Security settings, Webhooks, and a field for the signing secret AlgaPSA gives you.
On a self-hosted appliance, the webhook needs the appliance to reach TopLeft over the internet. If it can't, cards still update with the regular sync.
What doesn't sync
- Task dependencies. AlgaPSA's API doesn't share task dependencies, so TopLeft keeps its own links between tasks on the Gantt chart. Dependencies set in AlgaPSA don't show in TopLeft, and links made in TopLeft don't show in AlgaPSA.
- Client visibility of files. AlgaPSA marks files uploaded through TopLeft as internal, so clients don't see them in AlgaPSA's own portal.
Updated November 20, 2026

Comments
No comments yet.