Skip to main content
Skip table of contents

TB.Connect API

Many of the administrative functions are exposed through RESTful APIs, including:

  • management of user attributes

  • management of users and provisioning

  • management of identity and service providers

  • management of authentication schemes

  • management of access policies

  • computing a user's access rights for a URL

  • management of mail and web templates

  • management and validation of Digipass tokens linked to the user model 

  • management of various settings

  • self-service calls

  • branding.

Authentication and Authorization Flows

Noticeably absent from the previous list is the functionality to start  the necessary authentication and authorization flows when accessing a  service. These flows are handled by the Orchestrator. The Orchestrator also manages sessions.

Accessing REST Calls

For reasons of backwards compatibility, please note that the APIs are named idhub rather than tbconnect.

The REST API is organized in five parts:

API

Path

Comment

Admin

hostname/idhub/admin/api/v1/*

Requires a session (optional authorization rules may apply)

Installation

hostname/idhub/installation/*

No session required

Login

hostname/idhub/login

Basic user / password authentication only

Public

hostname/idhub/public/api/v1/*

No session required

Self-service

hostname/idhub/selfservice/api/v1/*

Some calls require a session

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.