Platform Readiness API
TheGET /v2/readiness endpoint provides an automated way to verify that all services and their dependencies (databases, Redis, brokers, etc.) are properly configured and reachable. It is the recommended first step after deploying or updating the platform.
Access
This endpoint is restricted to:- Super admins (authenticated users with the
superAdminrole) - Internal API key (via the
INTERNAL_API_KEYheader, used for service-to-service calls)
Usage
services query parameter accepts a comma-separated list to check only specific services. Valid values: api-gateway, runtime, events, workspaces.
Response
The endpoint returns a JSON response with an overallstatus (ready or error) and per-service details:
errors array with details:
What is tested
| Service | Modules tested |
|---|---|
| api-gateway | Can reach runtime, events and workspaces services. Redis cache, databases, broker, JWKS URI reachability |
| runtime | Redis cache, broker, permissions database, collections database, DSUL storage, searchengine reachable, custom code service reachable, gateway reachable |
| events | Redis cache, broker, permissions database, Elasticsearch (write & delete), gateway reachable |
| workspaces | Broker, permissions database, DSUL storage, gateway reachable |
| searchengine | Elasticsearch, Redis. Verifies it can create and delete an index |
| crawler | Elasticsearch, Redis, NO_PROXY=localhost check, gateway reachable. Verifies it can create and delete an index |
Results are cached for 30 seconds to avoid overloading services with repeated checks. You can configure the cache TTL with the
READINESS_CACHE_TTL_MS environment variable.Account Management
Create an Account
- Navigate to the Prisme.ai registration page.
- Complete the required fields (name, email, password, etc.).
- Confirm that the new account is created successfully.
Login
- Go to the Prisme.ai login page.
- Sign in with the credentials of the newly created account.
- Verify you can access the main platform dashboard.
Logout
- Ensure you can successfully log out of your account.
Pages
- Open the studio builder & create a workspace
- From the left menu, create a new page
- The technical slug will appear inside the page URL
- Add a simple text block to the page
- Save
- Verify that the text block is displayed correctly.
- Click the share button & open the page URL
- Verify that the same text block appears
Automations
- Open the created workspace
- From the left menu, create a new automation
- Open the green output block
- Type “Hello world” & save
- Execute the automation from the top right corner
- Verify you get the expected output
- Now open the blue trigger block
- Enable API trigger and save
- Copy the trigger URL which appeared inside the blue trigger block
- Open this URL inside a new tab & verify the output
- Return to the automation builder tab & click on “See code”
- Your automation manifest should appear in yaml format : try updating the output from here !
Apps
Publish an application
- Open the created workspace
- From the left menu open the 3 dots action list
- Publish as an app
Install an Application
- Come back to the studio builder in order to create a new workspace
- From the left menu, add a new app
- Install the previously published app
- Create a new automation
- Add an instruction & select the “Hello world” app automation you created before
- Type
outputin its output parameter - Open the green output block and type
{{output}} - Run the automation
- Verify you receive “Hello world”
Workspace Management
Workspace Share
- Try sharing the workspace you have created with another user.
Page share
- Create a new workspace.
- Try sharing the page you have created with another user.
- Verify that the other user can access the page but not the entire workspace.
Workspace settings
- Go to the workspace settings.
- Modify the name, description, and add a logo to your workspace.
Activity feed
- Open the activity feed
- Verify that all the operations you have performed are logged with associated data.
- Try filter suggestions
Workspace versioning
- Go to the workspace settings and add a version.
- Open the activity feed : a versioning event should have appeared, including a rollback action
- Create a new empty automation
- On the activity feed, rollback to the created version
- Verify the created automation has disappeared