Fichaloto

Integrations

A REST API you can actually build against

Forty-seven entities, four verbs, JSON in and JSON out, and a schema endpoint that tells your code what the columns are so you do not have to hard-code them.

The same entities as the bulk import, on purpose

Whatever you can download as CSV, you can read over the API, and with the same column names. That is not a coincidence: both come from a single registry in the code, so a field added to one appears in the other the same day.

It also means what the screen rejects, the API rejects. There is no second, laxer path into your data.

Ask the API what it looks like

GET /v1/meta returns the whole catalogue: which entities exist, what columns each has, which are required, which are references and what values they accept. Read it rather than copying it by hand — when we add a field, your integration finds out on its own.

References travel by name, not by our internal identifiers: a logged hour points at its person by email and at its project by code. Your system never has to store our IDs.

Keys that cannot do more than the person behind them

A key belongs to a person and inherits their role, and can additionally be marked read-only. Both have to allow an action for it to happen, so a key marked read-only stays read-only even if someone widens the role by mistake.

Keys are shown once, stored hashed, can be given an expiry date, and every call is attributed in the audit trail. Sessions are never accepted: identity comes only from the authorisation header, because an API that accepted cookies would be an API any web page could use in your name.

Frequently asked questions

Is the API an extra cost?

No. The API comes with the platform, like everything else, and there is no per-call or per-integration charge. If an endpoint you need is missing, tell us — proposals that would help more than one company go on the roadmap. What we do not do is build a one-off endpoint for a single case.

Can I give a dashboard read-only access?

Yes, and you should. Create a person for the integration, give them the read-only API role, and mark the key read-only too.

Is it rate limited?

There are sane limits to protect the service, and paginated listings with a date filter so you can pull only what changed instead of the whole table every night.

Getting started

Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.

What we have written about this

Keep reading