IA IAM Bajan Request access
Kitji Studios platform

Controlled integration for approved Barbados services.

IAM Bajan gives approved businesses, developers and government agencies a structured way to request access, integrate responsibly and operate within a clearly defined data-use boundary.

Request controlled access Read the integration guide
Designed for institutions

One controlled path from request to integration.

IAM Bajan is not a public people-search service. It is a governed integration platform for organisations with an approved, lawful and documented use case.

⌘

Businesses

Support approved onboarding, record-quality and operational reconciliation workflows without exposing a broad data console.

</>

Developers

Integrate authorised systems through documented APIs, short-lived credentials and clear technical onboarding.

▣

Government agencies

Enable controlled statutory and service-delivery workflows with an accountable approval and audit trail.

Pricing

Plans that reflect a controlled activation model.

All plans are subject to organisation verification, intended-use review, manual invoicing and activation. Published prices are in Barbados dollars.

Approved access

Integration Access

For approved developers and small teams integrating a defined use case.

BBD 99 / month
BBD 999 annually
  • Manual organisation review
  • Controlled onboarding
  • Named technical contact
  • Documentation access
Request access
Operational workflow

Verified Business

For established organisations with an approved operational workflow.

BBD 299 / month
BBD 2,999 annually
  • Approved production use case
  • Organisation-level review
  • Usage controls
  • Priority onboarding support
Request access
Contracted service

Institutional & Government

For ministries, agencies, regulated institutions and higher-scale integrations.

Custom pricing
Scoped by agreement
  • Contracted scope
  • Custom usage controls
  • Data-use review
  • Designated support contacts
Discuss your requirement
Approved use cases

Use data only where it has a legitimate, defined operational purpose.

Final approval depends on your organisation, documented use case, contractual scope and the authority responsible for the underlying information.

✓

Authorised record reconciliation

Confirm information supplied within an approved customer, constituent or case workflow.

↔

Institutional onboarding

Improve accuracy and resolve duplicates within an organisation's established, authorised process.

▤

Government service delivery

Support defined statutory, case-management and public service workflows under applicable authority.

How it works

A review-led route to production access.

IAM Bajan is intentionally designed to prevent an unverified request from turning into a live integration credential.

01 / REQUEST

Tell us who you are

Submit a business email, organisation details, selected plan and intended use.

02 / REVIEW

We verify the request

Kitji reviews the organisation, proposed use, authority and commercial fit.

03 / ACTIVATE

Manual commercial activation

Invoice and contractual steps are completed before approved access is provisioned.

04 / INTEGRATE

Use controlled credentials

Your named technical contact receives the approved integration path and security guidance.

Integration whitepaper

Start safely, then integrate only the approved scope.

This is the customer-facing onboarding path. Full endpoint references are provided only after approval so public documentation never becomes a data-discovery tool.

Your integration checklist

  1. 1
    Request accessSelect a plan, name your organisation and explain the intended use.
  2. 2
    Complete reviewConfirm the business need, authority, contractual scope and manual billing arrangement.
  3. 3
    Receive approved credentialsStore credentials only in a secure server-side secret store. Never place them in browser code.
  4. 4
    Request a short-lived tokenUse the approved client-authentication flow and the exact scopes assigned to your organisation.
  5. 5
    Handle results responsiblyUse minimum required fields, protect responses, record audit events and respect your retention commitments.
Illustrative integration sequenceServer to server only
# 1. Store credentials in your server-side secret store.
IAM_BAJAN_CLIENT_ID=approved-client-id
IAM_BAJAN_CLIENT_SECRET=never-in-browser-code

# 2. Request a short-lived token through the approved flow.
POST <approved-token-endpoint>
Content-Type: application/json

{
  "clientId": "approved-client-id",
  "clientSecret": "stored-server-side"
}

# 3. Use only approved endpoints and scopes.
Authorization: Bearer <short-lived-token>

# 4. Handle 401, 403, 429 and validation failures.
#    Do not log raw credentials or returned personal data.
Data use

Clear boundaries protect people, organisations and the platform.

Applicants must acknowledge these requirements before an access request can be submitted. Service terms and final contractual controls will apply to every activated subscription.

Permitted, subject to approval

  • Authorised identity and record reconciliation
  • Defined government-service and statutory workflows
  • Institutional onboarding and record-quality processes
  • Approved aggregate or public-interest planning use
  • Secure integration within the documented scope

Strictly prohibited

  • Political campaigning, voter targeting or political profiling
  • Direct marketing, lead generation, scraping or public people-search tools
  • Data resale, unauthorised onward disclosure or bulk extraction
  • Use in housing, employment, credit or insurance decisions without express authority
  • Training AI models with identifiable response data