TeamSystem

Partner credentials required. TeamSystem's APIs are published through its developer portal but issued per integration partner and per product line (TeamSystem Enterprise, TS Digital, Alyante, …). You will not find a self-service key in the product UI, and there is no public sandbox — which is why this adapter ships unverified.

Setup

1. Register at developer.teamsystem.com and have your TeamSystem partner enable the APIs for your customer's tenant.
2. Create an application and note the client id and client secret.
3. Note the tenant id that scopes your customer's data. Set TEAMSYSTEM_CLIENT_ID, TEAMSYSTEM_CLIENT_SECRET and TEAMSYSTEM_TENANT_ID.

Client credentials, scoped per product. The token endpoint is https://auth.teamsystem.com/oauth2/token and the scopes on your application decide which of the paths below answer. A 403 here is almost always a missing scope rather than a bad secret.

X-Tenant-Id on every call. TeamSystem multiplexes many customers behind one API host; the tenant header is what picks one. A wrong tenant returns an empty result, not an error.

Italian tax vocabulary applies. Documents carry partitaIva and codiceFiscale, and invoices going through the Sistema di Interscambio carry an e-invoice status. A rejected (scartata) invoice has not legally been issued.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.