Skip to content
TapLogic API
Italiano

Authentication

Every request carries a company API key in the Authorization header, with the Bearer scheme.

curl "https://api.taplogic.it/v1/members" \
  -H "Authorization: Bearer $TAPLOGIC_API_KEY"

Live keys and test keys

tl_live_… keys work on real data. tl_test_… keys see only demo tags and their scans, receive events on test endpoints and cannot invite or remove people. The code is the same: only the key changes.

Scopes

Each key has only the scopes chosen at creation. A request outside them answers 403 insufficient_scope and the param field names the missing scope.

ScopeWhat it allows
tags:readRead tags and actions (GET /tags, GET /actions).
tags:writeAssign a tag, set its action, deactivate it.
members:readRead members and seats (GET /members, GET /seats).
members:writeInvite and remove members. Live keys only.
scans:readRead scans (GET /scans).
webhooks:writeCreate, update, test and delete webhook endpoints.

Keeping keys safe

  • The key is shown once, at creation. TapLogic keeps only a fingerprint (hash): nobody can read it back.
  • Use it only from your server. Never in a mobile app, a web page or a repository.
  • One key per system, with the fewest scopes: if a system is compromised, you revoke only that key.
  • Revoking in Settings → API and webhooks takes effect at once.

Missing or invalid key

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="TapLogic"

{
  "error": {
    "code": "invalid_api_key",
    "message": "La chiave API non è valida, è scaduta o è stata revocata.",
    "doc_url": "https://docs.taplogic.it/it/errors#invalid_api_key",
    "request_id": "req_Qm3Xc81ZpRt0aBcYvWsK"
  }
}