Web App Generator
The Inspektlabs Web App Generator API enables the creation of fully customizable web applications for vehicle inspections, which can be delivered to customers via SMS or email. It supports both Photo Web Apps and Video Web Apps, offering flexible configuration options to add or remove sections, forms, questionnaires, or additional photo captures (such as the roof or wheel rims). The API also supports persona IDs to generate different app variations tailored to specific use cases, while white-labeling ensures the app can be branded according to customer requirements.
Please contact the Inspektlabs technical team to obtain your API key.
Base url
https://urlgen.inspektlabs.com/superappTokenClick the button below to download the Postman collection for the API.
Payload
{
"apiKey": "<YOUR_API_KEY>",
"personaId": "<customised_persona_id>"
}The above payload represents the minimal required fields for generating a URL or token. Additional fields, as shown below, are optional and only needed for specific use cases.
Please note that not all of the fields above may be relevant to you. The minimal fields required to generate a token or URL from this API are:
Parameters
Parameter | Description | Type | Required | Example |
apiKey | Secret key provided for authentication. Unique per clientId. | String | Yes | sk_abc123 |
personaId | Defines flow config provided by Inspektlabs. | Integer | Yes | 1 |
clientId | Account ID of the API consumer. | String | Optional | client_001 |
userDetails.phone | Phone number where the inspection link is sent. Format: +<country_code><number> | String | Optional | +919876543210 |
userDetails.email | Email ID where the inspection link is sent. | String | Optional | test@example.com |
inputMetaData.licensePlate | Vehicle registration number. Used for fraud/mistake validation. | String | Optional | MH12AB1234 |
inputMetaData.infoCarCode | Domus cost estimate integration code (region-specific). | String | Optional | DOMUS123 |
inputMetaData.vin | Vehicle Identification Number (VIN) / Chassis Number. | String | Optional | 1HGCM82633A123456 |
inputMetaData.agentId | Optional. ID of the agent handling inspection. | String | Optional | agent_101 |
inputMetaData.agentName | Optional. Name of the agent. | String | Optional | John Doe |
inputMetaData.tlId | Optional. Team Leader ID. | String | Optional | tl_202 |
inputMetaData.tlName | Optional. Team Leader Name. | String | Optional | Jane Smith |
Notes
- Token validity is limited (configured per client by Inspektlabs).
- Phone number must be in E.164 format:
+<country_code><number>.
Responses
Success Response
HTTP Status Code: 200 Success
{
"token": "Generated_Token",
"status": "true",
"message": "Token added successfully"
}Workflow: Automating Vehicle Inspections
1. Generate Token
- Call the Web App Generator with your credentials.
- On success, the API returns a secure token.
2. Capture Vehicle Media
- Option A: Share via SuperApp
- If
phoneoremailis provided, the system automatically generates and sends the inspection link to the customer. - Option B: Manual Link Creation
- If no phone/email is provided, you can generate the link yourself by appending the token to the SuperApp URL
https://superapp.inspektlabs.com/#<token>3. Inspection & Results
- The customer opens the SuperApp, captures required images/videos, and submits them.
- The inspection is processed and results are made available in the Results Portal for review and further actions.
cURL
curl -X POST "https://urlgen.inspektlabs.com/superappToken" \
-H "Content-Type: application/json" \
-d '{"apiKey":"sk_abc123","personaId":1,"caseId":"test"}'cURL for specific use cases
curl -X POST "https://urlgen.inspektlabs.com/superappToken" \
-H "Content-Type: application/json" \
-d '{
"apiKey": "sk_abc123",
"clientId": "client_001",
"caseId": "case_2025001",
"personaId": 1,
"userDetails": {
"phone": "+919876543210",
"email": "test@example.com"
}
}'Error Response
The API returns standard HTTP status codes along with a JSON response body indicating the reason for failure.
{
"status": "false",
"message": "Error description"
}Error Response Types
1. Missing API Key
Returned when the API key is not provided in the request.
HTTP Status Code: 403 Forbidden
{
"status": "false",
"message": "Forbidden: Invalid Request"
}2. Invalid API Key
Returned when the provided API key is incorrect or unauthorized.
HTTP Status Code: 401 Unauthorized
{
"status": "false",
"message": "Unauthorized: Invalid API Key"
}3. Client ID Mismatch
Returned when the provided client ID does not match the associated API credentials.
HTTP Status Code: 400 Bad Request
{
"status":"false",
"message":"Client ID mismatch"
}4. Internal Error During API Key Verification
Returned when an internal server issue occurs during API key validation.
HTTP Status Code: 500 Internal Server Error
{
"status":"false",
"message":"Internal Server Error: During API KEY Verification"
}5. Generic Internal Server Error
Returned when an unexpected internal server error occurs.
HTTP Status Code: 500 Internal Server Error
{
"status":"false",
"message":"Internal server error"
}Notes
- Ensure the API key is passed correctly in the request headers.
- Verify that the
client_idmatches the credentials associated with the API key. - For repeated
500errors, please contact support or retry after some time.
On this pag
- Web App Generator
- Base url
- Payload
- Parameters
- Notes
- Responses
- Success Response
- Workflow: Automating Vehicle Inspections
- 1. Generate Token
- 2. Capture Vehicle Media
- 3. Inspection & Results
- cURL
- Error Response
- Error Response Types
- 1. Missing API Key
- 2. Invalid API Key
- 3. Client ID Mismatch
- 4. Internal Error During API Key Verification
- 5. Generic Internal Server Error
- Notes