How to create user and company with API

Endret Mon, 22 Jun ved 11:42 AM

This guide is when 3rd party use Systima API anw want to create user and company.

Integrator provisioning API — onboarding flow

What you receive from Systima

Gateway token — a Bearer token shared with approved integration partners (Authorization: Bearer <token>).
clientId — your provisioning identity.
Provisioning key — your secret, shown once when issued (store it securely; we keep only a hash).

Flow

Call POST /external/onboarding with the three credentials above + the new user & company data.
Receive { userId, companyId, redirectUrl }.
Redirect the end-user's browser to redirectUrl. They land signed-in on the new company and are prompted to set their password. Done.

You never handle the user's password — Systima does.

{ 
  "user": { 
    "firstName": "Edvard", 
    "lastName":  "Munch", 
    "email":     "edvard@example.no",   // must be a real, unique address 
    "phone":     "+4721422121"          // optional 
  }, 
  "company": { 
    "name":                "Operahuset AS", 
    "type":                "AS",          // AS | ENK | ANS | DA | ... (org form) 
    "organizationNumber":  "999000111",   // required, unique 
    "phone":               "+4721422121", 
    "email":               "post@operahuset.no", 
    "billingEmail":        "faktura@operahuset.no", 
    "addressLine1":        "Kirsten Flagstads Plass 1", 
    "postalCode":          "0150", 
    "city":                "Oslo", 
    "country":             "Norway", 
    "vatPaymentFrequency": "MONTHLY"       // NONE | MONTHLY | BIMONTHLY | ANNUALLY 
    // optional: addressLine2, registeredAt (YYYY-MM-DD), sicCode, accountingStartDate 
  } 
}

Request

POST {API}/external/onboarding 
Authorization: Bearer <gateway-token> 
X-Provisioning-Client-Id: <your-clientId> 
X-Provisioning-Key: <your-provisioning-key> 
Content-Type: application/json

Response `200`

{ 
  "userId": "…", 
  "companyId": "…", 
  "redirectUrl": "https://app.systima.no/integrator_login#ticket=…" 
}

Open redirectUrl in the user's browser. The handoff ticket inside it is single-use and valid for ~60 seconds, so redirect promptly.

Errors

Code	Meaning
`401`	Missing/invalid gateway token
`403`	Missing/invalid provisioning credentials, or your access is disabled
`422`	Validation error, or duplicate email / organization number