Skip to content

API reference

Learning platforms

TalentLMS, 360Learning, Docebo and Moodle: who Bizisy keeps in the platform and what the next sync does for each person (new accounts, changes, deactivations). Confirming or excluding people happens in the web app; connecting and settings are integrations. Course tasks are checklist tasks done in the platform.

2 actions · base URL https://api.bizisy.com/v1 · generated from the same definitions as the API.

People in a learning platform#

POST/v1/org/learning.peopleRead

For one learning platform (TalentLMS, 360Learning, Docebo, Moodle): everyone Bizisy keeps there and what the next sync does for each: create (waiting: HR confirms it first; reason existing = already working here when the platform was connected, confirm = the create mode asks HR), update, deactivate (their last day has passed), reactivate, scheduled (created on date, days_before their first day), in_sync, excluded (HR chose to leave them out), deactivated. Counts by kind. Owners, admins and HR; never custom roles. Not connected: an empty list. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Who can call it
Manage key owner admin hr
MCP tool
org_learning_people on HR Assistant
Method
POST with a JSON body, or GET with the input as query parameters

Input

  • connector"talentlms" | "learning360" | "docebo" | "moodle"required

    The learning platform: talentlms, learning360 (360Learning), docebo or moodle.

Returns

  • connectedbooleanrequired
  • provisionbooleanrequired
  • countsobjectrequired

    People per kind.

    8 fields
    • createintegerrequired
    • updateintegerrequired
    • deactivateintegerrequired
    • reactivateintegerrequired
    • scheduledintegerrequired
    • in_syncintegerrequired
    • excludedintegerrequired
    • deactivatedintegerrequired
  • waitingintegerrequired

    Creations and reactivations waiting for HR.

  • peopleobject[]required
    9 fields
    • person_idstringrequired
    • namestringrequired
    • job_titlestring | nullrequired
    • teamstring | nullrequired
    • kindstring (enum)required

      One of: create, update, deactivate, reactivate, scheduled, in_sync, excluded, deactivated.

    • waitingbooleanrequired
    • reason"confirm" | "existing"required
    • datestring | nullrequired
    • linkedbooleanrequired

Errors

validation_failed unauthenticated forbidden not_found rate_limited internal

curl
curl https://api.bizisy.com/v1/org/learning.people \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"connector":"talentlms"}'
Response
{
  "data": {
    "connected": true,
    "provision": true,
    "waiting": 1,
    "counts": {
      "create": 1,
      "update": 0,
      "deactivate": 0,
      "reactivate": 0,
      "scheduled": 1,
      "in_sync": 2,
      "excluded": 0,
      "deactivated": 0
    },
    "people": [
      {
        "person_id": "p5",
        "name": "Inês Martins",
        "job_title": "Designer",
        "team": "Design",
        "kind": "create",
        "waiting": true,
        "reason": "confirm",
        "date": "2026-10-12",
        "linked": false
      },
      {
        "person_id": "p6",
        "name": "Rui Lopes",
        "job_title": "Engineer",
        "team": "Engineering",
        "kind": "scheduled",
        "waiting": false,
        "reason": null,
        "date": "2026-11-28",
        "linked": false
      },
      {
        "person_id": "p1",
        "name": "Ana Costa",
        "job_title": "CEO",
        "team": null,
        "kind": "in_sync",
        "waiting": false,
        "reason": null,
        "date": null,
        "linked": true
      },
      {
        "person_id": "p2",
        "name": "Bruno Dias",
        "job_title": "Engineer",
        "team": "Engineering",
        "kind": "in_sync",
        "waiting": false,
        "reason": null,
        "date": null,
        "linked": true
      }
    ]
  }
}

Confirm or exclude people for a learning platform#

POST/v1/org/learning.chooseWrite

For one learning platform: confirm (their account is created, or brought back, at the next sync, which starts right away), exclude (Bizisy never creates, changes or deactivates their account there; training courses still enrol them if they already have one) or include again (undo an exclusion or a confirmation). Up to 250 people at once. Owners, admins and HR, in the app only; never custom roles. Refused when the platform is not connected. New joiners are created 14 days before their first day at most. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Web app only
Refused for API keys and connected apps. A person confirms or excludes people for a learning platform in the app (Integrations → the platform → People).
MCP tool
org_learning_choose on HR Assistant
Preview
?dry_run=true runs every check and saves nothing
Retries
An Idempotency-Key prevents a second run, but the result is never stored (it holds a secret or personal data): a retry gets a 409 that points to Activity

Input

  • connector"talentlms" | "learning360" | "docebo" | "moodle"required

    The learning platform: talentlms, learning360 (360Learning), docebo or moodle.

  • person_idsstring[]required

    1–100 characters. 1–250 items.

  • choice"confirm" | "exclude" | "include"required

Returns

  • changedintegerrequired

Errors

validation_failed unauthenticated forbidden not_found conflict rate_limited internal

curl
curl https://api.bizisy.com/v1/org/learning.choose \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"connector":"moodle","person_ids":["p5","p6"],"choice":"exclude"}'
Response
{
  "data": {
    "changed": 1
  }
}

Something missing or wrong on this page? Write to hello@bizisy.com.

Developer docs