SL No API

1 GetMatchingSitesV1

2 DetailsV1

3 AddSite
4 GetSiteDetailsForEdit

5 EditSiteBasicInformation

6 EditSiteMoreInformation
7 AddOrRemoveChargeSpotToSite
Url

https://vegaapi.gnrgy.com/Site/GetMatchingSitesV1?lang=en

https://vegaapi.gnrgy.com/Site/DetailsV1?lang=en

https://vegaapi.gnrgy.com/Site/AddSite
https://vegaapi.gnrgy.com/Site/GetSiteDetailsForEdit

https://vegaapi.gnrgy.com/Site/EditSiteBasicInformation

https://vegaapi.gnrgy.com/Site/EditSiteMoreInformation
https://vegaapi.gnrgy.com/Site/AddOrRemoveChargeSpotToSite
Apps api is used

Vega

Vega

Vega
Vega

Vega

Vega
Vega
What is the impact

No Impacts as Existing API will be modified in backwards compa

No Impacts as Existing API will be modified in backwards compa

No Impacts as Existing API will be modified in backwards compa

No Impacts as Existing API will be modified in backwards compa

No Impacts as Existing API will be modified in backwards compa

Changes in parameters

"Chargers": [
….................
"ChargerType":"public"
…...................
]

Remove following Parameters from Request body

{
OperationStatus
PublishToApp
}
Remove following Parameters from response body
{
OperationStatus
PublishToApp
IsRoaming
}
->Remove GridmanagementDetails object
-> Remove ChargeplanDetails object

Remove following Parameters from Request body

{
OperationStatus
PublishToApp
}

Remove following Parameter from Request body

{
IsRoaming
}
Existing Business logic

Currently we are searching based on SiteType {public,

private , business} that referes the SiteType table

Currently We Are Getting Site Details by passing VendorId and

SiteId
For Charger Information we are Calling Sirius Api named it as
ChargersBy

Request Parameters:
VendorId,CustomerId,Type,Lat,Lon,IsRestricted,ZipCode,Countr
yId,IsUpcoming
Here they are checking CustomerId associated with the
sites or not by Passing the CustomerId to Office Customer
Table
By Mapping to Get all the Data
Passing Only SiteId to edit is happening
By Calling ChargersBy Sirius API to Get the
Chargers,Connectors details they're Mapping in here

Request Body:
SiteId,LanguageCode,Name,HouseNumber,street,City,ZipCode,
CountryId,CustomerId,SiteTypeId,OperationSttaus,PublishToAp
p,IsUpcoming,IsRestricted,Lat,Lon
Get the CustomerId to Edit the SiteDetails
Mapping the Other Site Details

Passing SiteId As Request Body

Just Get the Status as Response Body
All the Details fetched from Local DB
Approach 1 Approach 2
query chargers across sites, this may result in
->Remove SiteTypeId from Query an issue:
Site 1 may have 20 chargers,
Request Site 2 may have 20 chargers,
{ Site 3 may have 10 chargers,
"VendorId": 0, Total = 60 chargers, but only 50 are
"ShownInApp": 0, expected based on the default
"ReferenceCode": "string", PageSize.
"OperationStatus": 0, To overcome this, we will set the
"Name": "string", PageSize to 1000. This ensures that the
"Type": 0, request fetches a sufficient number of
"Address": "string", chargers to cover all the charger
"PageNumber": 0, details across the 50 sites, even if the
"StationMoreFilters": { charger distribution varies between
"SearchOption": "string", sites.
"SearchItem": "string",
"SearchValue": "string", 4. Mapping Sirius Data to Site Details
"ManagedSite": true, Once the data is retrieved from Sirius,
"ChargePlanName": "string" we will map the charger details back to
} the corresponding sites based on their
} SiteId. This mapping will ensure that
each charger is correctly associated
with the respective site from the
sirius request{ original database query.
"ShownInApp": 0,
"OperationStatus": 0, 5. Final Result
"ManagedSite": true, The result will be a comprehensive set
We are not using 1
"ChargePlanId: shared site functionality in of site records, each with the
vega
"ChargeType": corresponding charger details fetched
so"Gridmanagement":
we dont need to pass the chargertype in from Sirius, ensuring that no chargers
request are omitted due to page size
Response
} below Paramter you need to add limitations.

