You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Changes made based on the comments
* Updated as per the comments
* Commit made based on the PR comments
---------
Co-authored-by: Akshaya Kumar <Akshaya Kumar@DESKTOP-TIGJLBP>
@@ -47,7 +47,7 @@ During Auth0 authentication, the client passes 'client id' and 'client secret' t
47
47
48
48
All API requests must be made over HTTPS, and API requests without authentication will fail. Security on data is managed by the ACTS platform, and API requests will provide the same admin access available to logged in ACTS admin users.
49
49
50
-
The user authentication endpoint uses a POST (with input parameters described above) to generate the access token [bearer token].
50
+
The user authentication endpoint uses a POST to generate the access token [bearer token].
51
51
52
52
>Authentication API Endpoint - https: // dev-intelex.us.auth0.com/oauth/token
53
53
@@ -78,4 +78,4 @@ Response Code | Meaning
78
78
79
79
When we make backwards-incompatible changes to the API, we release new versions. The current version of the ACTS API is v1 and can be determined with our API base path /api/v1/.
80
80
81
-
>Example API Endpoint : https://*.actsapi.intelex.com/API/**/v1/TableName
81
+
>Example API Endpoint : https://{tenant}.actsapi.intelex.com/API/**/v1/TableName
Copy file name to clipboardExpand all lines: source/includes/_all-get-apis.md
+36-36Lines changed: 36 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -6,144 +6,144 @@ The following GET APIs are used to fetch the data from the respective tables.
6
6
7
7
All data from the Attribute Type table will be returned from the endpoint below. You can optionally fetch specific data by including Attribute ID’s and Attribute Types. The Attribute Type endpoint supports pagination.
8
8
9
-
> Example GET Endpoint Without Pagination:
9
+
> Example Of AttributeType GET Endpoint Without Pagination:
All data from the Compound table will be returned from the endpoint below. You can optionally fetch specific data by including compound ID’s, compound Type IDs, compound status IDs, compound Names, external identifiers, or CAS number. The Compound endpoint supports pagination.
24
24
25
-
> Example GET Endpoint Without Pagination:
25
+
> Example Of Compound GET Endpoint Without Pagination:
All data from the Emission Category table will be returned from the endpoint below. You can optionally fetch specific data by including the emission category ID. The Emission Category endpoint supports pagination.
40
40
41
41
42
-
> Example GET Endpoint Without Pagination:
42
+
> Example Of EmissionCategory GET Endpoint Without Pagination:
> Example GET Endpoint With Pagination and Filter Option:
47
+
> Example Of EmissionCategory GET Endpoint With Pagination and Filter Option:
48
48
49
49
```
50
-
https: // *actsapi.intelex.com/API-develop/v1/EmissionCategory/{int data – Emission Category ID}
50
+
https: // {tenant}.actsapi.intelex.com/API-develop/v1/EmissionCategory/{int data – Emission Category ID}
51
51
```
52
52
53
53
## 4.Emission Type API GET Endpoint
54
54
55
55
All data from the Emission type table will be returned from the endpoint below. You can optionally fetch specific data by including the emission type ID. The Emission Type endpoint supports pagination.
56
56
57
-
> Example GET Endpoint Without Pagination:
57
+
> Example Of EmissionType GET Endpoint Without Pagination:
> Example GET Endpoint With Pagination and Filter Option:
63
+
> Example Of EmissionType GET Endpoint With Pagination and Filter Option:
64
64
65
65
```
66
-
https: //*actsapi.intelex.com/API-develop/v1/EmissionType?PageNumber=1&PageSize=500&emissionTypeID={int data value}
66
+
https: //{tenant}.actsapi.intelex.com/API-develop/v1/EmissionType?PageNumber=1&PageSize=500&emissionTypeID={int data value}
67
67
```
68
68
69
69
## 5.Equipment API GET Endpoint
70
70
71
71
All data from the Equipment table will be returned from the endpoint below. You can optionally fetch specific data by including the equipment ID. The Equipment endpoint supports pagination.
72
72
73
-
> Example GET Endpoint Without Pagination:
73
+
> Example Of Equipment GET Endpoint Without Pagination:
> Example GET Endpoint With Pagination and Filter Option:
79
+
> Example Of Equipment GET Endpoint With Pagination and Filter Option:
80
80
81
81
```
82
-
https: //*actsapi.intelex.com/API-develop/v1/Equipment?PageNumber=1&PageSize=500&equipmentID={int data value}
82
+
https: //{tenant}.actsapi.intelex.com/API-develop/v1/Equipment?PageNumber=1&PageSize=500&equipmentID={int data value}
83
83
```
84
84
85
85
## 6.Equipment Status API GET Endpoint
86
86
87
87
All data from the Equipment Status table will be returned from the endpoint below. You can optionally fetch specific data by including the equipment status ID and equipment status value. The Equipment Status endpoint supports pagination.
88
88
89
-
> Example GET Endpoint Without Pagination:
89
+
> Example Of EquipmentStatus GET Endpoint Without Pagination:
All data from the Equipment Type table will be returned from the endpoint below. You can optionally fetch specific data by including the equipment type ID and equipment types value. The Equipment type endpoint supports pagination.
104
104
105
-
> Example GET Endpoint Without Pagination:
105
+
> Example Of EquipmentType GET Endpoint Without Pagination:
All data from the Operation table will be returned from the endpoint below. You can optionally fetch specific data by including the operation ids, operation type ids, emission type ids, emission category ids, unit ids, equipment ids, last modified start date and last modified end date. The Operation endpoint supports pagination.
120
120
121
-
> Example GET Endpoint Without Pagination:
121
+
> Example Of Operation GET Endpoint Without Pagination:
> Example GET Endpoint With Pagination and Filter Option:
127
+
> Example Of Operation GET Endpoint With Pagination and Filter Option:
128
128
129
129
```
130
-
https: // *actsapi.intelex.com/API-develop/v1/ Operation?PageNumber =1&PageSize=500&OperationIDs="int data"&OperationTypeIDs=”string data "&EmissionTypeIDs="int data”&EmissionCategoryIDs="int data”&UnitIDs="int data"&EquipmentIDs="int data"&LastModifiedStartDate=”string format – date time data"&LastModifiedEndDate="string format – date time data"
130
+
https: // {tenant}.actsapi.intelex.com/API-develop/v1/ Operation?PageNumber =1&PageSize=500&OperationIDs="int data"&OperationTypeIDs=”string data "&EmissionTypeIDs="int data”&EmissionCategoryIDs="int data”&UnitIDs="int data"&EquipmentIDs="int data"&LastModifiedStartDate=”string format – date time data"&LastModifiedEndDate="string format – date time data"
131
131
```
132
132
133
133
## 9.Unit API GET Endpoint
134
134
135
135
All data from the Unit table will be returned from the endpoint below. You can optionally fetch specific data by including the unit ids, unit type ids and units. The Unit type endpoint supports pagination.
136
136
137
-
> Example GET Endpoint Without Pagination:
137
+
> Example Of Unit GET Endpoint Without Pagination:
Copy file name to clipboardExpand all lines: source/includes/_total-apis-and-tables.md
+15-13Lines changed: 15 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -3,18 +3,20 @@
3
3
This ACTS API release includes 11 GET enpoints and 4 POST endpoints, along with the authentication endpoint described above. The tables you can query and update are as follows.
0 commit comments