developers · api-first

Build on the platform,
not around it.

Everything the fkra apps do goes through the same REST API you get — organizations, paths, modules, progress. Wire it into your stack, not the other way round.

Start using fkra ↗For your company

Three calls to a running academy

Create the org, enroll the team, read the progress. That is the API.

Create the organization

One POST — tenant, locale and theme. The org exists.

cURLTypeScriptResponse

curl -X POST https://api.fkra.ai/v1/orgs \
  -H "Authorization: Bearer sk_live_…" \
  -d '{ "name": "Acme Academy", "locale": "ar" }'

curl -X POST https://api.fkra.ai/v1/orgs/org_7f3/enrollments \
  -d '{ "pathId": "path_leadership", "userIds": ["u_812"] }'

curl https://api.fkra.ai/v1/orgs/org_7f3/progress?path=path_leadership

Enroll the team

Attach people to a path; prerequisites and notifications fire on their own.

cURLTypeScriptResponse

const fkra = new Fkra({ apiKey: process.env.FKRA_KEY });

const org = await fkra.orgs.create({
  name: 'Acme Academy',
  locale: 'ar',
});

await fkra.enrollments.create(org.id, {
  pathId: 'path_leadership',
  userIds: ['u_812'],
});

const progress = await fkra.progress.list(org.id);

Read the progress

The same numbers the dashboards render — completion, scores, evidence.

cURLTypeScriptResponse

201 Created

{
  "id": "org_7f3",
  "name": "Acme Academy",
  "locale": "ar",
  "rtl": true,
  "audit": {
    "actor": "api:sk_live_…",
    "action": "org.created"
  }
}

Define your own module types

A module type is a pair of JSON schemas — config and body. Ship a new interactive format without waiting on us: the studio forms and the player pick it up from the schema.

Tenants and scopes, for real

Every organization lives in its own tenant, and every admin action needs the right scope. The isolation the government tier runs on is in the core — not a bolt-on.