API Integration Information
1. Technical Integration Process:
Step 1: Integrate using the iSign API in the Sandbox environment.
Step 2: After integration, perform testing in the Sandbox environment and share the test results with A4B for evaluation.
Step 3: Once the test results are confirmed, A4B will provide integration information for the Production environment.
Step 4: Update the information and configure the environment to Production. Conduct testing, and after completion, share the test results with A4B.
Step 5: Deploy the iSign solution to users on your platforms.
2. Integration Environments:
iSign provides two separate environments for integration:
Sandbox: Used for development, testing, debugging, etc.
Production: Officially used for partners.
3. Integration Information:
The APIs are provided as RESTful APIs. iSign provides API key information for partners to use the API in both Sandbox and Production environments.
3.1 Gateway API URL:
Sandbox iSign
https://isign-i3p-uat.a4b.vn/partner
Production iSign
https://isign-i3p.a4b.vn/partner
3.2 HTTP Request Configuration :
Ensure to include the required headers such as Content-Type and x-api-key
Content-Type
application/json; charset=UTF-8
X-API-Key
API Key AWS
Authorization
Basic {Token} (iSign cấp cho đối tác)
3.3 HTTP Response Codes Information :
Standard HTTP response codes will be returned to indicate the status of the API requests.
200
Request successful. The results are returned in JSON format
400
The data format provided is invalid or missing. Error results return details in JSON format
401
API call error could not authenticate. Error results return details in JSON format
500
System error
Last updated