Get started on the G2G OpenAPI with our guide on managing your information on G2G. The G2G OpenAPI can provide the following functionalities for our sellers:

• Offer management
• Inventory management

Access keys consist of an access key ID and secret access key.

To access G2G OpenAPI, you will need to request from G2G.

When your request to access G2G OpenAPI is approved, you can create access keys from G2G OpenAPI management page. You authenticate with our API by providing the appropriate key in the request Authorization header. Never share your secret keys. Keep them guarded and secure.

Authentication is handled via HTTP headers, as shown in the table below:

1. Login to https://www.g2g.com/.
   

2. On top right of the menu bar, click on your avatar, select API Integration.
   

3. Request API integration access if you have not gotten permission to use G2G OpenAPI.
   

4. On the API integration page, click "Generate key" to generate the G2G API and Secret key.
   

5. Please copy the secret key and keep it securely. You will not be able to retrieve the secret key if you lose it, only re-generate a new key.
   

6. You can start to send requests to G2G OpenAPI by generating the g2g-signature and adding it to the HTTP request headers.

Upload Code Flow is mainly for Digital Code order.

Top Up only supported in V2

Order Delivery Flow is mainly for Top Up order.

Understand delivery attributes for Top Up

1. Buyer has to fill in Order Information when place order.

2. When you call Get Attributes API, delivery_method_list will be returned in the response.
3. Under delivery_method_list, lookup attribute_group_list.
4. From the Order Information sample image, you will get below response:

{
    "attribute_group_list": [
        {
            "attribute_group_id": "e02308e5",
            "attribute_group_name": "User ID",
            "input_field": "text",
            "input_settings": {},
            "is_required": true,
            "attribute_key": "delivery_info_1",
            "attribute_list": []
        },
        {
            "attribute_group_id": "1759fb6c",
            "attribute_group_name": "Servers (Ragnarok X: Next Generation)",
            "input_field": "dropdown",
            "input_settings": {
                "is_searchable": false
            },
            "is_required": true,
            "attribute_key": "delivery_info_2",
            "attribute_list": [
                {
                    "attribute_id": "98f0250f",
                    "attribute_name": "Aldebaran",
                    "sub_attribute_list": []
                },
                {
                    "attribute_id": "6ab853d2",
                    "attribute_name": "Angeling",
                    "sub_attribute_list": []
                },
                ... // more options
            ]
        }
    ]
}

• The 1st attribute is a text field, which is refers to User ID input and the attribute_key is delivery_info_1.
• The 2nd attribute is a dropdown field, which is refers to Server input and the attribute_key is delivery_info_2.
• You are adviced to use attribute_key for integration instead of attribute_group_id or attribute_group_name.

5. When order is placed, you will receive webhook order.api_delivery and delivery_method_list will be provided in the payload.

{
    "delivery_method_list": [
        {
            "attribute_group_id": "e02308e5",
            "attribute_group_name": "User ID",
            "attribute_key": "delivery_info_1",
            "attribute_id": "",
            "attribute_value": "",
            "value": "hello_world"
        },
        {
            "attribute_group_id": "1759fb6c",
            "attribute_group_name": "Servers (Ragnarok X: Next Generation)",
            "attribute_key": "delivery_info_2",
            "attribute_id": "98f0250f",
            "attribute_value": "Aldebaran",
            "value": ""
        }
    ]
}

6. From the sample payload above,

• delivery_info_1 refers to User ID and hello_world is the User ID provided by buyer.
• delivery_info_2 refers to Servers and Aldebaran is the server chosen by buyer.

The following code snippet is a sample error response that contains an error code and message pair:

{
  "code": 40400001,
  "message": "The requested resource does not exist.",
  "warning": "",
  "request_id": "595285dc-9c43-4b9c-a1e6-0cd9aff5b084",
  "payload": {}
}

When troubleshooting the error, you can divide the error code into two components: REST API HTTP status code and error category code. See the following error code sample:

40400001

• 404 - HTTP status code 404
• 00001 - G2G OpenAPI error code

The following table summarizes the HTTP response codes you may receive from the G2GOpen API.

Please visit https://github.com/g2g-official/open-api-sample to download the sample postman collection as a reference to kickstart your API integration.

Everything about your products.

Everything about your offers.