...
Service | API | Method | Data Model | Workflow | Group |
---|
multitenant | /product/package/acl/api | GET | Products | N/A | Product |
Description
Get the ACL of a specific api in the product package
Input
...
Code Block |
---|
Type: application/json |
Name | Source | Mandatory | Type | Special Format | Description |
---|
productCode | Query | YES | String | | The product code |
packageCode | Query | YES | String | | The package code |
mainEnv | Query | YES | String | | |
secEnv | Query | NO | String | | |
page | Query | NO | integer | | |
Output
...
Response
SOAJS has a unified response. Check out this link to understand more the schema of SOAJS response
Valid Response
Expand |
---|
|
Code Block |
---|
| {
"result": true,
"data": {
"package": "TROD_BASIC",
"product": "TROD",
"acl": [{
"service": "micro1",
"version": "1.2",
"group": "calendar",
"method": "post",
"api": "/v1/domain",
"envs": {
"dev": true
},
"access": {
"dev": true
},
"restriction": {
"dev": true
}
}, {
"service": "micro1",
"version": "1.2",
"group": "calendar",
"method": "post",
"api": "/v1/schedules/:scheduleId",
"envs": {
"dev": true
},
"access": {
"dev": false
},
"restriction": {
"dev": true
}
}, {
"service": "micro1",
"version": "1.2",
"group": "calendar",
"method": "post",
"api": "/v1/schedules/:scheduleId/approvals",
"envs": {
"dev": true
},
"access": {
"dev": false
},
"restriction": {
"dev": true
}
}],
"aclTypeByEnv": {
"dev": "granular"
}
}
} |
|
Invalid Response
Code Block |
---|
{
"result":false,
"errors":{
"codes":[460],
"details":[
{
"code":461,
"message":"Unable to find package"
}
]
}
} |
|
Response schema
Follow this link to check out the response JSON Schema
SOAJS Error Codes
...
Code | Description |
---|
400 | Business logic required data are missing |
461 | Unable to find pacakge |
602 | Model error: + %model_error% |