"Chargers": [
{
"ChargeBoxSerialNumber": "string",
"ChargeBoxId": "string",
"ChargerType":"public"--> Add new
parameter
}

Remove following Parameters from Request

body

{
OperationStatus
PublishToApp
}
Remove following Parameters from response
body
{
OperationStatus
ShowInApp
IsRoaming
}
->Remove GridmanagementDetails object
-> Remove ChargeplanDetails object

Remove following Parameters from Request

body

{
OperationStatus
PublishToApp
}

Remove following Parameter from Request

body

{
IsRoaming
}

Moving gridmanagement section to Charger

level
Moving ChargePlan Section to Charger level
No Changes
 API

SL No

1 GetMatchingChargeSpots

2 Details

3 AddChargeSpot

4 EditChargeSpot

5 Download

6 DownloadPdf
Url

https://vegaapi.gnrgy.com/ChargeSpot/GetMatchingChargeSpots

https://vegaapi.gnrgy.com/ChargeSpot/Details

https://vegaapi.gnrgy.com/ChargeSpot/AddChargeSpot

https://vegaapi.gnrgy.com/ChargeSpot/EditChargeSpot

https://vegaapi.gnrgy.com/ChargeSpot/Download

https://vegaapi.gnrgy.com/ChargeSpot/DownloadPdf
Apps api is used

Vega

Vega

Vega

Vega

Vega

Vega
What is the impact

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

Request{
----
ChargerType:1 Currently We are Passing
--- CBID ,SiteType,SiteName,Vendor
Id as a Request
Changes
} in parameters Existing Business
In Response logic
We are Getting the
Chargers and connector
Response{ Information
--- We're Getting SiteName and
"ChargerType":"public" Chargeplan Name from LocalDb
---

Currently Passing
VendorId.ChargeBoxId as
Request Parameter we are
Response: getting Chargespot Details
{ By Calling Charger API in Sirius
ChargerType:"public" We're Getting Chargers Details
}

Add following Parameters from

request body
{ Request:
OperationStatus {
PublishToApp VendorId,CustomerId,Chargepoi
IsRoaming ntSerialNumber
ChargerType }
Request:
VendorId,CustomerId,ChargeBox
ChargerPlanDetails: At
Id First,They are checking
{ whether the passing
Calling Sirius CustomerId
API Chargers to
is existis in OfficeCustomer
add new chargespot in here
} Table Or Not
} Calling Sirius API Chargers get
the Chargers information

Add ChargePlan Section

They are take

UserId,VendorId,CustomerId
Using VendorId,CustomerId to
Call SearchChargespot to get
the Chargers information
Mapping the All the Column
Details which contains in the pdf

They are take

UserId,VendorId,CustomerId
Using VendorId,CustomerId to
Call SearchChargespot to get
the Chargers information
Mapping the All the Column
Details which contains in the csv
----
ChargerType:1
---

}
New Business logic
Response{
---
"ChargerType":"public"
---
}

Just Add the One Parameter in

Response Body to Get
ChargeType for Chargers

Response:
{
ChargerType:"public"
}

Add following Parameters from

request body
{
OperationStatus
PublishToApp
IsRoaming
ChargerType

ChargerPlanDetails:
}

Add ChargePlan Section

Get SiteType from New

SiteType Table
Add a New ChargerType
Column also

Get SiteType from New

SiteType Table
Add a New ChargerType
Column also
SL.No API

1 GetMatchingChargingTransactionsV1

2 OngoingChargingTransaction
3 Download
4 DownloadPdf
Url

https://vegaapi.gnrgy.com/ChargingTransaction/GetMatchingChargingTransactionsV1

https://vegaapi.gnrgy.com/ChargingTransaction/OngoingChargingTransaction
No Impacts as Existing API will be modified in backwards compatible way
No Impacts as Existing API will be modified in backwards compatible way
Apps API is Used

Vega

Vega
Vega
Vega
What is the Impact

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way

No Impacts as Existing API will be modified in backwards compatible way
No Impacts as Existing API will be modified in backwards compatible way
Changes in Parameters

We need to new column ChargeType to do billing for transaction

Add Response in ChargeType

Add ChargerType column
Add ChargerType column
Existing Business Logic
VendorId,and Site applying filters to
match the Transaction
We're Getting passing Customer
Id,vendorId to Get the Details from
BillingInfo Table

Request:
SiteId,SiteName,CustomerId.Custom
erName,VendorId,ChargerId
Based On the Applying filters We're
Getting all the Transaction details
from Our Db SIDE

Taking VendorId,CustomerId,UserId to
Taking VendorId,CustomerId,UserId to
New Business Logic

We need to add ChargersType Column in BillingInfo Table for Transaction

Add Response in ChargeType

Add ChargerType column
Add ChargerType column