Developer docs
TribePeer for organisations

A classroom API with a proper front door

This is the engineer’s guide — not the sales page. You will connect a portal, a widget, or a Campus shell to one engine: tribes, materials, enrollments, chat, and an optional AI tutor.

Base URL: https://www.tribepeer.com/api. Send JSON. Organisation calls use a partner token. Learner calls use a user token. Never put a client secret in a browser, a NEXT_PUBLIC_* env, or a desktop webview.

First hour

1

Create trial access

From a Tribe Owner workspace, issue a trial key. That is enough to integrate. Production students wait until you go live.

2

Exchange the secret on your server

POST the client id and secret to /api/partner/v1/auth/token. Cache the JWT. It lasts about an hour. See the Organisation auth section.

3

Let people sign in as themselves

Learners and staff use /api/product/v1/auth/*. A token is issued only after the email is verified. Scope Campus or widget calls with X-Institution-Uuid.

Two tokens, on purpose

Organisation automation (create a class, grade a paper, set branding) uses the partner token. Humans walking through Campus, the widget, or your own UI use a user token. Mixing them is how secrets leak and how gradebooks go missing.

Partner token →  ·  Learner token →

Full API reference

Request bodies, response JSON, scopes, and samples in cURL, JavaScript, PHP, and Python:

Website embed

Publishable keys (pk_test_ / pk_live_) are origin-locked. The public widget is Ask TribeMate and does not require a login. Forum chat, quizzes, and assignments stay on Campus and the Product SDK with a user token. A pk_test_ key always shows TEST MODE.

HTML
<script
  src="https://www.tribepeer.com/widget.js"
  data-key="pk_…"
  data-mode="ask"
  async></script>

Widget UI is ₦3,000 / month. Removing the TribePeer badge is ₦5,000 / month. Both together ₦8,000. TEST MODE cannot be paid away on a test key.

Campus and self-host

Point a Campus shell at your API URL. Branding is stored on the institution via PATCH /api/partner/v1/me/branding. Desktop builds keep secrets in the OS keychain.

Open-source shells only render UI. Enrollment, grading, AI, caps, and billing stay on TribePeer. A clone that grows its own course table has left the product.

Support

Ready-made products (Campus, website widget, WordPress, a branded launch) start from the request form — a person fulfils them. Live access and the AI tutor for an app you already built are paid from your Tribe Owner workspace.

Talk to us AI reference