Access Control
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Get the list of actions based on the input parameters.
Request info for getting actions.
unique API ID
API version
response timestamp YYYY-MM-DDThh:mm:ss+/-nn:nn (timezone defaulted to +5.30)
api action like GET/POST/PUT/DELETE in case of http calls
device UUID from which API is called
API key (dynamic)
unique request message id, UUID, for handling API idempotency
UserId of the user calling
//session/jwt/saml token/oauth token
Successful response
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
To create new Role(s) in the system.
Details for the new role(s) + RequestInfo meta data.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Role(s) created sucessfully
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
Get the list of roles based on role codes in the input parameters.
Request info for getting actions.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Successful response
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
To create new action(s) in the system. An action entry is required for each and every path to authenticate the access based on the assigned role of an user.
Details for the new Action(s) entry + RequestInfo meta data.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
action master
if enabled or not
unique id for feature
left icon
url for navigating
right icon
codes specifying role
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
Action(s) created sucessfully
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
To update the existing role(s) in the system.
Details for the Role(s) entry with new values + RequestInfo meta data.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Update role(s) successful
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
To update the existing action(s) in the system.
Details for the Action(s) entry with new values + RequestInfo meta data.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
action master
if enabled or not
unique id for feature
left icon
url for navigating
right icon
codes specifying role
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
Update action(s) successful
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
Create mapping for feature and role.
Request info for getting actions.
List of Role Id to be provided for mapping it to feature.
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
Successful response
Create mapping for role and action(s).
Details for the Role and Action(s) mapping + RequestInfo meta data.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
minimal representation of the Roles in the system to be carried along in UserInfo with RequestInfo meta data. Actual authorization service to extend this to have more role related attributes
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
Role - Action(s) mapping created sucessfully
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver and msgId in ResponseInfo should always correspond to the same values in respective request's RequestInfo.
Validate a particular action for a given tenant and roles of the tenant.
Request info for getting actions.
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Successful response without any content