| Serial | APIs / SDKs | Transaction Definition |
|---|---|---|
| 1 | Interactive Map JS Web SDK/API (also applicable to Cordova/ReactJS based packages) | One transaction is one load of the SDK (SDK Initialization) in any web app. Events such as Panning, zooming in/out, adding markers, polyline, ploygons on Map is NOT considered as a transaction, unless they result in fresh tiles being downloaded from the server. In case where fresh tiles are requested from server, for every 10 tiles so refreshed an additional transaction is incurred. Actions such as zoom may not necessarily cause tiles being fetched anew from server; since browser's JS engines are capable of limited1 amount of browser-cache based rendering. 1Deliberate caching of map tiles is not permitted. When a page is refereshed/reloaded, it results in the map SDK loaded afresh and hence incurs additional transaction in accordance with above. |
| 2 | Geocoding API | One request using the API method/URL will be considered as one transaction. Upto 1 geocoded address is returned one request, unless otherwise specified in agreement with customer. |
| 3 | Reverse Geocoding API | One request using the API method/URL will be considered as one transaction. Upto 1 reverse geocoded address is returned one request, unless otherwise specified in agreement with customer. |
| 4 | Routing API | One Transaction for Routing API (any profile) is equivalent to route requested between two sets of lat-long. Upto 98 via points are allowed in one request. E.g. If distance from x,y to x3,y3 via x1,y1 and x2,y2 is requested, then its counted as 3 transactions. |
| 5 | Distance Matrix API | One Transaction for Distance Matrix API is equivalent to distance requested between two sets of lat-long. E.g. distance from x,y to x1,y1 and x2,y2 is requested, then its counted as 2 transactions. |
| 6 | Still Map Image API | One Request(which returns one image) using the API method/URL will be considered as one transaction. |
| 7 | Autosuggest API (per request) | One request using the API URL will be considered as one transaction. At any point, for any string in the input, the output will be list of places matching with that input string. |
| 8 | Nearby APIs | One request using the API method/URL will be considered as one transaction. Upto a maximum of 10 places are returned in 1 request unless otherwise specified in agreement with customer. |
| 9 | Place Details | One request using the API method/URL will be considered as one transaction. |
| 10 | Traveled Route Image API | One Request(which returns one image) using the API method/URL will be considered as one transaction. |
| 11 | POI Along the Route API | One request using the API method/URL will be considered as one transaction. Upto a maximum of 10 places are returned in 1 request unless otherwise specified in agreement with customer. |
| 12 | Snap to Road API | One request using the API method/URL will be considered as one transaction. One request can take upto a maximum of 100 raw coordinates for map matching. |
| 13 | Address Standardization API | One request using the API method/URL will be considered as one transaction. |
| 14 | Route Optimization API | One Transaction for Route Optimization API (any profile) is equivalent to route optimization requested between two sets of lat-long. Upto 98 via points are allowed in one request. E.g. If optimization is requested from x,y to x3,y3 via x1,y1 and x2,y2 is requested, then its counted as 3 transactions. |
| 15 | Mobile Maps SDK for Android | One transaction is one load of the SDK (SDK Initialization) in any mobile app. Events such as Panning, zooming in/out, adding markers, polyline, ploygons on Map is NOT considered as a transaction, unless they result in fresh tiles being downloaded from the server. In case where fresh tiles are requested from server, for every 10 tiles so refreshed an additional transaction is incurred. |
| 16 | Mobile Maps SDK for iOS | One transaction is one load of the SDK (SDK Initialization) in any mobile app. Events such as Panning, zooming in/out, adding markers, polyline, ploygons on Map is NOT considered as a transaction, unless they result in fresh tiles being downloaded from the server. In case where fresh tiles are requested from server, for every 10 tiles so refreshed an additional transaction is incurred. |
| 17 | Text Search API | One request using the API method/URL will be considered as one transaction. |
For any queries and support, please contact:
@ Copyright 2020 CE Info Systems Pvt. Ltd. All Rights Reserved.
Terms & Conditions | Privacy Policy | Supplier Sustainability Policy | Health & Safety Policy | Environmental Policy & CSR Report
Customer Care: +91-9999333223