Table of Contents style Square
...
Background and strategic fit
The purpose of this Integration is to pull the Location information. This data can be further used while hitting other APIs)
(as request parameter). This document provides information on how the the end Users can consume the API
Assumptions
- ProcessMAP system User permissions would not be considered while exposing the data
- Data will be shown in Readable JSON format
- User accessing this endpoint through a valid Token & ConsumerId, provided by ProcessMAP, will have access to complete data
- The "Level" property in the output will be shown only if the end user passes the Top RootNode name in the parameter.
- If the user passes any intermediate Level as Parameter or does not pass anything, then the "Level" property in output will be NULL. This is because the system allows for having sublevels under different structure with same name. So the hierarchy can be multiple in that case.
...
| Product Field Name | Description | Field Type and Size |
|---|---|---|
| Location Name | Represents location name | NVARCHAR(50) |
| Location Code | Represents location code | NVARCHAR(50) |
| LocationId | Represents Database LocationId | |
| Address | Represents Location Address | |
| City | Represents Location City | |
| State | Represents Location State | |
| Country | Represents Location Country | |
| Zip | Represents Location Zip | |
| Level | Represents the Level Hierarchy in flat format[when rootname is passed in parameter] |
...