Skip to content

Limits, logging and correlation ​

Salaxy publishes few hard limits. This page lists the ones that are stated, says what to log in your integration, and says what to send Salaxy when you need a server-side log lookup. Examples use the test environment; see Environments for demo and production.

Logging on both sidesYour system calls the Salaxy API and logs every request with its own reference, the Salaxy ids from the response and the time. Salaxy logs the request on its side. When something fails, you send Salaxy the request time and the account id, and Salaxy looks up the server-side log.YOUR SYSTEMLog each callyour reference, Salaxy ids,status code, timeSalaxy APIlogs the request toorequesttime + account id on a failure
Log both sides of every call. For a failure, Salaxy needs the request time and the account id to find the server-side log.

Limits that are stated ​

AreaLimitSee
RateNo rate limit or Retry-After is published today, so there is no 429 handling to implement. Poll at a sensible intervalErrors, Polling
List page sizeAt most 50 items per page (1000 on the Pro API). Follow nextPageLink until it is missing. $top above the page size returns 400Queries
Access token lifetime48 hours, no refresh tokens. Repeat the grantREST authentication
Field lengths and formatsPer the API reference. Validation failures name the fieldREST API reference, Errors
IdempotencyNo general idempotency key. Endpoint-specific onlyRetries and idempotency

Two limits apply only to v04 beta endpoints, see Versions and Payment channels:

  • A data funnel file upload is at most 10 MB, and only csv, tsv, txt, jsonl, xlsx, xls, ods and pdf files are accepted.
  • A payment message create accepts an Idempotency-Key header: the same key and body within 24 hours returns the original message, and the same key with another body is refused.

No limit is published for request size or for requests per minute.

Logging on your side ​

The API documents no correlation header, so build your own trail:

  • Your own reference. Keep a reference for every operation and store it with the Salaxy id you get back. A retried create then does not need a guess; see Retries and idempotency.
  • Salaxy ids. Log the id of every object you create or read (calculation, payroll, invoice, employment) and the account id you acted as.
  • Request and response. Log the method, path, HTTP status and time. Log the error and validation parts of a 400 body. Never log tokens or private keys.
  • Personal data. Payroll responses and SEPA files carry names and bank accounts. Keep them out of general logs.

Asking Salaxy for a server-side log lookup ​

Send the time of the request (with time zone) and the account id you acted as, plus the Salaxy id of the object if you have one. Use the contact channel agreed in your project; see Support.

Checklist ​

  • Your code does not assume a rate limit header and does not loop on 429.
  • Every list read follows nextPageLink and does not use $top.
  • You log your own reference, the Salaxy id, the account id, the status and the time of every call.
  • Tokens, keys and personal data stay out of your logs.
  • You can give Salaxy the request time and account id for any failed call.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.