oto.cx
silae

silae

silae.

A payroll dossier — what the key reaches, or one dossier's settings.

ajouter à otoauth : —prefix : silae_*

setup & usage

⚠ your silae paie api access

silae paie v1 uses oauth2 credentials with three fields; each firm/employer enters their own, and their payroll is visible only to them. they come from the silae api portal (api-portal.silae.fr), the dossiers being opened to the api from silae itself (an "api access configuration").

  • client_id — the api account's identifier
  • client_secret — the associated secret
  • subscription_key — the key of the api access configuration: it decides which dossiers AND which functions are reachable. a dossier missing from silae_dossier() may simply be outside it

    • enter these three fields in your oto connector keys under silae

  • the silae contract decides the functions: "usage interne paie" (model 1A) or "usage interne rh" (1B) open everything this connector reads; "mise à disposition" (model 2) does not open silae_dossier(op="organisms") nor silae_declaration (dsn list, dsn content, declaration states)
  • avoid calling between 1am and 5am: silae refreshes its platforms then
    • ▸ from the dossier to the payslip line

    every call targets one dossier (numero_dossier); pay months are written AAAA-MM (2026-05), a range is periode_debut + periode_fin (both included).

  • silae_dossier() lists the reachable dossiers; op="current_period" the open month, op="establishments", op="organisms" (urssaf, pension, provident… with their affiliation)
  • silae_employee() lists the employees (periode="2026-05" keeps those active that month); op="get" reads one employee's record; op="jobs" gives each job's identifiant_emploi
  • a payslip is addressed by matricule + `identifiant_emploi` + month + `indice_periode`: an intermittent holds several jobs in a month, and a job can have several payslips (supplementary, profit-sharing) — silae_payslip(op="indices") lists them, index 0 being the first one
  • silae_payslip(op="header") gross, net, deduction totals; op="lines" every line with employee/employer base, rate, amount and DUCS code (line_filters to keep a zone, a DUCS code, a label with %); op="totals" cumulative totals over 12 months at most
  • silae_payslip() (op pdf_ids) only returns the ids of the payslip PDF images, not their content
    • ▸ reconcile the charges table with the DSN
  • silae_report(report="charges_table", periode="2026-05") — the charges table; report="contributions_detail" the contributions detail (12 months at most, detail_salaries=True per employee); report="declaration_summaries" the month's declaration summaries (pdf). format="xlsx" returns the spreadsheet as csv to read; a pdf comes back as its text, the original file as a temporary raw_url
  • a heavy report: op="start" returns a task_id, then op="status" until ETAT_TERMINEE
  • silae_declaration(periode="2026-05") lists the month's dsn (establishment, body, type_dsn, fraction); op="dsn_content" with those values reads one dsn, whole or only segments (["S21.G00.30"]); op="states" the declarations and their returns (ads, ars…)
    • · personal data and documents

    nothing is masked by default: employee records, payslips and the dsn carry names, nir and pay in clear until the org sets a field-filter policy for silae. a filter cannot see inside a file, so reports and dsn contents are refused while that policy masks anything.

    the connector never writes to silae: no variable element, bonus, hours, entry confirmation, payslip control nor declaration setting goes out of it.

    ⚙ multiple comptes

    this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.

  • the first one doesn't need a name; from the second on, each one carries its own (the first then takes the name "principal", renamable)
  • without specification, the agent takes the only stored compte, otherwise the one marked as default; otherwise the call is refused, naming the available comptes — never a random choice
  • target a compte for a call: _account="<name>" on the tool; list them: oto_identity(op='list', connector='silae') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='silae', identity_id='<name>'); rename: op='rename' with new_name
  • ⚠️ no tool walks through the comptes on its own: a total across several comptes is obtained by calling each one (_account) and adding up

    • outils

    chargement…

    utilisation

    claude code — installe le plugin oto — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.
    claude.ai — branche mcp.oto.cx/mcp en connecteur custom (guide)
    cli — pipx install oto-cli puis oto silae …
    ← tous les connecteurscatalogue mcp →