DIGIT-API's
  1. Schemas
DIGIT-API's
  • Using DIGIT-PLAYGROUND
  • User
    • Manage
      • Create User
      • Search All Users
      • Search Active Users
      • Create User Without OTP Validation
      • Update User Without OTP Validation
      • Get User
      • Update Profile
    • Authenticate
      • Logout
      • Reset Password
      • Login
  • Master Data V1
    • List
    • Search
  • Master Data V2
    • Create Schema
      • Create Schema
    • Search Schema
      • Seach Schema
    • Add Data
      • Create
    • Seach Data
      • Seach Data
    • Update data
      • Updata
  • Access-control
    • Action
      • Authorize User
      • Get the list of actions based on either roles or features.
      • Create a new action.
      • Update existing action(s).
      • getAllMDMSActions
      • Validate a particular action for a given tenant and roles of the tenant
    • Role
      • Get the list of roles based on role codes.
      • Create a new role.
      • Update existing role(s).
    • Role-Action
      • Create mapping for role and action(s).
  • Workflow-v2
    • WorkFlow
      • Create new workflow entry for a given application number(businessId).
      • Process search of the applicaition
      • Get the list of workflow applications defined in the system.
      • Get the count of applications satisfying the given criteria
      • Get the nearing sla count of workflow applications defined in the system.
      • Get the list of status count workflow applications defined in the system.
    • Escalate
      • Get the list of escalate workflow applications defined in the system.
      • Get the list of workflow applications defined in the system.
    • BusinessServiceV2
      • Create new v2 BuinessService.
      • Updates a existing v2 BuinessService.
      • Get the list of v2 BusinessServices defined in the system.
    • BusinessService
      • Create new BuinessService.
      • Updates a existing BuinessService.
      • Get the list of BusinessServices defined in the system.
  • Filestore
    • Upload File
      • Uploads different kinds of files to server.
    • Search
      • Search file url based on tenantid and filestoreid.
      • Search file url based on tenantid and tag name.
      • Get metadata of file based on tenantId and filestoreId.
      • Search file url based on tenantid and filestoreid.
  • Idgen
    • IdGeneration Controller
    • Create new id.
  • Location
    • Boundary
      • Search Location
      • It Will provide the List of boundaries based on search criteria Like "Srikakulam Municipality","Zone-1","Zone-2" etc.
    • Geography
      • Handles all requests related to Geographical boundaries by providing appropriate GeoJson and other associated data
    • Tenant
      • Resolves a given latitude / longitude to the corresponding tenant Id
  • Enc-Service
    • Crypto
      • Encrypts the given input value/s OR values of the object.
      • Decrypts the given input value/s OR values of the object.
      • Provide signature for a given value.
      • Check if the signature is correct for the provided value.
      • Deactivate the keys for the given tenant and generate new keys. It will deactivate both symmetric and asymmetric keys for the provided tenant.
      • cryptoRotateAllKeys
  • PG-Service
    • transactions-api-controller
      • transactionsV1AvailableGatewaysPost
      • transactionsV1CreatePost
      • transactionsV1SearchPost
      • transactionsV1UpdatePost
  • URL-Shortening
    • egov-url-shortening service endpoints
      • shorten given url
      • redirects user to orignal url identified by id
  • Indexer
    • egov-indexer service
      • This endpoint is used to start legacy index job to reindex records from DB. The data is fetched from DB by calling api mentioned in request in batches. The is useful when some record is present in DB but missing on index.
      • This endpoint is used to start indexing job to reindex records from one index to another index.
      • This endpoint is used to index one record on a index. The information to pick correct config is provided with the data to be indexed.
      • Index data in row
  • PDF-Service
    • PDF-Service endpoints
      • Generate PDF and store output pdfs to filestore and return their filestoreids. The information is also saved into DB so that using _search endpoint we can retrieve already generated pdfs.
      • Generates pdf without storing any information on filestore or in DB. The generated pdf would be returned as binary response
      • Get filestoreids and other information about already generated pdf by searching on jobid or entityid with other optional search parameters
  • Report
    • Report Meta
      • createv1
      • getReportDatav1
      • Metadata API for report definition
    • Report
      • Search API for report data
  • eGov-OTP
    • OTPConfig
      • create OTP Configuration entry
      • validate OTP Configuration entry
      • search OTP Configuration entry using uuid
  • User-OTP
    • user otp send
  • Localization
    • Create Message
      • create massage
    • Fetch Message
      • fetch message
    • Update message
      • update message
    • Delete message
      • delete mesage
    • Upsert message
      • upsert message
  • Service Request
    • Service Defination Create
      • Create service defination
    • Service Defination search
      • Search service defination
    • Service create
      • service create
    • Service Search
      • Service search
  • Audit Service
  • Schemas
    • Schemas
      • NonLoggedInUserUpdatePasswordRequest
      • MdmsCriteriaReq
      • Document
      • ReindexResponse
      • FilestoreIdResponse
      • IdRequest
      • HierarchyType
      • EncReqObject
      • Transaction
      • ShortenRequest
      • PDFResponse
      • MetadataRequest
      • Otp
      • LoggedInUserUpdatePasswordRequest
      • MdmsCriteria
      • ActionRequest
      • ProcessInstance
      • LegacyIndexResponse
      • UploadFileResponse
      • IdResponse
      • Boundary
      • EncryptionRequest
      • TransactionRequest
      • PDFRequest
      • MetadataResponse
      • OtpRequest
      • User
      • UpdatePasswordResponse
      • ModuleDetail
      • ActionResponse
      • StatusCountRequest
      • ReindexRequest
      • TagFileResponse
      • IdGenerationRequest
      • Geography
      • SignRequest
      • TransactionCreateResponse
      • ReportRequest
      • OtpValidateRequest
      • UserSearchRequest
      • MasterDetail
      • ActionValidation
      • BusinessService
      • APIDetails
      • MetaDataResponse
      • IdGenerationResponse
      • TenantBoundary
      • SignResponse
      • ReportResponse
      • OtpResponse
      • CreateUserRequest
      • MdmsResponse
      • AuthorizationRequest
      • State
      • LegacyIndexRequest
      • UploadFile
      • BoundaryResponse
      • VerifyRequest
      • TransactionResponse
      • ColumnDef
      • CustomUserDetails
      • AuthorizationRequestWrapper
      • PaginationDetails
      • TagFile
      • GeographicalResponse
      • VerifyResponse
      • TaxAndPayment
      • SearchParam
      • Action
      • RoleAction
      • ProcessInstanceRequest
      • TenantResponse
      • RotateKeyRequest
      • ColumnDetail
      • Address
      • UserRes
      • RoleRequest
      • ProcessIntanceResponse
      • RequestInfoWrapper
      • RotateKeyResponse
      • ReportMetadata
      • AuditDetails
      • ResponseInfo
      • RoleActionsRequest
      • ProcessInstanceSearchCriteria
      • Tenant
      • ReportErrorRes
      • TokenWrapper
      • RoleActionsResponse
      • StatusCountResponseObject
      • City
      • SourceColumn
      • RoleResponse
      • ResponseEntity
      • SearchColumn
      • RolesReq
      • BusinessServiceRequest
      • ReportDefinition
      • TenantRole
      • BusinessServiceResponse
      • RequestInfo
      • ValidateAction
      • UserInfo
      • ValidateActionReq
      • Role
      • ValidateActionRes
      • ErrorRes
      • Error
  1. Schemas

ErrorRes

All APIs will return ErrorRes in case of failure which will carry ResponseInfo as metadata and Error object as actual representation of error. In case of bulk apis, some apis may chose to return the array of Error objects to indicate individual failure.

{
    "ResponseInfo": {
        "apiId": "string",
        "ver": "string",
        "ts": 0,
        "resMsgId": "string",
        "msgId": "string",
        "status": "SUCCESSFUL"
    },
    "Errors": [
        {
            "code": "string",
            "message": "string",
            "description": "string",
            "params": [
                "string"
            ]
        }
    ]
}
Built with