# Webview method
### Connection Process
Step 1: Account Initialization
The partner provides the necessary information for Gotadi to create an agency account in the sandbox environment. The required information includes:
**Company Information:**
* Company Name
* Company Address
* Website Address
**Administrator Information:**
* Full Name
* Email Address
* Phone Number
**Integration Information:**
* Links to the partner’s system (e.g., product link, payment gateway link, etc.)
* Relevant integration documents
* Partner’s public key (RSA public key with a minimum length of 1024 bits)
Step 2: Providing Sandbox Environment Account
Gotadi creates an account based on the information provided by the partner and sends the account details back. The provided information includes:
* **Activation link and login credentials** for Gotadi’s B2B portal (sent to the administrator’s email).
* **Gotadi system endpoint:** ``
* **Gotadi's public key** (RSA public key with a minimum length of 1024 bits).
* **Request header parameters:**
* **API access key:** ``
* **Partner access code:** ``
Step 3: Integration and Testing
The partner activates the account and uses the information from **Step 2** to establish the connection and conduct testing in the sandbox environment.
Step 4: Acceptance Testing
Acceptance Testing in Sandbox and Go-Live
**Note:** During the testing phase, if any bookings require a refund, cancellation, or modification, please follow the instructions below.
Step 5: Training & Customer Support Coordination
Establish a communication channel between Gotadi’s customer support team and the partner.
Prioritize direct communication via OTA applications such as **Skype, Zalo, Viber**, or other suitable platforms.
Conduct **customer support training** (if needed) to ensure optimal service quality from both sides.
### **Webview Interface**
Please refer to the interface at the link below:
{% embed url="" %}
{% hint style="info" %}
Gotadi can customize the color scheme upon request to match the partner's interface.
{% endhint %}
### **Terminology and Abbreviations**
| Viết tắt | Từ đầy đủ | Mô tả |
| -------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| URL | Uniform Resource | Used to reference resources on the Internet. |
| SSL | Secure Sockets Layer | A cryptographic protocol designed to provide secure communication over the Internet. |
| HTTPS | Hypertext Transfer Protocol Secure | A protocol that combines HTTP with SSL or TLS to enable secure information exchange over the Internet. |
| 3DES | Triple DES (3DES hay TDES) | A symmetric key algorithm that applies the DES encryption algorithm three times to each data block. |
| RSA | Rivest–Shamir–Adleman | A public-key cryptographic algorithm. It is the first algorithm suitable for both digital signature generation and encryption. |
| SHA-256 | Secure Hash Algorithm | An algorithm used to transform a specific data segment into a fixed-length output with a high probability of uniqueness. SHA-256 returns a 256-bit result. |
| | Chữ ký điện tử | Information attached to data (text, images, videos, etc.) to identify the owner of that data. |
| M | Mandatory | Mandatory when calling the API |
| O | Optional | Not required when calling the API; this parameter is optional depending on the use case. |
| C | Condition | This field is determined as Mandatory or Optional based on the Condition of another field when calling the API |
### HTTP Response code
| Code | Description |
| ---- | --------------------- |
| 200 | Success |
| 400 | Bad Request |
| 401 | Unauthorized |
| 402 | Forbidden |
| 402 | Not Found |
| 500 | Internal Server Error |
| 503 | Service Unavailable |
### Error code
| Mã lỗi | Mô tả |
| ------ | -------------------------------------------------------------- |
| 00 | Request processed successfully. |
| 01 | Request is being processed. |
| 02 | Request processing failed. |
| 03 | Request rejected due to agency account authentication failure. |
| 04 | Request rejected due to an invalid digital signature. |
| 05 | Request rejected due to data decryption failure. |
| 06 | Request rejected due to an invalid access code. |
| 07 | Request rejected due to incorrect data format. |
| 08 | Request rejected as it has already been processed. |
| 09 | Request not yet provessed. |
| 10 | Account information not found. |
| 99 | Other errors. |
### Customer Email Types
* Successful Reservation – Pending Payment
* Ticket Issued Successfully
* Reservation Failed
* Payment Failed
* Payment Successful – Ticket Not Yet Issued
### **Related Documents**
* Integration Information between Gotadi and the Partner.
* Testing Scenarios.
* Sample Source Code.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://developer.gotadi.com/english/b2b2c-partner/webview-method.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.