Developer Help Center

Implementation Models

Revelator is a highly customizable application which is relevant for many use cases.

Child Account Model

For API implementations using the child account model, tasks are performed within a user's personal Revelator account.

  • Partner application will create a new user and child account in the Revelator system for each of the partner's users. All child account assets (releases and tracks) will appear in the partner tenant.

  • Partner can choose to authenticate their users with or without their knowledge or involvement (prompted or unprompted authentication).

  • Partner will perform administrative tasks, such as inspecting release metadata, in the partner tenant in the Revelator web interface.

    API access is possible for partners building their own administrator application. Please contact support for details.

  • Partners on API plan C will additionally perform administrative tasks via the API in their partner tenant, such as managing contracts.

  • Required model for any use case which involves directing your users to the Revelator web interface.

Single Tenant Model

For API implementation using the single tenant model, all tasks will be performed in the partner tenant.

Note

Upon onboarding, Revelator will provide you with a partnerUserId, in addition to your API key and Enterprise ID.

  • Partner does not signup each user individually in the Revelator system (does not use the signup resource).

  • Partner will always authenticate in the Revelator system without the users knowledge/involvement ( will always uses unprompted authentication).

  • Partner will perform administrative tasks, such as inspecting release metadata in the Revelator web interface.

    API access is possible for partners building their own administrator application. Please contact support for details.

  • Recommended for customers building complete applications who will never direct their users to the Revelator web interface.