Tyk v2.2 Documentation Components

HomeTyk v2.2 Documentation ComponentsTyk Portal: Monitisation

Tyk Portal: Monitisation

Out of the box, the Tyk Developer Portal does not have a billing component, however, this does not mean that it is not possible to enable monitisation within a portal developer access flow.

The Developer Key Request Flow

When a developer enrolls for API access with a Tyk portal system, they will:

  1. Sign up
  2. Select a catalogue entry to participate in
  3. Submit a key request form
  4. Receive their token

With Tyk, it is possible to prevent step 4 which auto-enables the token, and instead have the developer redirected to a third party app, this app can then handle any transactional process such as taking a credit card number or pre-validating the developer, before returning the developer to the portal.

When Tyk hands off to the redirected app, it will also add the key request ID to the request, so the application that handles the transaction can then use the Tyk Dashboard REST API to approve the key request (triggering the email that notifies the developer of their token, as well as notifying the calling application of the raw token), closing the loop.

To enable the developer hand-off in a Tyk Portal, browse to the portal Settings screen and enable the redirect option:

enter image description here

Was this article helpful to you? Yes No