BSK API Integration Guide V5.0
BSK API Integration Guide V5.0
V 5.0
Bangla Sahayata Kendra (BSK)
and
Departments of Government of West Bengal
By
Table of Contents
Bangla Sahayata Kendras (BSKs) set up under State Government Memorandum No. 352-
CS/2020 dated 14.10.2020, across the State 'to provide government services free of cost at the
grassroot level through online mode' and also to strengthen the existing system of information
dissemination about various social and development schemes. The BSKs are located in the
offices of District Magistrates, Sub-Divisional Officers, Block Development Officers, Health
Centres, Government Aided Libraries, Office of the SI of Schools and all Urban Local Bodies
(ULBs). The Personnel & Administrative Reforms (PAR) and e-Governance Department of the
Government of West Bengal is the Nodal Department coordinating BSK project. There is a
Project Management Unit (PMU) at the State level looking after day-to-day functioning of
BSKs. All the notified services of BSKs are provided through its online BSK portal
[Link] The major key points
a) The grassroot level services are provided to the citizen at Bangla Sahayata Kendras (BSKs)
by Data Entry Operators (DEOs) absolutely free of cost.
b) Each DEO is having unique credential (login/password) on BSK Portal and authorized to
process the citizen centric services.
c) Each DEO use up to 25000/- for service-related costs incurred by the citizen through the
SBI e-wallet
d) DEO may pay the online fees / bills (electricity bill etc.) of citizen through BSK Bank Account
and collect the Cash or online payment from citizen and deposit to the said account.
2. Objective
The objective of the Application Programming Interface (API) integration is for handshaking
between BSK and the departments for sharing of data in a secure way. BSK is a single window
citizen delivery platform at the grassroots level. BSK emphases end-to-end delivery model to
the citizen. BSK provides service with assistance using the resources of on behalf of the
department.
3. Departments
All Departments of the government of West Bengal are mandated to use the BSK portal to
provide online services to citizens of the state. The departments are developing and sharing
APIs with BSK PMU tech team, onboarding the process to channelize departmental services
through the BSK portal. Currently 39 departments are already working with BSK PMU to
develop their APIs and use the BSK portal for delivering services at the grassroots.
4. Scope
The scope of the API Integration process is to integrate the Bangla Sahayata Kendra online
portal with all the departments of the Government of West Bengal so that citizens can
seamlessly get online services from (1) BSK Center, (2) BSK portal, and (3) BSK Mobile App at
the doorsteps. In addition, there will be a timeline for each service integration.
1. All the departments of the Government of West Bengal can integrate with BSK Portal
2. Departmental online service(s) only be included with BSK Portal
3. BSK Portal delivers service to the citizen using an End-to-End delivery model
4. Delivery material like e-certificate / receipt / acknowledgment can be available through
BSK Portal
5. Each service integration is having Service Level Agreement (SLA)
6. The citizen can get a digitally signed certificate from BSK Center / Portal.
5. Mandate of BSK
6. Potential Benefits
The API integration will share the data in a secure way between the BSK Portal and
Departmental Portal. The API system delivers data and facilitates connectivity between devices
and programs by sharing messages and enabling interaction of data, applications, and
devices. API is also defined as an online programming interface of organizations. It allows
applications to communicate with backend systems and create grounds for providing services
to the ordinary citizen of the state. The new services launching information is notified through
Short Message Services (SMS). The integration process has the following benefits:
a) Public Services available at the doorsteps of people
b) Citizens get complete assistance from a resource person working as Data Entry
Operators at the BSK centers
c) Citizens get the assistance of resources like computers, printers, the Internet, etc.
at the BSK center
d) The citizen data is entirely secure at the BSK Portal. Also, citizens provide only their
basic data.
7. Challenges
a) The data keyed at BSK centers by the DEOs are based on verbal information from
citizens.
b) Mapping of Citizen identity through Application Software using Mobile Number, Ticket
Number, Beneficiary Name etc. may be an issue as those may be keyed in differently
for same beneficiary in the BSK Portal & the Departmental Portals.
c) No mechanism for standardized application submission acknowledgement
d) Coordination with the department with versatile technology
BSK Tech team has classified the departments and services into three major categories.
The following flow diagram will identify that what to do by the department for integration:
Start
BSK is ready to
No Yes
Is partial Services Integrate all Services
Online? Immediately
Category A
BSK is ready to support BSK is ready to Integrate
to make service Online online Services
Immediately
Category C Category B
End
The top-level view of API integration will show the objective and outcome of the API
integration. Based on requirement, more API may be added.
This is hybrid model where encrypted data is transferred from BSK portal to Departmental
Portal through post method and there is no requirement of response against this call. After
submission of the form (may be draft / final) department will send data to BSK portal with
some detail like ticket no, timestamp of form submission, form submission amount (if any) etc.
Citizen_Basic_Info_Page
{date1, date2}
citizen_info_log/DB dept_service_page bsk_user_log/DB
Encrypted
Server to Server Call
push_api_page submit_page Data with
Response Response
thank_you_page bsk_service_log/DB
push_api_log/DB
generate_mis_report
Encrypted
{date1, date2}
bsk_call_missed_data dept_access_point
Response
o (c) Server to Server call to Department Access Point using POST method
• Step 4: [Dept Portal] Dept portal will receive at dept_controller_page. This controller
page has three tasks as follows
o (a) Decrypt the data using AES-256-CBC algorithm in JSON format
o (b) May Store the data into bsk_user_log/DB
o (c) Open the Service Page (Application Form etc.)
• Step 5: [Dept Portal] dept_service_page will open for fill-up and after draft / final
submission, it will call submit_page
• Step 6: [Dept Portal] submit_page has FOUR tasks as follows
o (a) Encrypt the JSON data using AES-256-CBC algorithm
o (b) Call BSK API (push) with the encrypted data and keep the response received
from BSK Portal
o (c) Store the data into bsk_service_log/DB with the response received from BSK
o (d) open thank_you_page
• Step 7: [BSK Portal] bsk_call_missed_data will call the dept_access_data with from date
(date1) and to date (date2) to retrieve the all missed out data between the dates.
• Step 8: [Dept Portal] dept_access_point will send the required data with encryption.
• Step 9: [BSK Portal] call_bsk_missed_data will receive and update the push_api_log/DB
• Step 10: The process ends.
BSK Tech Team designed the API integration architecture with all Government of West Bengal
departments to pull or push the data between the BSK Portal and Departmental Portal based
on the requirement. This API integration process will never force to change the existing
architecture of the departmental software. Instead, the API architecture will work with any
architecture and any software. It is one of the most secure methods for sharing data between
the BSK Portal and Departmental Portal, maintaining maximum security.
BSK follows a secure and standard process for integration across the departments. There are
two values in the JSON object. The first is a secret code, ‘passcode’ for authentication of the
API sources. The department will provide the passcode. And the second one is the data value
in the form of a JWT Token. The JWT Token is secured digitally signed secure code. In a
nutshell, BSK uses the following security measure:
{
“passcode”: “376423”,
“token”:” eyJhbGciOiJIUzI1N5cCI6IkpXVCJ9.sdfknxcvmxv4.7474udfhrr”
}
BSK server will communicate to the department through POST method with multiple
objectives and hence BSK Tech Team has designed multiple APIs, which are given below:
API-1 is the mandatory call as it the first communication with the department. The
API-1 is designed to provide the data to the department as a request. Department will
store the data to the department database and send the application submission initial
status as response.
✓ Step 1: When the citizen visits a BSK for service, BSK Portal captures citizen’s basic
data. BSK Portal then generates a service log with a unique identification which
comprises of userId and ticketNo. The userId is the operator mobile no and ticketNo
is the timestamp of the service. BSK Portal stores userId and ticketNo along with
citizen basic data into the BSK database.
✓ Step 2: userId is the 10-digit mobile number of DEO (user) and ticketNo is the
timestamp (YYYYMMDDHHmmSS) of the service entry in the BSK Portal. Jointly
userId and ticketNo is unique.
✓ Step 3: BSK portal transfers service detail and citizen basic data to the departmental
portal as a request of API-1 in format of JSON Web Token (JWT). The department
has to keep the ticketNo and userId along with citizen service-related information
in their database.
✓ Step 4: The citizen will be redirected to departmental specific service page for
application fill up. After redirecting to the application / service page, department
will return the initial status of the application as response of the API-1. The task of
API-1 completes.
BSK Database
Department
Database Citizen Service
information along with
userid and tokenNo
API-1
Use Case The API-1 is called to push the data of user and citizen to the
department database as the service has initiated.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{
“userid”: 9054233544,
“ticketNo”: 20220811130723,
“serviceCode”: ”A D/003”,
“name”: ”Arindam Ray”,
“mobile”: ”9350778824”,
“email”: ”[Link]@[Link]”,
“gender”: ”male”,
“age”: 48
}
The API-2 is initiated when the application is submitted either in the draft or final
version. Once the form is submitted (draft or final) then the API-2 is called by the
department for transferring the data to BSK Server. The data will be sent as request
and BSK Portal will send the response to that request.
✓ Step 1: The API-2 is called once the application submitted successfully (draft or final).
The transaction information like transaction detail, payment detail (if any) will be
transferred to the BSK by the department. And BSK will update the flag of application
status (applicationStatus) in the BSK portal.
Service Information
BSK Database
Departmental
Service Page
Use Case API-2 is called by the department once the application is submitted
as draft or final submission along with transaction detail.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ {
“userid”: 9054233544, “appNo” : “123456”,
“ticketNo”: 20220811050723, “responseStatus”: ”Success”,
“serviceCode”: ”A D/003”, “statusCode”: 200
“appNo” : “123456”, }
“ appSubTime ” : 20220811052025,
“deptPayRefNo” : “23424423424”,
“transNo” : “1234353435”,
“bankRefNo” : “4653443656”,
“paidAmt” : 200.00,
“message”: “Draft Submitted”,
“applicationStatus”: 2,
“statusCode”: 200
}
The API-3 is called for finding the status of the application. Each department maintains
the service level agreement (SLA) for each service. So, during the service, citizen may
search the status of the application and that can be shown through this API-3.
✓ Step 1: The API-3 is required for finding the status of the application. Citizen can check
the status of the application through BSK portal. It retrieves the data from the
departmental portal by providing the Application No as request in API-3 which will
return the application status in an array as the response.
✓ Step 2: The response is an array of data of all the phases (Sub-SLA). The array of data
is required to show in citizen dashboard.
✓ Step 3: After receiving the data as the response, the task of API-3 completes.
BSK Database
Department
Department
Portal
Database
API-3
Use Case API-3 is called for getting the intermediate status of the application.
Against the application number it returns the stagewise detail in the
form of array and that will be shown in the citizen dashboard.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ {
“userId”: 9054233544, “userId”: 9054233544,
“tokenNo”: 20220811050723, “tokenNo”: 20220811050723,
“serviceCode”: ”A D/003”, “applicationNo”: ”AP7373633/003”
“applicationNo”: ”AP7373633/003” “serviceName”: “Seed Certificate”,
} “ServiceCode”: ”A D/003”,
"applicationStage":[
{
“responseTime”: 20220710052220,
“message”: “Successfully Submitted”
},
{
“responseTime”: 20220712022000,
“message”: “Field Verification Successful”
},
{
“responseTime”: 20220713140500,
“message”: “Document Verified”
}
{
“responseTime”: 20220714100000,
“message”: “Certificate Issued”
}
],
“applicationStatus”: 4,
“statusCode”: 200
}
The API-4 is required to download the document. The document means certificate,
receipt, acknowledgement, duplicate document etc. The API-4 will send the application
certificate no and pull the document, if available otherwise a suitable message will be
shown. The request and response parameters are show below:
✓ Step 1: The API-4 is for verify and download the document. Citizen can verify or
download document from BSK portal by receiving data/link from the departmental
portal. BSK portal will provide the Document No as request of API-4. The department
will return the link of the Certificate/document as the response.
✓ Step 2: If the certificate is not available then it will send the relevant message in the
response and API-4 completes.
Back Print
BSK Database
Request: Certificate /
Document No Document
Department
Department
Portal Response:
Database
Document Value
API-4
Request Body
Response Body
{ {
“userId”: 9054233544, “userId”: 9054233544,
“tokenNo”: 20220811050723, “tokenNo”: 20220811050723,
“serviceCode”: ”A D/003”, “serviceCode”: ”A D/003”,
“applicationNo”: ”AP7373633/003” “serviceName”: “Birth Certificate”,
} “documentType”: 1,
“documentValue”: “<URL>”,
“applicationStatus”: 5,
“statusCode”: 200
}
The API-5 is used for One Time Password (OTP) verification. The document may be
download after confirmation OTP from citizen. That can be done through BSK Portal.
The OTP will be generated by the department only. To complete the process of OTP
verification two APIs is needed.
✓ Step 1: The API-5 is required only if OTP verification is required. This API completes
the process by calling twice API-5A and API-5B sequentially.
✓ Step 2: The API-5A will send the document number along with OTPId (Unique number
for OTP sender identification), generated by BSK portal, as the request. The department
will send the OTP to the citizen and confirmation to BSK portal as response.
✓ Step-3: The API-5B will send the OTP number entered by the citizen along with the
earlier OTPId (which was sent in API-5A) for department validation. The department
will send response with document download / show status information and API-5
completes.
Back Print
BSK Portal
OTP Page
Document No
Department Department
Database Portal
Mobile No
API-5A
Use Case API-5A is called for sending the document no and request to
generate OTP for citizen confirmation of service. A unique number is
generated for identification of sender.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ {
“otpId”:393747483, “otpId”: 393747483,
“documentNo”: ”AP7364733/273” “otpGenStatus”: 1,
} “statusCode”: 200
}
API-5B
Use Case API-5B is called for sending the OTP value by the citizen for
verification. If OTP verified then the control forwarded for service.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ {
“otpId”: 393747483, “otpId”: 393747483,
“userTypedOtp”: 8374 “serviceCode”:”AMD/003”,
} “serviceName”: “Seed Certificate”,
“documentType: 1,
“documentValue”: “<URL>/Base64 Code”,
“statusCode”: 200
}
The API-6 is required to authenticate a BSK user. Through the userId (DEO) the
department may get the user detail for their verification and others.
✓ Step 1: The API-6 is required to get the user detail. The API-6 will verify the BSK Data
Entry Operator’s (DEO) UserId, department code, department access code for the
authentication. BSK has large number of operators having variable status at any point
of time like ‘Active / Inactive / Left ‘. So, if require, at any point of time it can be verified.
✓ Step 2: The API will be called by department with userId as request along with the
department accessCode provided by BSK Team and BSK portal reply the status of the
user along with other information of user as response and the process of API-6
completes.
Department
Portal
Response: Request:
User detail userid, deptCode
accessCode
BSK Portal
BSK Database
API-6
Use Case API-6 is called for getting the user detail. There are department code
and access code verification for getting the detail of user (DEO).
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ {
“userId”: 9054233544, “userId”: 9054233544,
“deptCode”: “A D” “userName”:”Charan Das”,
“accessCode”:7364443 “userEmail”: “[Link]@[Link]”,
} “bskCode”:”B/L/384”,
“bskName”:”BDO Office Balagarh”,
“gp”:”Guptipara”,
“block”:”Balagarh”,
“subdivision”:”Chandannagar”,
“district”:”Hooghly”,
“userStatus”: 1,
“userType”: “DEO”,
“statusCode”: 200
}
The API-7 is required to pull the missed data from department. BSK will request to the
department with two parameters from date and to date. Department will reply all the
data received from BSK portal within the dates in JSON Array format only.
✓ Step 1: The API-7 is required to get the service detail which were served to the
department during the start and end date. The all information will be encrypted
standard only. It will be server to server calling.
✓ Step 2: The API will be called by BSK Portal with From_Date and To_Date. Department
will validate the request and response the data as mentioned in the table and the
process of API-7 completes.
BSK Database
BSK Portal
Response: Request:
Service Detail in Array {From Date, To Date}
Departmental
Portal
Department
Database
API-7
Use Case API-7 is called by the BSK once the application is submitted as draft
or final submission along with transaction detail. All the data must
be in JSON Array format only.
HTTP Request POST URL will be provided by the department
Request Body
Response Body
{ [{
“formDate” : “2022-12-10”, “userid”: 9054233544,
“toDate”: ”2022-12-22”, “ticketNo”: 20220811050723,
} “serviceCode”: ”A D/003”,
“appNo” : “123456”,
“ appSubTime ” :
20220811052025,
“deptPayRefNo” : “23424423424”,
“transNo” : “194858535”,
“bankRefNo” : “46535687”,
“paidAmt” : 2500.00,
“message”: “Draft Submitted”,
“applicationStatus”: 2,
“statusCode”: 200
},
{
“userid”: 9054233476,
“ticketNo”: 20220811050744,
“serviceCode”: ”A D/003”,
“appNo” : “765456”,
“ appSubTime ” :
20220811052025,
“deptPayRefNo” : “23424423424”,
“transNo” : “1234353435”,
“bankRefNo” : “4653443656”,
“paidAmt” : 0.00,
“message”: “Final Submitted”,
“applicationStatus”: 2,
“statusCode”: 200
},
{
“userid”: 9854233744,
“ticketNo”: 20220811050723,
“serviceCode”: ”A D/003”,
“appNo” : “123456”,
“ appSubTime ” :
20220811052025,
“deptPayRefNo” : “23424423424”,
“transNo” : “1234353435”,
“bankRefNo” : “4653443656”,
“paidAmt” : 200.00,
“message”: “Draft Submitted”,
“applicationStatus”: 2,
“statusCode”: 200
}
]
There are some parameters whose value is transmitted in request and response. These values
are very important for BSK Portal to generate Management Information Service (MIS) Report.
The parameters and corresponding values are at a glance
Parameter: applicationStatus
Value Description
0 Default value
1 Application Initiated
2 Draft Submission
3 Final Submission
4 Search Application only
5 Download Application
Parameter: documentType
Value Description
0 Default Value
1 URL Link
2 base64Code
3 Image type
4 Another format 1
5 Another format 2
6 Another format 3
Examples:
[Link]
[Link]
[Link]
[Link]
The process of the API integration must be completed in a stipulated time. Just as the
first API integration is completed by completing all FOUR steps. BSK Tech Team
proposes a timeline to complete all the stages of API Integration for seamless andedn
to end delivery of services. If the department is having number of services, then the
stipulated time will be considered accordingly.
14. Definition
JSON Web Token (JWT) is an open standard that defines a compact and self-
contained way for securely transmitting information between parties as a JSON
object. This information can be verified and trusted because it is digitally
signed. In its compact form, JSON Web Tokens consist of three parts separated
by dots (.), which are:
Header: The header typically consists of two parts: the type of the token, which
is JWT, and the signing algorithm being used, such as HMAC SHA256.
alg=>algorithm, typ=>the media type, cty=> the contain type.
Example:
{
"alg": "HS256",
"typ": "JWT"
}
Then, this JSON is Base64Url encoded to form the first part of the JWT.
Payload: The second part of the token is the payload, which contains the
claims. Claims are statements about an entity (typically, the user) and additional
data. There are three types of claims: registered, public, and private claims.
Example:
{
"userid": "9350778825",
“serviceno”:”275”,
"name": "Mahit Sen",
"admin": false
}
Signature: To create the signature part one must take the encoded header, the
encoded payload, a secret, the algorithm specified in the header, and sign it.
HMAC using SHA-256, called HS256 in the JWA spec. if you want to use the
HMAC SHA256 algorithm, the signature will be created in the following way:
Example:
HMACSHA256(
base64UrlEncode(header) + "." +
base64UrlEncode(payload),
secret)
The output is three Base64-URL strings separated by dots that can be easily
passed in HTML and HTTP environments, while being more compact when
compared to XML-based standards such as SAML.
A whitelist, allow list, or pass list is a mechanism which explicitly allows some
identified entities to access a particular privilege, service, mobility, or
recognition. Allowing only preapproved individuals to access your network can
lower the chances that you might encounter a virus, malware or another cyber-
attack. It can also help you share any sensitive information your business might
have with only those you trust.
BSK server has the firewall security and the data receive from other
departmental server through API will be restricted unless the public IP address
has pre-allowed to send data. The pre-allowed implies whitelisting of IP
address. If the department has dynamic public IP, then the DNS (Domain Name
System) need to be whitelisted.
data has been tampered with (data integrity), to increase people’s confidence that they
are communicating with the people they think are communicating with
(authentication) and to be sure that messages were sent and received (non-
repudiation).
Encryption Key: Advanced Encryption Standard (AES) keys are symmetric keys that can be
three different key lengths, BSK uses 256 bits. AES is the encryption standard that is recognized
and recommended. The 256-bit keys are the longest allowed by AES. BSK Tech Team will
provide the decryption key to decrypt the data. It is required to encrypt the data before
sending to network.
Decryption Key: Advanced Encryption Standard (AES) keys are symmetric keys that can be
three different key lengths, BSK uses 256 bits. AES is the encryption standard that is recognized
and recommended. The 256-bit keys are the longest allowed by AES. BSK Tech Team will
provide the decryption key to decrypt the data. It is required to decrypt the data before further
use.
Initialization Vector: An initialization vector (IV) is an arbitrary number that can be used with
a secret key for data encryption to foil cyber-attacks. This number, also called a nonce (number
used once), is employed only one time in any session to prevent unauthorized decryption of
the message by a suspicious or malicious actor. BSK Tech Team will provide that value which
will be required to decrypt the code.
Data: The data will be forwarded from BSK portal only in the JSON format. The variable length
data will be transferred. Based on the requirement of the department, BSK portal will send
accordingly.
a) Encryption Key
b) Initialization Vector
Step 3: call the function for encryption algorithm “AES-256-CBC” and encrypt.
Functions in different language is given for the ready reference.
a) Decryption Key
b) Initialization Vector
Step 3: call the function for decryption algorithm “AES-256-CBC” and decrypt.
Functions in different language is given for the ready reference.
[Link]
Source Code is available for ready reference in multiple languages (Node | Java | PHP)
Prior to run the following code, it is required to keep the two encryption and decryption values. The
sample value is given here for test purpose. For live, each department has different values. BSK Tech
Team will provide the encryption / decryption code.
For the following code, the encryption decryption test keys are as follows:
a) Node
Encryption:
let text =
‘{"userid":"8527419636","ticketno":"20221202153322882","citizenmobile":"996325896
3","citizenname":"Anupam Ghosh"}’
OUTPUT:
m4p3CxxkyshZk6hQdSi509Uu3Gn8i4MXIz/uqgSl40FfH0Hv7M/ThZj3YnAiVLdmuQ4Dd
GEPVLYtOihNsC2c59tkK97qagxo9+rX6hWJem/AilzVNBTsN206liJKiAaoFAKfmaxFAFo/
UmGTrVExKI428RouVxqyechhX0OyIDg=
POST REQUEST:
Department URL: [Link]
Accepted Method: POST
Parameters:
agId: BSK
encData: encryptedData
Decryption:
OUTPUT:
{"userid":"8527419636","ticketno":"20221202153322882","citizenmobile":"996325896
3","citizenname":"Anupam Ghosh"}
b) Java
import [Link];
import [Link];
import [Link];
import [Link].Base64; //[Link] need to
add in class path
// Encryption
public static String encrypt(String value) {
try {
IvParameterSpec iv = new IvParameterSpec([Link]("UTF-8"));
SecretKeySpec skeySpec = new SecretKeySpec([Link]("UTF-8"), "AES");
Cipher cipher = [Link]("AES/CBC/PKCS5PADDING");
[Link](Cipher.ENCRYPT_MODE, skeySpec, iv);
byte[] encrypted = [Link]([Link]());
return Base64.encodeBase64String(encrypted);
} catch (Exception ex) {
[Link]();
}
return null;
}
// Decryption
public static String decrypt(String encrypted) {
try {
IvParameterSpec iv = new IvParameterSpec([Link]("UTF-8"));
SecretKeySpec skeySpec = new SecretKeySpec([Link]("UTF-8"), "AES");
Cipher cipher = [Link]("AES/CBC/PKCS5PADDING");
[Link](Cipher.DECRYPT_MODE, skeySpec, iv);
byte[] original = [Link](Base64.decodeBase64(encrypted));
return new String(original);
} catch (Exception ex) {
[Link]();
}
return null;
}
c) PHP
<?php
echo "<p>Encryption - Decryption ACE-256-CBC</p>\n";
// Encryption
$data='{"userid":"8527419636","ticketno":"20221202153322882","citizenmobile":"996
3258963","citizenname":"Anupam Ghosh"}';
$encryptionKey = "IP16TDW0L5AQB41V6S6J8QLTPLRXBV2W";
$initializationVector = "V0ZMZO6WZ45KY2PL";
$options = 0;
$encryptedData = openssl_encrypt($data, 'aes-256-cbc', $encryptionKey, $options,
$initializationVector);
// Decryption
$decryptionKey = "IP16TDW0L5AQB41V6S6J8QLTPLRXBV2W";
$initializationVector = "V0ZMZO6WZ45KY2PL";
Saadia Azim
Chief Operating Officer
Bangla Sahayata Kendra, PMU
+91 9830047512
[Link]@[Link]
There are major changes of API Integration concepts over the previous versions. BSK-
Tech Team had already integrated with number of departments with previous version
of API documents which will be gradually updated with new architecture. The version
information is given below:
18. Conclusion
The API Integration process is the data flow between two parties with all possible
securities against Unauthorised Access, Denial-of-Service (DoS) attack and followed
the best practices. As the process develops and the scope for new APIs increases, BSK
PMU may add new APIs per the system's requirements.