Adeptia Connect APIs
You can use the listed APIs on this page to view product information and to manage various activities (User, Partner, Transactions, Schema, and Mapping) from an external application. The API provides the way to fetch product information, Create, Update, and Delete activities without accessing the user interface.
Use any REST client with the following header information to process your request.
Key | Header Information (value) |
---|---|
Content Type | application/json |
ACCESS_TOKEN | To get the Access Token, refer below table for more details. |
API to Get Access TokenÂ
Operation | Method | API Endpoint | Example Payload | Example Response |
---|---|---|---|---|
Get Access Token | POST | /rest/login/user | { "username":"{User Name}", "password":"{Password}" } |
APIs for Managing Users
Operation | Method | API Endpoint | Example Payload | Example and Notes |
---|---|---|---|---|
Create User | POST | /rest/invitation?resourceIdentifier=users | For Single Partner and Single Role: { "roleInfo":"[{\"partner\":1,\"roles\":[2],\"defaultRole\":2}]", For Multiple Partner and Multiple Role: { Note: In case of multiple partner and multiple role, you need to modify the roleInfo field with the respective activity IDs. | Example Response: This endpoint creates an invitation and return invitation id in response which you will use while creating the user. |
POST | /rest/users/createuser | { | Example Response:
Use the invitation Id from the above Create User response. | |
Update User | PUT | /rest/users/{userId} | { "company":"Adeptia", | Example Response: |
Get User | GET | /rest/user/{userId} | ||
Get All Users (Connect Portal) | GET | /rest/users?limit={maximum number of users} | Using this API, you will get only Connect Portal users. By default the value of limit is 1. Moreover, the limit stands for maximum number of users can be fetched from the database. | |
Activate User | PUT | /rest/users/activate/{userId} | EMPTY | |
Deactivate User | PUT | /rest/users/deactivate/{userId} | EMPTY | |
Delete User | PUT | /rest/users/updateowner?oldUserId={userId}&deleteUser=true | EMPTY | By default this endpoint will delete the user who has no dependency else an exception message to move objects will be generated. |
APIs for Managing Partners
Â
Operation | Method | API Endpoint | Example Payload |
---|---|---|---|
Create Partner | POST | /rest/company | Â Â |
Update Partner | PUT | /rest/company/{partnerId} | |
Delete Partner | PUT | rest/company/deletepartner/{partnerId} | EMPTY |
Update Partner Parameters | PUT | /rest/company/{partnerId} | |
Grant all Templates Access to Partner | POST | rest/templatepartnerlinkage?resourceIdentifier=company | |
Revoke all Templates Access to Partner | DELETE | rest/templatepartnerlinkage/partnerId?resourceIdentifier=company | EMPTY |
Grant a Template Access to Partner | POST | /rest/templatepartnerlinkage?isTemplate=true&resourceIdentifier=transactiontemplate | |
Revoke Template Access from Partner | DELETE | rest/templatepartnerlinkage/ {linkageId}?isTemplate=true&resourceIdentifier=transactiontemplate | EMPTY |
Move Partner from One Network to another | POST | /rest/company/{partnerId} | |
Convert Internal Partner to External | POST | rest/company/enableSelfOnbaord | |
Convert Internal Partner to External Partner | POST | rest/users/import | Multipart Request ContentType : multipart/form-data form-data Part1 :
form-data Part2:
   |
Â
APIs for Managing Transaction
Operation | Method | API Endpoint | Example Request Payload |
---|---|---|---|
Create Transaction | POST | /rest/transaction | |
Create Transaction with Parameters | POST | /rest/transaction | |
Update Transaction | PUT | /rest/transaction/{transactionId} | |
Update Transaction Parameters | PUT | /rest/transaction/{transactionId} | |
DELETE | DELETE | /rest/transaction/{transactionId} | EMPTY |
APIs for Managing Transaction for Custom TemplateÂ
Operation | Method | API Endpoint | Example Request Payload | Example Response |
---|---|---|---|---|
Create Transaction | POST | /rest/transaction | To identify the sequence ID for each steps, it is recommended to run the below Get Step Info API. | |
Get Step Info | GET | /rest/transactiontemplate/getactivitiesinfo/ {templateId}/{processFlowId} | EMPTY |
APIs for Managing Schema and Mapping
Operation | Method | API Endpoint | Example and Notes |
---|---|---|---|
Get all Schema and Mapping activities available to Partner | Â GET | Â /rest/activities/{partnerId} | Â By default this endpoint lists all the activities available to partner. To retrieve specific activities pass the comma separated service name query parameter as below ?services=TextSchema,ExcelSchema Valid Service Names are
By default all the available fields of all activities are returned in response. To limit the number of fields and to get specific fields pass the "fields" query param and pass the comma separated field names as below ?fields=id,entityName Note: Only those activities will be returned in response to which the requesting user is authorized to view as per permission settings. Admin will get all activities. Â |
Get all Schema and Mapping activities used by Partner in Transactions of a particular Template | GET |  /rest/activities/{partnerId}/{templateId} | By default this endpoint lists all the activities used by partner for a particular template. To retrieve specific activities pass the comma separated service name query parameter as below ?services=TextSchema,ExcelSchema (See above the list of valid service Names)  By default all the available fields of all activities are returned in response. To limit the number of fields and to get specific fields pass the "fields" query param and pass the comma separated field names as below ?fields=id,entityName  |
APIs for Viewing Product Information
Operation | Method | API Endpoint | Example Response |
---|---|---|---|
View Connect Server (Developer Suite) Info | GET | /rest/fetchproperties/aboutinformation | |
View Connect Portal Info | GET | /rest/applications/getTag |
Known Issues with API
These are the issues which occur while updating Partner Parameters:
- Empty Partner Parameters [ { }, { } ] create Parameters with NULL parameter Id and Value.
- Different Network Parameters can be associated with Partner to those Networks on which Partner does not belong.
- Passing Empty array ( [ ]) of Partner Parameters do not remove existing Parameters.
Â