cupa-ceil-proxy-xapi

1.0.x
(0 reviews)

Security

Policies:

Client Id Enforcement

To consume the API, consumer must register its client application with in Any point exchange and get the Client ID and Client Secret. The Client ID (client-id) and Client Secret(client-secret) should be passed in http headers to get authorized for the request.

  • Client ID Expression[attributes.headers['client-id']]
  • Client Secret Expression[attributes.headers['client-secret']]
No.MethodsResource
1.GET/status
2.GET/products
3.POST/products
4.POST/role/access
5.GET/marks/minimax/{posid}
6.POST/markadjustmnet/adjustMarks
7.POST/markadjustment/fetchMarks
8.POST/markadjustment/bulkUpload
9.GET/markadjustment/downloadTemplateDetails
10.GET/resultAudit
11.POST/resultAudit
12.POST/briefingCommentsForRma/getComments
13.GET/briefingCommentsForRma/upload
14.POST/briefingCommentsForRma/update
15.POST/accounts.setAccountInfo
16.POST/candidateenquiry/candidatedetails
17.POST/candidateenquiry/resultdetails
18.POST/markTransfer
19.POST/searchCandidate
20.POST/GDPRRemarking
21.POST/monitoring/overview
22.POST/monitoring/records
23.POST/monitoring/recorddetails

Endpoints are secured using Client ID policies
Reference: Client Id Enforcement

Reviews