Blibli Merchant API Documentation v-3.6.0 PDF

2 Dec 2018 MTA API
Documentation
Version 3.6.0
Table of Contents
Table of Contents ..........................................................................................................................................................1
Document History ..........................................................................................................................................................3
1. Overview ....................................................................................................................................................................4
2. API Authentication .....................................................................................................................................................4
2.1 API Token.............................................................................................................................................................4
2.2 API Signature .......................................................................................................................................................6
2.2.1 Build the raw signature based on request meta data .................................................................................6
2.2.2 Get the API client secret ..............................................................................................................................6
2.2.3 Hash using HMAC SHA-256 ..........................................................................................................................7
3. API Sandbox ...............................................................................................................................................................7
4 Token Endpoint ...........................................................................................................................................................9
4.1 [POST] Get token for production .........................................................................................................................9
4.2 [POST] Get token for sandbox ...........................................................................................................................11
4.3 [POST] Refresh token ........................................................................................................................................12
5. Product Component API ..........................................................................................................................................13
5.1 [GET] Get Product List .......................................................................................................................................13
5.2 [GET] Get Product Detail ...................................................................................................................................16
5.3 [GET] Get Attribute List .....................................................................................................................................21
5.4 [GET] Get Category Tree ....................................................................................................................................23
5.5 [GET] Get Product Brands .................................................................................................................................25
5.6 [GET] Get Pickup Point ......................................................................................................................................26
5.7.1 [GET] Get Product in Review List ....................................................................................................................28
5.7.2 [GET] Get Product in Review List Version 2 ....................................................................................................30
5.8 [GET] Get Rejected Product List ........................................................................................................................33
6. Maintain Product API ...............................................................................................................................................35
6.1 [GET] Synchronize Product ................................................................................................................................35
6.2 [GET] Unsynchronize Product ...........................................................................................................................36
6.3 [POST] Create Product .......................................................................................................................................37
6.4 [POST] Update Product Summary .....................................................................................................................41
6.5 [POST] Update Detail Product ...........................................................................................................................43
6.6.1 [POST] Upload Product Image (deprecated, please use Upload Image Version 2) ........................................48
6.6.2 [POST] Upload Product Image Version 2 ........................................................................................................50
7. Order Component API .............................................................................................................................................52
7.1 [GET] Get Order List ..........................................................................................................................................52
Page: 1 | Go to table of contents

Create by agie.falah@gdn-commerce.com
7.2 [GET] Get Order Detail ......................................................................................................................................55
7.3 [GET] Download Shipping Label ........................................................................................................................61
7.4 [GET] Get Airway Bill Information .....................................................................................................................62
7.5 [GET] Get Combine Shipping List .......................................................................................................................64
7.6 [GET] Get Returned Order List ..........................................................................................................................66
7.7 [GET] Get Returned Order Detail ......................................................................................................................69
7.8 [GET] Download Airway Bill Document .............................................................................................................72
8. Fulfill Order API ........................................................................................................................................................74
8.1 [POST] Fulfill Regular Order ...............................................................................................................................74
8.2 [POST] Fulfill Big Product Order ........................................................................................................................77
8.3 [POST] Fulfill BOPIS (Buy Online, Pickup In Store) Order ..................................................................................79
8.4 [POST] Partial Fulfill Order ................................................................................................................................80
8.5 [POST] Settle Order ...........................................................................................................................................81
9. Utility API .................................................................................................................................................................83
9.1 [GET] Get Queue Feed API ................................................................................................................................83
9.2 [GET] Get Queue Feed List ................................................................................................................................85
9.3 [GET] Get Queue Feed Detail ............................................................................................................................87
Appendix ........................................................................................................................................................................0
Appendix I: Create product flow ...............................................................................................................................0
Appendix II: Update product flow .............................................................................................................................1
Appendix III: Order fulfillment flow ..........................................................................................................................0

Document History
No Document What’s new
Version
6 Version 3.3.0 • 5.1 Get Product List API filter by stock value is deprecated
• 5.4 Get Category Tree API response revision
• 6.3 Create Product API explanation improvement about input value of “Brand”
• 6.3 Create Product API, new feature for image path auto correction
• 6.4 Update Product Summary API behavior changes
• 7.1 Order List API new attribute response
• 7.2 Order Detail API new attribute response
• 7.3 Download Shipping Label API explanation improvement
• 7.8 Download Airway Bill Document API, NEW API
• 8.2 Fulfill Big Product API request body revision of “merchantCourier”
• 8.5 Settle Order API, NEW API
• A.III Order fulfillment flow diagram revision
7 Version 3.4.0 • 4.1 Get Token error message improvement
• 6.3 Create Product, improve description about product weight policy
• 7.1 Get Order List, add new attribute response
• 7.2 Get Order Detail, add new attribute response
• 7.8 Download Airwaybill, correction on missing parameter
• 8.4 Partial Fulfill, description improvement
8 Version 3.5.0 • Secret key changes policy
• API Sandbox default account
• 5.3 Get Attribute List, improve explanation about category type mapping
• 5.7.2 Get Product in Review List, new API
• 6.6 Upload Product Image, image file policy
• 7.1 Order List API, new API attributes, new API filters
• 7.2 Order Detail API, new API attributes
• 7.4 Get Airway Bill API, new API attributes
• 7.5 Get Combine Shipping API, new policy and new attributes
• 7.6 Get Returned Order List, new API attributes, new API filters
9 Version 3.5.1 • 7.2 Order Detail API, changes on gdnSku and gdnItemSku
10 Version 3.6 • 5.1 [GET] Get Product List, wrong field name expanation and removed unused field
• 5.8 [GET] Get Rejected Product List, add new API field
• 6.3 [POST] Create Product API, remove unused field
• 6.6.1 [POST] Upload Product Image, will be deprecated, we suggest to use version 2
• 6.6.2 [POST] Upload Product Image Version 2, new API
• 7.1 [GET] Get Order List, add new API field
• 7.2 [GET] Get Order Detail, add new API fields
• 7.5 [GET] Combine Shipping List, add new API fields

1. Overview
MTA-API is a tool that allows merchant to manage their product and order via Application Programming
Interface (API).
Merchant can use the API to fetch product and order data as they want (not limited), but stay monitored.
For transaction API like: create product, update product and post image, will be excuted asynchronously
and merchant is able to see the async process status with “Get Feed Status API”.
Async process have limitation, each merchant only able to make 50 concurrent async request in 2 minutes.
Single async request can contains 100 elements of product/image in the body request.
2. API Authentication
To make a connection, merchant should be able:
1. Get API token to authenticated currenct merchant, the API time to live (TTL) is 1 day. Merchant
must be save the token value in their local system. Merchants are advised not to invoke “Get
Token API” for every API call.
2. Generate a valid signature for every API request, the signature is generated base on current
request metadata.
2.1 API Token

API token is an authentication key to validate each merchant who will access MTA-API. A single token key
can be used to send multiple request while it was still valid. The token expiration time is 1 day. Once it
has been expired, client is able to refresh the expiration time by sending the specified request.
To get the valid token, merchant must have API credential. Merchant can do the API credential registration
in the MTA web page on https://merchant.blibli.com/MTA/api-docs. See registration step below:
Picture 2.1 Go to “Merchant API” page

Picture 2.2 Open “API Client Manager” panel
Picture 2.3 Set your client credential password
The API credential is unique per merchant’s username. After merchant complete the registration, they
can get their token via “Get Token API” and place their credential information like Picture 2.4.

Picture 2.4 Putting API credential when get token, using postman
2.2 API Signature

API signature is used as second layer of authentication mechanism. Client should generate the signature
for every request. The signature will be valid until 15 minutes for specified request. Here is a mechanism
to generate signature:
2.2.1 Build the raw signature based on request meta data

The string pattern are:
{Request method}
{MD5 of request body}
{Content type}
{Current date}
{URL request}
Raw Signature Example for POST request Raw Signature Example for GET request
POST\ndd50f190b5bce5deca42dfa3dbea08a3\napplication/json\nMon GET\n\n\nMon May 16 14:07:15 WIB
May 16 14:07:15 WIB 2016\n/mtaapi/api/businesspartner/v1/feed/status
2016\n/mtaapi/api/businesspartner/v1/product/updateProduct
2.2.2 Get the API client secret

API client secret will combined with the raw signature to generate the valid signature. The secret key is
unique per merchant code. Merchant can register their secret key API Client Manager panel, see Picture
2.5. Merchant can revoke their secret key, if they wannna disconnect their API integration.
The secret key is cached for 1 hour, so if merchant changing the secret key, it will take 1 hour to apply the
changes.

Picture 2.5 Set your client secret key
2.2.3 Hash using HMAC SHA-256

The final step is combine the signature string pattern and API client secret then hash using HMAC SHA-
256. Read these following reference about HMAC SHA-256 mechanism:
https://kayako.atlassian.net/wiki/display/DEV/Generating+an+API+Signature
http://www.jokecamp.com/blog/examples-of-creating-base64-hashes-using-hmac-sha256-in-different-languages/#java
The signature will be attached on every request header for x-blibli-mta-authorization, see Picture 2.6.
Picture 2.6 Placing API signature using postman
3. API Sandbox
MTA API also provide sandbox environment, so it help the customer to do API integration testing without
affecting production data. The sandbox environment provide API contract (request and response
validation) with static data. To work on sandbox environment, you can use this value of mentioned
parameter as follows:
Parameter name Parameter value Response result
Will pass the merchant validation and return the API
businessPartnerCode BLI-17103
response successfully
Will pass the merchant validation and return the null list
businessPartnerCode BLI-27103
of API response
Will pass the category validation and return the API
categoryCode / masterCategoryCode FX-1000004
response successfully

Will pass the category validation and return the null list of
categoryCode / masterCategoryCode FX-2000004
API response
storeId 10001 Will return API response of current store ID
requestId (for get feed API) 001-1001 Will return success and finished queue process
requestId (for get feed API) 002-1002 Will return failed and finished queue process
requestId (for get feed API) 003-1002 Will return success and unfinished queue process
Marked as valid Blibli product SKU in sandbox
productSKU SKU-16005-0001
environment
Marked as valid Blibli product item SKU in sandbox
productItemSKU SKU-16005-0001-0001
environment
orderNumber 15000026173 Marked as valid order number in sandbox environment
orderItemNumber 25000026173 Marked as valid order number in sandbox environment
You can use following account to connect (Get Token) in sandbox environment
username: mta-api-sandbox
password: sandbox-secret-key

4 Token Endpoint
4.1 [POST] Get token for production
URL Production : https://api.blibli.com/v2/oauth/token
Purpose : get the token to validate the specified client ID
Authorization request:
Attribute name Attribute value Description
type Basic Auth Authrorization type for get token API
username {api-username} API client username, based on Blibli API agreement for each merchant
password {api-password} API client password, based on Blibli API agreement for each merchant
Header request:
application/x-www- Content type for get token request using x-www-form-urlencoded
Content-type
form-urlencoded
Accept application/json Accept type for the API result
Body request: (set body type to application/x-www-form-urlencoded)
grant_type password The value of API grant type
username {mta-username} MTA web username for specified merchant
password {mta-password} MTA web password for specified merchant
Note: if you hit this API with invalid MTA username up to three times, your MTA username will be locked. You
need to reset password for your MTA account.
Success response
{
"access_token": "1e1ab274-b8dd-4b21-9323-0d1c85f7091d",
"token_type": "bearer",
"refresh_token": "0468d301-af86-4482-ba17-144b642e19f5",
"expires_in": 86400,
"scope": "read write trust"
}
Attribute name Description
access_token API token that used as an authentication key
refresh_token Refresh token key that will be used to refresh the token expiration time
expires_in Token expiration time in seconds, 86400 seconds = 1 day
Failed response due to invalid client api username/password

{
"error": "unauthorized",
"error_description": "Bad credentials"
}
Failed response due to invalid mta username/password. Please be carefull with this case. If client hit “Get Token API”
with wrong MTA account up to three times, the MTA account will be locked.
{
"error": "INVALID_PASSWORD",
"error_description": "Username or password you entered is not appropriate"
}
Failed response due to locked MTA account
{
"error": "USER_LOCKED",
"error_description": "Username is locked"
}
Failed response due to inactive MTA account, please contact merchant assistant

{
"error": "USER_INACTIVE",
"error_description": "Username is inactive"
}

4.2 [POST] Get token for sandbox
URL : https://apisandbox.blibli.com/v2/oauth/token
Purpose : get the token to validate the specified client ID
{ api-sandbox- API client username, based on Blibli API agreement for each merchant
username
username}
{api-sandbox- API client password, based on Blibli API agreement for each merchant
password
password}
Header request:
Content-type
form-urlencoded
grant_type client_credentials The value of API grant type
Success response
{
}

4.3 [POST] Refresh token
URL : https://api.blibli.com/v2/oauth/token
Purpose : refresh the token expiration time to 1 day
username {api-username} API client username, based on Blibli API agreement for each merchant
password {api-password} API client password, based on Blibli API agreement for each merchant
Header request:
Content-type
form-urlencoded
grant_type refresh_token The value of API grant type
client_id {api-username} API client username, based on Blibli API agreement for each merchant
refresh_token {refresh-token} Refresh token key, obtained from “get token API” on section 4.1
Success response
{
}
Failed response due to invalid api username

{
"error": "invalid_client",
"error_description": "Given client ID does not match authenticated client"
}
Failed response due to invalid refresh token key
{
"error": "invalid_grant",
"error_description": "Invalid refresh token: 5a53c0f2-c29d-4964-b677-03946267f318"
}

5. Product Component API
5.1 [GET] Get Product List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/getProductSummary
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/getProductSummary
Purpose : get product list from specified merchant by based on filter parameter
Note.
This API will return single product item list for current merchant
Authorization request: No Auth
Header request:
Authorization bearer {token-key} Token key is obtained from “get token API”
x-blibli-mta-authorization BMA {mta-username}:{api-signature} API signature is generate by client like explained in section 2.2
x-blibli-mta-date-milis {current-milli-second} Get this value from: http://currentmillis.com as a reference
Accept application/json Accept type for the current request
Content-Type application/json Content type for the current request
requestId {client-request-id} Unique request ID that generated for each client request
sessionId {client-session-id} Unique session ID that generated for each client session
username {mta-username} MTA web username
Body request: Not necessary
Parameter request:
businessPartnerCode {merchant-code} Merchant code value for specified merchant partner
gdnSku {gdn-item-sku} Filter product list by GDN Item SKU, like: TOQ-15130-00060-00001
productName {product-name} Filter product list by product name using “LIKE” operation
categoryCode {category-code} Filter product list by category code
salePrice {sale-price} Filter product list by category code
pickupPointCode {pickup-point-code} Filter product list by pickup point code
stock {product-stock} Filter product list by product stock
Filter product list by stock value is deprecated
page {page-list} Filter product list by page list index, the default value is 0
size {list-size} Filter product list by size list, the default value is 10
Note: the underlined attribute is an optional parameter
Success response
{
"requestId": "4613cbb6-7ca9-4932-9d31-8e4e4634a159",
"errorMessage": null,
"errorCode": null,
"success": true,
"content": [
{
"gdnSku": "TOA-15142-00069-00001", //this field name is gdnSku but the field value is itemSku, please expect that its contain itemSKU
"productName": "PRO ATT 6 Brick Red",
"productItemCode": "MTA-0300002-00002",
"merchantSku": "SKU-0001",
"regularPrice": 15000,
"sellingPrice": 15000,
"stockAvailableLv2": 36,
"stockReservedLv2": 914,
"productType": "REGULAR",
"pickupPointCode": "PP-3000197",
"pickupPointName": "pick up point argo",
"displayable": false,
"buyable": true,

"autohide": null,
"image": https://blibli.com/images/catalog/full/nike_nike-free-rn-831508-001-sepatu-lari_full01.jpg,
"synchronizeStock": false
},w
…………… product-list-2
…………... product-list-n
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 54
}
}
gdnSku Product GDN SKU, this SKU is generated by Blibli system
productName Name of current product
productItemCode Product item code value for current product
merchantSku Product merchant SKU, this SKU is generated by merchant
regularPrice Regular price for current product
sellingPrice Sale price for current product
Product available stock is the number of stock which be able to purchased by
stockAvailableLv2
customer
Product reserved stock is the number of stock which reserved by customer, since
stockReservedLv2
order created until delivired.
The product type based on shipping method, that is:
• REGULAR : regular product
productType
• BIG PRODUCT : shipped by merchant
• BOPIS : bopis product, like: ticket, voucher, etc
pickupPointCode The pickup point code for current product
pickupPointName The pickup point name for current product
The displayable status for current product, if displayable is false then the product
displayable
will not displayed on blibli.com
The buyable status of current product, if buyable is false then the product is can’t
buyable
bought by customer
image The main image for current product
pageMetaData Page metadata information for product list result
pageSize Page size for current product list
pageNumber Page number information for current product list
totalRecords Total record of product list that able to get by current filter
Synchronize stock status:
• If it true then the product is able to bought based on Lv 1 stock, even the Lv
synchronizeStock 2 is larger.
• If it false then the product is able to bought based on Lv 2 stock, Lv 1 stock
will abandoned.
Failed response due to invalid business partner/merchant code

{
"requestId": "9986a0a7-f3d6-4b26-93ee-d8f89770abf9",
"errorMessage": "Invalid input data :Business partner code must not be empty",
"errorCode": "NO_DATA",
"success": false,
"content": [],
"pageMetaData": {
"pageSize": 0,
"pageNumber": 0,
"totalRecords": 0
}

}
Raw signature example Raw signature example (sandbox)
GET\n\n\nMon May 16 14:07:15 WIB GET\n\n\nMon May 16 14:07:15 WIB 2016\n/mtaapi-sandbox
2016\n/mtaapi/api/businesspartner/v1/product/getProductSummary /api/businesspartner/v1/product/getProductSummary

5.2 [GET] Get Product Detail
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/detailProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/detailProduct
Purpose : get product detail based on product GDN SKU
Note.
This API will return single product item detail based on request parameter value
Header request:
Parameter request:
gdnSku {gdn-item-sku} Get product detail by product item GDN SKU, ex: TOQ-15130-00006-00001
username {mta-username} MTA web username for specified merchant
Success response
{
"errorCode": null,
"success": true,
"value": {
"productSku": "TOS-16005-00004",
"productCode": "MTA-0267411",
"businessPartnerCode": "TOS-16005",
"synchronize": false,
"productName": "Xiaomi MI 5 Smartphone - Black [3 GB/ 32 GB/ Garansi Distributor]",
"productType": 2,
"categoryCode": "10249",
"categoryName": "Android",
"categoryHierarchy": "Handphone & Tablet > Handphone > Android",
"brand": "Xiaomi",
"description": "Xiaomi MI 5 Smartphone - Black [3 GB/ 32 GB/ Garansi Distributor], hadir dengan layar berukuran 5.0 Inch
dan sistem operasi Android OS",
"specificationDetail": "<ul><li>Brand<ul><li>Xiaomi</li></ul></li><li>Kamera<ul><li>16 MP & 4 MP</li></ul></li><li>Kapasitas
Baterai<ul><li>3000 mAh</li></ul></li><li>Memory<ul><li>3 GB RAM</li></ul></li><li>Operating System<ul><li>Android
OS, v6.0 (Marshmallow)</li></ul></li><li>Sim Card<ul><li>Dual-SIM\nNano-SIM</li></ul></li><li>Ukuran
Layar<ul><li>5.15 Inch</li></ul></li><li>Memori Internal<ul><li>32 GB ROM</li></ul></li><li>Slot Memori
Eksternal<ul><li>No</li></ul></li><li>Chipset<ul><li>Qualcomm MSM8996 Snapdragon 820</li></ul></li></ul>",
"uniqueSellingPoint": "<ul>\n<li>OS : Android OS, v6.0 (Marshmallow)</li>\n<li>Chipset : Qualcomm MSM8996 Snapdragon
820</li>\n<li>Memori : Internal 32 GB & RAM 3 GB</li>\n<li>Kamera : Belakang 16 MP & Depan 4
MP</li>\n<li>Layar : 5.0 Inch</li>\n</ul>",
"productStory": "",
"items": [
{

"itemSku": "TOS-16005-00004-00001",
"skuCode": "MTA-0267411-00001",
"merchantSku": null,
"upcCode": "XIA-MI-5-SMART-BLK",
"itemName": "Xiaomi MI 5 Smartphone - Black [3 GB/ 32 GB/ Garansi Distributor]",
"length": 20,
"width": 10,
"height": 10,
"weight": 1,
"shippingWeight": 1,
"dangerousGoodsLevel": 0,
"lateFulfillment": false,
"pickupPointName": "Haneda Store",
"availableStockLevel1": null,
"reservedStockLevel1": null,
"availableStockLevel2": 1087,
"reservedStockLevel2": 3,
"minimumStock": 0,
"synchronizeStock": false,
"off2OnActiveFlag": false,
"prices": [
{
"channelId": "DEFAULT",
"price": 400000,
"salePrice": 350000,
"discountAmount": null,
"discountStartDate": null,
"discountEndDate": null,
"promotionName": null
}
],
"viewConfigs": [
{
"display": false,
"buyable": false
}
],
"images": [
{
"mainImage": true,
"sequence": 0,
"locationPath": " https://blibli.com/images/catalog/full//xiaomi_xiaomi-mi-5-smartphone---black--3-gb--32-gb--garansi-
distributor-_full03.jpg"
}
],
"cogs": null
}
],
"attributes": [
{
"attributeCode": "CH-0036989",
"attributeType": "DESCRIPTIVE_ATTRIBUTE",
"values": [
"Qualcomm MSM8996 Snapdragon 820"
],
"skuValue": false,

"attributeName": "Chipset",
"itemSku": null
},
{
"attributeCode": "SL-0037089",
"values": [
"No"
],
"skuValue": false,
"attributeName": "Slot Memori Eksternal",
"itemSku": null
},
{
"attributeCode": "BR-M036969",
"attributeType": "PREDEFINED_ATTRIBUTE",
"values": [
"Xiaomi"
],
"skuValue": false,
"attributeName": "Brand",
"itemSku": null
},
],
"images": [
{
"mainImage": true,
"sequence": 0,
"locationPath": "https://blibli.com/images/catalog/full/xiaomi_xiaomi-mi-5-smartphone---black--3-gb--32-gb--garansi-
distributor-_full03.jpg"
}
],
"url": null,
"installationRequired": false
}
}
productSku Product GDN SKU, this SKU is generated by Blibli system
productCode Product code information
businessPartnerCode Business partner/merchant partner code
synchronize Synchronize status:
• If it true then the product data is synchronize with the master data.
Merchant can’t edit current product if the sync status is true.
• If it false then the product data is not synchronized with the master data.
Merchant is able to edit the value of the product data.
Note: if merchant switch the sync status become true, then the product data will be
reloaded like as master data.
productName Product name information
productType
categoryCode Category code for the current product
categoryName Category name for the current product
Category hierarchy for the current product, using “>” as separator. For example:
categoryHierarchy
Handphone & Tablet > Handphone > Android
brand Product brand information

description Product description information
specificationDetail Specification detail for the current product
uniqueSellingPoint Unique selling point for the current product
productStory Product story information
Product items information, usually 1 master product has several product items.
items
The product item is contains different variant.
Product item SKU that generated by Blibli system.
itemSku Note: product item SKU is not same like productSku, each product item has different
product item SKU
skuCode Product item code information, it’s not same like productCode
merchantSku Product item merchant SKU, this SKU is generated by merchant partner
upcCode Universal product code, like barcode and etc
itemName Product item name information
length Product length information in centimeters
width Product width information in centimeters
height Product height information in centimeters
weight Product weight information in kilograms
Product shipping weight information in kilograms, this value is calculated by Blibli
shippingWeight
system
Dangerous goods level information, that is:
• Lv 0: non dangerous goods
• Lv 1: dangerous goods that contains liquid, like: alcohol, aseton, etc
dangerousGoodsLevel
• Lv 2: dangerous goods that contains: explosive product, flammable product,
poison & infectious substances, radioactive product, corrosive product, and
magnetized product.
Late fulfillment status:
• If it true then the product is buyable even the merchant is in close store
lateFulfillment state
• If it false then the product is no buyable when merchant is in close store
state
pickupPointCode Pikcup point code information for current product item
pickupPointName Pickup point name information for current product item
Available stock for Blibli’s warehouse product (just for several merchant).
availableStockLevel1 Product available stock is the number of stock which be able to purchased by
customer.
Reserved stock for Blibli’s warehouse product (just for several merchant).
reservedStockLevel1 Product reserved stock is the number of stock which reserved by customer, since
Product available stock is the number of stock which be able to purchased by
availableStockLevel2
customer
Product reserved stock is the number of stock which reserved by customer, since
reservedStockLevel2
This is product minimum stock, if product current stock is below minimumStock
then merchant will be notified. If up to 4 days, the current stock is below
minimumStock
minimumStock, then the product will automatically become unbuyable and
undisplayable.
• If it true then the product is able to bought based on Lv 1 stock, even the Lv
synchronizeStock 2 is larger.
• If it false then the product is able to bought based on Lv 2 stock, Lv 1 stock
will be abandoned.
Offline to online flag for the current product. which allow customer to buy the
off2OnActiveFlag product as offline but do the payment by online in Blibli.com. Please contact our
trade & partnership PIC about this business flow.
prices The product prices information for the current product
channelId Channel ID for the current product
price Product price information

salePrice Product sale price information
discountAmount Product discount price information
discountStartDate Product discount start date
discountEndDate Product discount end date
promotionName Promotion name for specified product price
viewConfigs Viewable configuration for current product
Displayable status:
• If it true then the product will displayed on blibli apps
display
• If it false then the product will not displated on blibli apps and only
displayed on merchant apps
Buyable status:
buyable • If it true then the product is able to bought by customer
• If it false then the product is can’t to bought by customer
images Product images information
mainImage Main image flag, if true then it will displayed as main image on product list page
sequence The image sequence on product detail page, start from 0
locationPath Product image location path information
cogs Product Cost of Goods Sold (COGS) information, it’s generated by Blibli’s system
attributes Product attributes information
attributeCode Attribute code information
Atrrbute type information, contains:
• DESCRIPTIVE_ATTRIBUTE: attribute that defined by merchant, like:
operating system, screen size, etc
attributeType • PREDEFINED_ATTRIBUTE: attribute that defined by Blibli, like: product
operating system that able to sell in Blibli apps, etc
• PREDEFINING_ATTRIBUTE: attribute that indicate the product variant like:
size, colour, etc
values Product attribute value information
• If it true then merchant must fill the attribute data
skuValue • If it false then attribute name will be derived from master data if merchant
not filled the attribute data
attributeName Attribute name information
itemSku Information for product item SKU
url Other product promotion url, like: youtube link video and so on
Product installation status, that is:
installationRequired • If it true then the product is needs to installed when received by customer,
like: sport equipment, bike, etc

GET\n\n\nMon May 16 14:07:15 WIB GET\n\n\nMon May 16 14:07:15 WIB 2016\n/mtaapi-sandbox
2016\n/mtaapi/api/businesspartner/v1/product/detailProduct /api/businesspartner/v1/product/detailProduct

5.3 [GET] Get Attribute List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/getCategoryAttributes
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/getCategoryAttributes
Purpose : get attribute list for specified category.
Note.
This API is used to determine the mandatory attribute for current category. It required to build body request for 6.3 Create Product
API.
Header request:
Parameter request:
categoryCode {category-code} Filter attribute list result by specified category code
Success response
{
"requestId": "bc9795a7-e756-4962-b023-e625eecd5f38",
"errorCode": null,
"success": true,
"value": {
"name": "Baju Kerja",
"attributes": [
{
"attributeCode": "GA-0036802",
"name": "Material"
"options": []
},
{
"attributeCode": "TI-M000161",
"name": "Tipe Atasan",
"options": [
"Blouse",
"Tunik",
"Tank Top",
"Polo",
"Kemeja",
"Kaos",
"Etnik",
"Batik"
]
},

{
"attributeCode": "WA-M000319",
"attributeType": "DEFINING_ATTRIBUTE",
"name": "Warna",
"options": [
"Black",
"Blue",
"Green",
"Grey"
]
},
{
"attributeCode": "OU-2000004",
"attributeType": "DEFINING_ATTRIBUTE",
"name": "Ukuran",
"options": [
"Semua Ukuran",
"XS",
"S",
"M",
"L"
]
}
]
}
}
categoryCode Category code for current attribute list
name Category name for current attribute list
attributes List of attributes for current category
attributeType Attribute type information, contain:
• DESCRIPTIVE_ATTRIBUTE: attribute that allow merchant able to fill with free
text value
• PREDEFINED_ATTRIBUTE: attribute that restrict merchant to choose only one
option of the lists
• DEFINING_ATTRIBUTE: attribute that restrict merchant to choose one or more
options from the lists. The choosen attributes will mapped into product items
DESCRIPTIVE_ATTRIBUTE and PREDEFINED_ATTRIBUTE is used as product feature

DEFINING_ATTRIBUTE is used as product variant
name Attribute name information
options Atrribute options value for current attribute, defined by Blibli

GET\n\n\nMon May 16 14:07:15 WIB GET\n\n\nMon May 16 14:07:15 WIB 2016\n/mtaapi-
2016\n/mtaapi/api/businesspartner/v1/product/getCategoryAttributes sandbox/api/businesspartner/v1/product/getCategoryAttributes

5.4 [GET] Get Category Tree
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/getCategory
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/getCategory
Purpose : get eligible category tree for current merchant

Header request:
Parameter request:
Success response
{
"requestId": "efc984b1-5174-4390-aa93-a261388ae52c",
"errorCode": null,
"success": true,
"content": [
{
"categoryCode": "CO-1000048",
"categoryName": "Computer",
"children": [
{
"categoryCode": "DE-1000037",
"categoryName": "Desktop"
},
{
"categoryCode": "LA-1000062",
"categoryName": "Laptop"
}
]
},
{
"categoryName": "Fashion Pria",
"children": [
{
"categoryName": "Jam Tangan",
"children": [
{
"categoryName": "Jam Tangan Casual"
},
{

"categoryName": "Jam Tangan Fashion"
},
{
"categoryName": "Jam Tangan Sport"
}
]
},
{
"categoryName": "Baju Batik & Etnik",
"children": [
{
"categoryName": "Luaran Batik"
},
{
"categoryName": "Baju Etnik"
}
]
},
{
"categoryName": "Tas & Aksesoris",
"children": [
{
"categoryName": "Ikat Pinggang"
},
{
"categoryName": "Sunglasses"
},
]
},
]
}
categoryCode Category code for current merchant partner
name Category name information
children Category child from current category partner

2016\n/mtaapi/api/businesspartner/v1/product/getCategory sandbox/api/businesspartner/v1/product/getCategory

5.5 [GET] Get Product Brands
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/getBrands
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/getBrands
Purpose : get product brands base on filter parameter

Header request:
Parameter request:
masterCategoryCode {category-code} The specified category code (category level 1), to verify that specified category is
supported with brand data as an attribute
brands {brands-filter} To filter the brands list using “LIKE” operator
page {page-list} To filter the brands list based on page index, default value is 0
size {list-size} To filter the brands list based on list size, default value is 10
Success response
{
"requestId": "c5ad0d8c-70d0-4f82-97aa-f1e5d20d117e",
"errorCode": null,
"success": true,
"value": [
"Acerola",
"WR ACERBIS",
"Apacer",
"Acerbis",
"Acer"
]
}
value Brands list value information

2016\n/mtaapi/api/businesspartner/v1/product/getBrands sandbox/api/businesspartner/v1/product/getBrands

5.6 [GET] Get Pickup Point
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/getPickupPoint
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/getPickupPoint
Purpose : get pickup point list for specified merchant partner

Header request:
Parameter request:
Success response
{
"requestId": "73b87463-9550-4a1d-b7bd-2a955559cdff",
"errorCode": null,
"success": true,
"content": [
{
"createdDate": 1478498478663,
"createdBy": "account@gdn-commerce.com",
"updatedDate": 1479876246783,
"name": "Haneda Store",
"code": "PP-3000408"
},
{
"createdDate": 1479734383070,
"updatedDate": 1479876246836,
"name": "Store Singapore",
"code": "PP-3000495"
},
{
"createdDate": 1479870914182,
"updatedDate": 1479876246953,
"name": "tokyo towncenter",
"code": "PP-3000517"
}
]
}
name Pickup point name information
code Pickup point code information
createdBy Pickup point data creator
createdDate Pickup point created date, in epoch time format

updatedDate Pickup point last updated date, in epoch time format
2016\n/mtaapi/api/businesspartner/v1/product/getPickupPoint sandbox/api/businesspartner/v1/product/getPickupPoint

5.7.1 [GET] Get Product in Review List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/inProcessProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/inProcessProduct
Purpose : to get product in review list. After merchant create new product, it will reviewed by Blibli and not displayed in the
website directly.

Header request:
Parameter request:
Success response
{
"errorCode": null,
"success": true,
"content": [
{
"id": "216ab946-e0df-43a0-9ad2-528977b7fd0b",
"storeId": "10001",
"createdDate": 1485424298774,
"createdBy": "system",
"updatedDate": 1485424298774,
"updatedBy": "system",
"businessPartnerId": "BLI-17103",
"productId": "eae2b4dc-ed46-4dc3-a163-3850e3901dbd",
"gdnProductSku": "SKU-00001-00002",
"activated": false,
"productName": "Product name",
"categoryName": "Handphone dan Tablet",
"brand": "Samsung",
"productItemBusinessPartners": [
{
"id": "f5aef2e7-1bf0-475c-98a5-5bbaf587c97a",
"storeId": "10001",
"createdDate": 1485424298774,
"updatedDate": 1485424298774,
"updatedBy": "",
"productItemId": "2e2bafcf-9452-4715-a24e-bda89958ede4",
"productType": 1,
"gdnProductItemSku": " SKU-00001-00002-00001",
"price": 100000,
"salePrice": 120000,

"saleStartDate": null,
"saleEndDate": null,
"stock": 12,
"minimumStock": 1,
"pickupPointId": "PP-0001",
"display": false,
"buyable": false,
"installation": false
}
],
"productBusinessPartnerAttributes": null
}
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 5
}
}
storeId Product store ID
createdBy Product data creator
createdDate Product created date, in epoch time format
updatedBy PIC which updated data product
updatedDate Pickup point last updated date, in epoch time format
businessPartnerId Merchant code for current product data
productId Product ID information
gdnProductSku Blibli product SKU
activated Product activation status
categoryName Category name of current product
brand Product brand
productItemBusinessPartners Product item information
productItemId Product item ID
productType The product type based on shipping method, that is:
gdnProductItemSku Blibli product item SKU
price Product item price
salePrice Product item sale price
saleStartDate Product sale price start date
saleEndDate Product sale price end date
stock Product stock information
minimumStock Input of current minimum stock, set to 1 if minimum stock is not
defined by business agreement
pickupPointId Product pickup point ID
display Product is displayable status
buyable Product is buyable status
installation Product is installation required status

2016\n/mtaapi/api/businesspartner/v1/product/inProcessProduct sandbox/api/businesspartner/v1/product/inProcessProduct

5.7.2 [GET] Get Product in Review List Version 2
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v2/product/inProcessProduct
URL Sandbox :-
Purpose : to get product in review list. After merchant create new product, it will reviewed by Blibli and not displayed in the
website directly.
This API is version 2 from previous API, this API allow merchant to check whether product’s image is already uploaded with valid
mapping or not.
Header request:
Parameter request:
Success response
{
"errorCode": null,
"success": true,
"content": [
{
"productName": "Kemeja Bagus",
"brand": "Warwolf",
"length": 2,
"width": 2,
"weight": 0.022,
"height": 2,
"shippingWeight": 0.02,
"url": "-",
"description": "PHA+S2VtZWphIEJhZ3VzPC9wPg==",
"uniqueSellingPoint": "Kemeja Bagus",
"productStory": "-",
"specificationDetail": "<ul><li>Care Label<ul><li>afasdf</li></ul></li><li>Warna<ul><li>Forrest Green</li><li>Brick
Red</li><li>Black/Violet</li></ul></li><li>Material<ul><li>arvserdzfre</li></ul></li><li>Ukuran<ul><li>Semua
Ukuran</li></ul></li><li>Brand<ul><li>Warwolf</li></ul></li></ul>",
"productImages": [
{
"imagePath": "/full/MTA-0307414/warwolf_kemeja-bagus_full01.jpg",
"sequence": 0,
"active": false,
"mainImage": true,
"uploaded": true
},

{
"sequence": 1,
"active": false,
"mainImage": false,
"uploaded": true
},
{
"sequence": 2,
"active": false,
"mainImage": false,
"uploaded": true
}
],
"categoryName": "Baju Kerja",
"activated": true,
"viewable": false,
"productItems": [
{
"generatedItemName": "Kemeja Bagus Semua Ukuran Forrest Green",
"upcCode": "12345",
"productItemCode": "MTA-0307414-00003"
},
{
"generatedItemName": "Kemeja Bagus Semua Ukuran Brick Red",
"upcCode": "213124",
},
{
"generatedItemName": "Kemeja Bagus Semua Ukuran Black/Violet",
"upcCode": "213124",
}
]
},
{
Element-2 …………….
}
]
}
height Product weight information in kilograms
weight Product height information in centimeters
shippingWeight Product shipping weight information in kilograms, this value is
calculated by Blibli system
productImages List of product images

imagePath Product image location path information
sequence The product’s image sequence on product detail page, start from 0
active Product image status, if true then the specified image is already
approved by QC (Quality Control) team
mainImage Main image flag, if true then it will displayed as main image on product
list page
uploaded This attribute indicate whether current product image is already
uploaded or not.
If you using API integration you must check this attribute to ensure
that your product image is uploaded and well mapped into your
specified product.
activated If true it already approved in QC phase 1
viewable If trus it already approved in QC phase 2
productItems Product items information, the product item list is generated based on
product varian
generatedItemName Product item name information, it’s generated by Blibli system based
on product name and specified product’s variant
productItemCode Product item code information

2016\n/mtaapi/api/businesspartner/v2/product/inProcessProduct sandbox/api/businesspartner/v2/product/inProcessProduct

5.8 [GET] Get Rejected Product List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/rejectedProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/rejectedProduct
Purpose : to get rejected product list, so merchant is able to know whether his new product is rejected or not.

Header request:
Parameter request:
Success response
{
"errorCode": null,
"success": true,
"content": [
{
"productName": "Product Merchant 1",
"categoryName": "Smartphone",
"brand": "Lenovo",
"submitDate": 1472203006457,
"initiator": "system",
"rejectedReason": "product description is not valid",
"rejectedDate": 1472469892264,
"productCode": "MTA-0305289"
},
{
"productName": "Product Merchant 54",
"categoryName": "Smartphone",
"brand": "Sony",
"submitDate": 1472203006457,
"initiator": "system",
"rejectedReason": "please improve the product image quality",
"rejectedDate": 1472469892264,
"productCode": "MTA-0305289"
}
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 2
}
}

categoryName Category name information for current product
Brand Product brand information
submitDate Submited date for the current new product request, in epoch time
format
initiator Initiator identifier that do the product review
rejectedReason Rejected reason for current new product request
rejectedDate Rejected date information for current new product request, in epoch
time format

2016\n/mtaapi/api/businesspartner/v1/product/rejectedProduct sandbox/api/businesspartner/v1/product/ rejectedProduct

6. Maintain Product API
6.1 [GET] Synchronize Product
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/syncProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/syncProduct
Purpose : synchronize product web data with master data, the product web data will be returned from master data.
Note.
Product master data for iPhone 6 is “abc”, when merchant change their product web data into “def” then hit this API, his product web
data will become “abc” again, which is returned from product master data.
Header request:
Parameter request:
requestId {request-id} Unique request ID that generated for each client request
productSku {product-sku} Product SKU value
Success response
{
"errorCode": null,
"success": true
}
success As indicator whether the current request is success or not

2016\n/mtaapi/api/businesspartner/v1/product/syncProduct sandbox/api/businesspartner/v1/product/syncProduct

6.2 [GET] Unsynchronize Product
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/unsyncProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/unsyncProduct
Purpose : unsynchronize product web data with master data, merchant partner is able to edit the product web data when it
already unsynchronized.
Note.
Merchant can’t update his product detail if it still synced with master data. So it must unsynced first then merchant will able to update
the product detail data. But 6.5 Product Detail Product API will do product unsynced automatically.
Header request:
Parameter request:
requestId {request-id} Unique request ID that generated for each client request
productSku {product--sku} Product SKU value
Success response
{
"errorCode": null,
"success": true
}

2016\n/mtaapi/api/businesspartner/v1/product/unsyncProduct sandbox/api/businesspartner/v1/product/unsyncProduct

6.3 [POST] Create Product
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/createProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/createProduct
Purpose : to create new product data, this is a bulk request. Merchant partner is able to create 100 new product in 1
request. The request will be queued, then merchant partner is able to check the queue status with “Get Queue Feed API”.
Note.
Create product API have auto correction feature for product’s image path. The default value is true, is you want to deactive this
feature you can set request parameter of “validateImagePath” to false.

Header request:
Parameter request:
validateImagePath Boolean: true or false It’s to indicate whether auto correction feature for product
image path will be activated or not
Body request:
{
"merchantCode": "TOQ-15130",
"products": [
{
"merchantCode": "TOQ-15130",
"categoryCode": "OL-1000044 ",
"productName": "Product Merchant",
"url": "https://www.youtube.com/merchant-video",
"merchantSku": "MY-SKU-0111",
"tipePenanganan": 1,
"price": 10000,
"salePrice": 8000,
"stock": 12,
"minimumStock": 1,
"length": 1,
"width": 2,
"height": 1,
"weight": 15,
"desc": "This is new merchant product",
"uniqueSellingPoint": "Unique selling point of current product",
"productStory": "This product is launched at 25 Des 2016, made in Indonesia",
"upcCode": "1231230010",
"display": false,
"buyable": true,
"installation": false,
"features": [
{
"name": "Brand",
"value": "Samsung"
},

{
"name": "Berat",
"value": "5 Kg"
},
{
"name" : "Dimensi Produk",
"value" : "50cm x 40cm"
}
],
"variasi": [
{
"name": "Warna",
"value": "Black"
},
{
"name": "Warna",
"value": "Red"
},
{
"name": "Ukuran",
"value": "35"
},
{
"name": "Ukuran",
"value": "36"
}
],
"images": [
{
"locationPath": "samsung_product-merchant_full01.jpg",
"sequence": 0
},
…….. product image 1
…….. product image n
]
},
……. new product 2
……. new product 3
……. new product n
]
}
Body attribute name Description
merchantCode Specified merchant code value
products Input of bulk create new product request
categoryCode Category code value for new product
productName Product name value
url Other product promotion url, this attribute is nullable
merchantSku Merchant SKU for new product, this attribute is nullable
tipePenanganan Shipping type for specified product:
• 1 = regular product, shipped by Blibli
• 2 = big product, shipped by merchant partner
• 3 = BOPIS, (Buy Online, Pickup In Store) product
price Product price value
salePrice Product sale price value, the value of salePrice must be <= than price
stock Product stock value
minimumStock Input of current minimum stock, set to 1 if minimum stock is not defined by business agreement
pickupPointCode Pickup point code for the current new product

length, size, height Size of new product in centimeters
Weight of new prodcut in grams
weight
Note. minimal product weight is 10 grams
desc Product description value
uniqueSellingPoint Unique selling point for the new product
productStory Product story value
upcCode Universal Product Code (UPC) code of new product
The displayable status for new product, if it true once the product is approved by Quality Control
display
division then the product will displayed in Blibli apps.
buyable The buyable status for new product, if it true then product is able to bought by customer
installation The installation required status for new product
The list of feature attributes for new product. This value is got from 5.3 Get Attribute List, fill the
feature attribute from DESCRIPTIVE_ATTRIBUTE and PREDEFINED_ATTRIBUTE.
features
Note: Brand is mandatory input for “features” attribute, Brand value is got from 5.5 Get
Product Brands
The list of variant attributes for new product, this value will define the generated product item.
This value is got from 5.3 Get Attribute List, fill the variasi attribute from DEFINING_ATTRIBUTE.
For example: if the product variant is color = black and red, size = 35 and 36. So the generated
variasi product item will be 4 items:
1. Color red, size 35
2. Color black, size 35
3. Color red, size 36
4. Color black, size 36
Fill product image location with pattern:
[product-brand]_[lowercase-product-name]_full[images-sequence-start-with-1].jpg
Example of image location path: samsung_product-merchant_full01.jpg

locationPath
Note:
• space character of [lowercase-product-name], must be replaced strip character (-)
• symbol character must be replaced with strip character (-)
• using _full01.jpg as image path suffix
sequence The image sequence for current product, start with 0.
Parameter request: Not necessary
Success response
{
"requestId": "7ab7911e-d679-45c7-b405-76bf3ad1c30c",
"errorCode": null,
"success": true,
"value": {
"timeStamp": 1459479692789
}
}
requestId This is the request ID for current bulk request, the request ID is generated by Blibli
system. Merchant partner is able to check the bulk status by passing this request ID
into “get queue feed API”
timeStamp The current bulk request created date, in epoch time format

POST\nbf74d5182b38d45238a23db8988571e0\napplication/json POST\nbf74d5182b38d45238a23db8988571e0\napplication/json
\nMon May 16 14:07:15 WIB \nMon May 16 14:07:15 WIB 2016\n/mtaapi-
2016\n/mtaapi/api/businesspartner/v1/product/createProduct sandbox/api/businesspartner/v1/product/createProduct

6.4 [POST] Update Product Summary
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/updateProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/updateProduct
Purpose : to update product summary (sotck, price, buyable, and displayable status), this is a bulk request. Merchant
partner is able to update 100 product in 1 request. The request will be queued, then merchant partner is able to check the queue
status with “get queue feed API”.
Note.
If merchant only want to change product stock without changing another value like (price, buyable & displayable), then merchant can
set “null” value for unchanged attirbutes.
Header request:
Body request:
{
"merchantCode": "TOX-0952",
"productRequests": [
{
"gdnSku": "TOX-15338-00039-00001",
"stock": 20,
"minimumStock": 1,
"price": 20000,
"salePrice": 15000,
"buyable": true,
"displayable": false
},
{
"gdnSku": "TOX-15346-00039-00001",
"stock": -5,
"minimumStock": 1,
"price": null,
"salePrice": null,
"buyable": null,
"displayable": null
},
……… update product summary 3
……… update product summary n
]
}
Note: if you wanna only update some product attribute you can set another field with null value
merchantCode Input input current business partner/merchant code
productRequests Input of bulk update product request
gdnSku Input of product GDN Item SKU that wanna be updated
stock Input of delta stock for current product’s GDN SKU.
Note: if current product stock is 10 and merchant partner wanna updated to 5, then the delta
stock value must be -5.
If current product stock is 10 and wanna updated to 12, then the delta stock value must be 2.

Input of minimum stock for current product’s GDN SKU, set to 1 if it not defined by business
minimumStock
agreement
price Input of new product price
salePrice Input of new product sale price
Input of displayable status for new product, if it true then the product will displayed in Blibli
display
apps.
Input of buyable status for new product, if it true then product is able to bought by customer
buyable
Note. this flag will also changes displayable status. If buyable changed to ‘true’ then displayable
will become ‘true’ also and apply vice versa.
Success response
{
"errorCode": null,
"success": true,
"value": {
"timeStamp": 1459479692789
}
}

2016\n/mtaapi/api/businesspartner/v1/product/updateProduct sandbox/api/businesspartner/v1/product/updateProduct

6.5 [POST] Update Detail Product
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/updateDetailProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/updateDetailProduct
Purpose : to update product detail, this is a bulk request. Merchant partner is able to update 100 product in 1 request. The
request will be queued, then merchant partner is able to check the queue status with “get queue feed API”.
Note.
1. If merchant hit this API, the current merchant’s product web data will unsynced automatically from master data.
2. To fill the body request for this API, it can got from 5.2 Get Product Detail API. Merchant must remove the value of
https://blibli.com/images/catalog/full// for images -> locationPath.
Example.
“https://blibli.com/images/catalog/full///535/samsung_merchant-product_full01.jpg” must converted into
“/535/samsung_merchant-product_full01.jpg”

Header request:
Body request:
{
"merchantCode" : "TOS-16005",
"productDetailRequests" : [
{
"productSku": "TOS-16005-00009",
"businessPartnerCode": "TOS-16005",
"synchronize": false,
"productName": "Merchant Product",
"productType": 1,
"categoryName": "Android",
"categoryHierarchy": "Handphone & Tablet > Handphone > Android",
"brand": "Samsung",
"description": "Product description ",
"specificationDetail": "<ul><li>Outlet<ul><li>Jakarta Pusat - Plaza Indonesia</li></ul></ul>",
"uniqueSellingPoint": "product unique selling point",
"productStory": "This product is release at 26 Des 2016",
"items": [
{
"itemSku": "TOS-16005-00009-00001",
"skuCode": "MTA-0306263-00001",
"merchantSku": "MY-SKU-001",
"upcCode": "1231230010123",
"itemName": "Merchant Product Jakarta Pusat - Plaza Indonesia Black",
"length": 1,
"width": 2,
"height": 1,
"weight": 0.01,
"shippingWeight": 0.02,

"dangerousGoodsLevel": 0,
"lateFulfillment": true,
"pickupPointName": "Haneda Store",
"deltaStock": 0,
"synchronizeStock": false,
"prices": [
{
"price": 10000,
"salePrice": 8000,
"discountAmount": null,
"discountStartDate": null,
"discountEndDate": null,
"promotionName": null
}
],
"viewConfigs": [
{
"display": true,
"buyable": true
}
],
"images": [
{
"mainImage": true,
"sequence": 0,
"locationPath": "/535/samsung_merchant-product_full01.jpg"
},
{
"mainImage": false,
"sequence": 1,
}
],
"off2OnActiveFlag": false
}
],
"attributes": [
{
"attributeCode": "BR-M036969",
"values": [
"Samsung"
],
"skuValue": false,
"attributeName": "Brand",
"itemSku": null
},
{
"attributeCode": "KA-0000001",
"values": [
"4 MP"
],
"skuValue": false,
"attributeName": "Kamera",

"itemSku": null
}
],
"images": [
{
"mainImage": true,
"sequence": 0,
},
{
"mainImage": false,
"sequence": 1,
}
],
"url": "https://www.youtube.com/merchant-video",
"installationRequired": false
}
……. update product detail 2
……. update product detail 3
……. update product detail n
]
}
merchantCode Merchant code value for specified merchant partner
productDetailRequests Bulk update product detail request
productSku Product GDN SKU, this SKU is generated by Blibli system
businessPartnerCode Business partner/merchant partner code
synchronize Synchronize status:
• If it true then the product data is synchronize with the master data. Merchant can’t edit
current product if the sync status is true.
• If it false then the product data is not synchronized with the master data. Merchant is able
to edit the value of the product data.
Note: if merchant switch the sync status become true, then the product data will be reloaded like as
master data.
productType
Category hierarchy for the current product, using “>” as separator. For example: Handphone &
categoryHierarchy
Tablet > Handphone > Android
Product items information, usually 1 master product has several product items. The product item
items
is contains different variant.
Product item SKU that generated by Blibli system.
itemSku
Note: product item SKU is not same like productSku, each product item has different product item SKU
skuCode Product item code information, it’s not same like productCode
merchantSku Product item merchant SKU, this SKU is generated by merchant partner

itemName Product item name information
height Product height information in centimeters
weight Product weight information in kilograms
shippingWeight Product shipping weight information in kilograms, this value is calculated by Blibli system
Dangerous goods level information, that is:
• Lv 0: non dangerous goods
dangerousGoodsLevel • Lv 1: dangerous goods that contains liquid, like: alcohol, aseton, etc
• Lv 2: dangerous goods that contains: explosive product, flammable product, poison &
infectious substances, radioactive product, corrosive product, and magnetized product.
Late fulfillment status:
lateFulfillment • If it true then the product is buyable even the merchant is in close store state
• If it false then the product is no buyable when merchant is in close store state
pickupPointCode Pikcup point code information for current product item
pickupPointName Pickup point name information for current product item
Input of delta stock for current product’s GDN SKU.
deltaStock Note: if current product stock is 10 and merchant partner wanna updated to 5, then the delta
stock value must be -5.
If current product stock is 10 and wanna updated to 12, then the delta stock value must be 2.
synchronizeStock • If it true then the product is able to bought based on Lv 1 stock, even the Lv 2 is larger.
• If it false then the product is able to bought based on Lv 2 stock, Lv 1 stock will abandoned.
prices The product prices information for the current product
channelId Channel ID for the current product
price Product price information
salePrice Product sale price information
discountAmount Product discount price information
discountStartDate Product discount start date
discountEndDate Product discount end date
promotionName Promotion name for specified product price
viewConfigs Viewable configuration for current product
Displayable status:
• If it true then the product will displayed on blibli apps
display
• If it false then the product will not displated on blibli apps and only displayed on merchant
apps
Buyable status:
buyable • If it true then the product is able to bought by customer
• If it false then the product is can’t to bought by customer
images Product images information
mainImage Main image flag, if true then it will displayed as main image on product list page
sequence The image sequence on product detail page, start from 0
locationPath Product image location path information
Offline to online flag for the current product. Please contact our trade & partnership PIC about
off2OnActiveFlag
this business flow.
attributes Product attributes information
Atrrbute type information, contains:
• DESCRIPTIVE_ATTRIBUTE: attribute that defined by merchant, like: operating system,
screen size, etc
attributeType
• PREDEFINED_ATTRIBUTE: attribute that defined by Blibli, like: product operating system
that able to sell in Blibli apps, etc
• PREDEFINING_ATTRIBUTE: attribute that indicate the product variant like: size, colour, etc
values Product attribute value information
skuValue • If it true then merchant must fill the attribute data

• If it false then attribute name will be derived from master data if merchant not filled the
attribute data
attributeName Attribute name information
Product installation status, that is:
installationRequired • If it true then the product is needs to installed when received by customer, like: sport
equipment, bike, etc
Success response
{
"errorCode": null,
"success": true,
"value": {
"timeStamp": 1459479692789
}
}

2016\n/mtaapi/api/businesspartner/v1/product/updateDetailProduct sandbox/api/businesspartner/v1/product/updateDetailProduct

6.6.1 [POST] Upload Product Image (deprecated, please use Upload Image Version 2)
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/product/postImage
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/product/postImage
Purpose : to upload product image, this is a bulk request. Merchant partner is able to upload 100 product images in 1
request. The request will be queued, then merchant partner is able to check the queue status with “get queue feed API”.
Note.
The image file that uploaded must be:
1. have minimum resolution 600x600 px
2. have minmum dpi = 72 dpi
3. maximum file size is 1 Mb
4. image format must be: JPG or PNG
5. use white color of product’s background
Header request:
x-blibli-mta-authorization BMA {mta-username}:{api- API signature is generate by client like explained in section
signature} 2.2
x-blibli-mta-date-milis {current-milli-second} Get this value from: http://currentmillis.com as a
reference
Body request: multipart/form-data
merchantCode {merchant-code} Specified merchant code value
productImages[0].brand {product-brand} Specified product brand value
productImages[0].productName {product-name} Specified product name value
productImages[0].images[0] {product-image} Specified product image in .jpg extension type
productImages[0].images[1] {product-image} Specified product image in .jpg extension type
productImages[0].images[n] {product-image} Specified product image in .jpg extension type
productImages[1].brand {product-brand} 2nd product image request
productImages[1].productName {product-name}
productImages[1].images[0] {product-image}
productImages[100].brand {product-brand} 100th product image request
productImages[100].productName {product-name}
Success response
{
"errorCode": null,
"success": true,
"value": {
"timeStamp": 1459479692789
}
}

Note: Post image API implement different signature pattern for POST request, look at below:
POST\n\n\nMon May 16 14:07:15 WIB POST\n\n\nMon May 16 14:07:15 WIB 2016\n/mtaapi-
2016\n/mtaapi/api/businesspartner/v1/product/postImage sandbox/api/businesspartner/v1/product/postImage

6.6.2 [POST] Upload Product Image Version 2
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v2/product/postImage
URL Sandbox :-
Purpose : to upload product image, this is a bulk request. Merchant partner is able to upload 100 product images in 1
request. The request will be queued, then merchant partner is able to check the queue status with “get queue feed API”.
With this API you can upload the product image specific per product’s item code (optional). You can upload images per product code
also (mandatory).
Note.
The image file that uploaded must be:
1. have minimum resolution 600x600 px
2. have minmum dpi = 72 dpi
3. maximum file size is 1 Mb
4. image format must be: JPG or PNG
5. use white color for image’s background
5. have image ratio 1:1
Header request:
x-blibli-mta-authorization BMA {mta-username}:{api- API signature is generate by client like explained in section
signature} 2.2
x-blibli-mta-date-milis {current-milli-second} Get this value from: http://currentmillis.com as a
reference
Body request: multipart/form-data
merchantCode {merchant-code} Specified merchant code value
productCode {product-code} Specified product code value
productImages[0] {product-image} Image 1 for product
productImages[1] {product-image} Image 2 for product
productImages[n] {product-image} Image n for product
productItem[0].productItemCode {product-item-code } Specified product item code value
productItem[0].images[0] {product-item-image} Image 1 product product item
productItem[0].images[1] {product-item-image} Image 2 product product item
productItem[0].images[n] {product-item-image} Image n product product item
….
productItem[n].productItemCode {product-item-code } Specified product product item
productItem[n].images[0] {product-item-image} Image n product product item n
Success response
{
"errorCode": null,
"success": true,
"value": {
"timeStamp": 1459479692789
}
}

Note: Post image API implement different signature pattern for POST request, look at below:
POST\n\n\nMon May 16 14:07:15 WIB POST\n\n\nMon May 16 14:07:15 WIB 2016\n/mtaapi-
2016\n/mtaapi/api/businesspartner/v2/product/postImage sandbox/api/businesspartner/v2/product/postImage

7. Order Component API
7.1 [GET] Get Order List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/orderList
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/orderList
Purpose : get order list from specified merchant by based on filter parameter
Note.
This API will return per order item list information
Header request:
Parameter request:
storeId 10001 Default store ID for Blibli
productTypeCode {product-type} Filter order list by product type:
• 1: REGULAR
• 2: BIG PRODUCT
• 3: BOPIS
status {order-status} Filter order list by order status, that is:
• FP : new order for merchant
• PF : partial fulfilled order
• CR : customer request
• CX : in delivery
• PU : ready for pickup
• OS : out of stock
• BP : big product order
• NCX : cash on delivery (COD)
• NDF : COD failure
• DF : delivery failure
• DC : delivery canceled
• D : delivered
• X : canceled
• ES : email sent
page {page-list} Filter order list by page list index, the default value is 0
size {list-size} Filter order list by size list, the default value is 10
logisticCode {logisticProviderCode} Filter order list by logisticProviderCode
orderDate {order-date} Filter order list by orderDate, using format YYYY-MM-DD
Success response
{
"errorCode": null,

"success": true,
"content": [
{
"orderNo": "25000028314",
"orderItemNo": "25000029207",
"qty": 1,
"orderDate": 1480401269630,
"orderStatus": "BP",
"orderStatusString": "MENUNGGU DATANG",
"productName": "LG G5 SE Smartphone - Titan [32 GB], Sync Stock True Product Black",
"productPrice": 5000000,
"logisticService": "JNE Regular",
"logisticProviderCode": "JNE",
"dueDate": 1488301200000,
"merchantDeliveryType": "DROPSHIP",
"logisticsOptionName": "Express",
"logisticsProductName": "JNE Regular",
"merchantSku" : "MM-0412",
"itemSku": "TOQ-15126-00100-00001",
"awbNumber": "JNE6337668311",
"awbStatus": "VALID",
"paid": false,
"productTypeCode": "1",
"productTypeName": "Regular"
},
{
"orderNo": "25000028297",
"orderItemNo": "25000029190",
"qty": 1,
"orderDate": 1480400850566,
"logisticService": "JNE Regular",
"logisticProviderCode": "JNE",
"dueDate": 1488301200000,
"merchantDeliveryType": "PICKUP"
"logisticsOptionName": "Standard",
"merchantSku" : "MM-0412",
"itemSku": "TOQ-15126-00100-00001",
"awbStatus": "INVALID",
"paid": false,
" productTypeCode ": "1",
"productTypeName": "Regular"
}
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 200
}
}

orderNo Order number information
orderItemNo Order item number information
qty Order item quantity information
orderDate Order created date, in epoch time format
orderStatus Order status code information
orderStatusString Order status description
productPrice Product sale price information
logisticService Logistic option code is the type of specified logistic product name. For example is
logistic option code Standard. Express, etc
logisticProviderCode Logistic service code information for current order.
If the value:
• “Big Product”: merchant must hit 8.2 Fulfill Big Product Order API
• “BOPIS”: merchant must hit 8.3 Fulfill BOPIS Order API
• Except “Big Product” and “BOPIS” merchant must hit 8.1 Fulfill Regular
Order API
dueDate Due date to fulfill current order, in epoch time format
merchantDeliveryType Merchant delivery type for current order:
• PICKUP: regular product and Blibli courrier will pickup the order to
merchant’s pickup point. Merchant hit 8.1 Fulfill Regular Order API
without awbNo attribute.
• DROPSHIP: regular product and merchant sends the order by himself.
Merchant hit 8.1 Fulfill Regular Order API with awbNo attribute
logisticsOptionName Logistic option code is the type of specified logistic product name. For example is
logistic option code STANDARD. EXPRESS, etc
logisticsProductName Logistic service name information for current order item
pickupPointCode Pickup point code information current order item
itemSku GDN item SKU information for current order item
awbNumber Airwaybill number information for current order shipment
awbStatus Airwaybill status for current order shipment, the status are:
• FAILED : airway bill validation is failed
• INVALID : airway bill is not valid
• VALID : airway bill is valid
• NOT_VALIDATED_YET : airway bill is not validated yet
paid Boolean value to identify whether current order already paid to merchant or not.
This field is used for financial purpose.
productTypeCode The product type code based on shipping method, that is:
• 1 : regular product
• 2 : shipped by merchant
• 3 : bopis product, like: ticket, voucher, etc
productTypeName The product type name based on shipping method, that is:
pageMetaData Page metadata information for order list result
pageSize Page size for current order item list
pageNumber Page number information for current order item list
totalRecords Total record of order list that able to get by current filter

2016\n/mtaapi/api/businesspartner/v1/order/orderList sandbox/api/businesspartner/v1/order/orderList

7.2 [GET] Get Order Detail
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/orderDetail
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/orderDetail
Purpose : get order detail by order item number
Header request:
Parameter request:
orderNo {order-number} Order number information
orderItemNo {order-item-number} Order item number information
Success response
{
"errorCode": null,
"success": true,
"value": {
"orderNo": "25000039861",
"orderItemNo": "25000029207",
"qty": 1,
"orderDate": 1505442541562,
"autoCancelDate": 1505840400000,
"productItemName": "batik indonesia raya L Black/Violet",
"total": 5000000,
"itemWeightInKg": 0.17,
"custName": "Andri Kusnanto",
"customerAddress": "Jalan Aipda K.S. Tubun II C No. 8, Daerah Khusus Ibukota Jakarta, Indonesia Cadasari",
"customerEmail": "masitha@mailinator.com",
"logisticsService": "JNE Regular",
"currentLogisticService": "JNE Regular",
"pickupPoint": "PP-3000408",
"pickupPointName": "My Warehouse 1",
"pickupPointAddress": "Haneda 87 District 6 Tokyo",
"pickupPointCity": "Kota Jakarta Selatan",
"pickupPointProvince": "DKI Jakarta",
"pickupPointCountry": "ID",
"pickupPointZipcode": "12440",
"gdnSku": "TOS-16005-00001",
"gdnItemSku": "TOS-16005-00001-00001",

"merchantSku": null,
"totalWeight": 1.34,
"merchantDeliveryType": "DROPSHIP",
"installationRequired": false,
"awbStatus": "VALID",
"shippingStreetAddress": "Jalan KH Mas Mansyur, Daerah Khusus Ibukota Jakarta, Indonesia",
"shippingCity": "Kota Jakarta Barat",
"shippingSubDistrict": "Kebon Kacang",
"shippingDistrict": "Tanah Abang",
"shippingProvince": "DKI Jakarta",
"shippingZipCode": "10240",
"shippingCost": 22220,
"shippingMobile" : "0854569871234",
"shippingInsuredAmount": 0,
"startOperationalTime": null,
"endOperationalTime": null,
"issuer": null,
"refundResolution": null,
"unFullFillReason": null,
"unFullFillQuantity": null,
"productTypeName": "Regular",
"custNote": "-",
"shippingRecipientName": "Masitha .",
"logisticsProductCode": "JNE",
"logisticsOptionCode": "STANDARD",
"logisticsOptionName": "Standard",
"originLongitude": null,
"originLatitude": null,
"destinationLongitude": 113.921327,
"destinationLatitude": -0.789275,
"fulfillmentInfo": { //just for big product order
"deliveryDateStart" : 1479166599946,
"deliveryDateEnd" : 1479166599946,
"installationDateStart" : 1479166599946,
"installationDateEnd" : 1479166599946,
"installationNote" : "Please handle with care",
"installationOfficerName" : "Merchant installation PIC name",
"installationOfficerPhone" : "085456789321",
"courierName" : "Merchant courrier anme",
"courierType" : "Merchant courrier",
"settlementCode" : "a23s1df6a5s4df55",
},
"settlementInfo": { //for big product and bopis order
"settlementCode" : "a23s1df6a5s4df55"
},
"financeSettlementInfo": {
"paymentDate" : 1479166599946,
"transactionFee" : 100000,
"commission" : 500000,
"pph23" : 5000,
"merchantPromo" : 50000,
"totalPayment" : 5000000,
"reportPath" : "https://blibli.com/merchant-document/54542135"
},
"manifest": [ //if shipped by Gojek

"logisticProviderCode" : "GOJEK",
"airwaybill" : "7564489787894615",
"status" : "On Delivery",
"timestamp" : 1479166599946,
"picName" : "Gojek driver name",
"picImageUrl" : "https://image-service.com/profile/756168712",
"picContactInformation" : "085456789321"
}
],
"orderHistory": [
{
"id": "33d8abd6-f26c-4d36-abea-72205227b4d9",
"storeId": "10001",
"createdDate": 1480401901011,
"updatedDate": 1480401901011,
"orderStatusDesc": "Pengiriman Oleh Merchant / Pengambilan Barang di Merchant"
},
{
"id": "7eaa0776-0120-41e5-a1d0-159f608442d5",
"storeId": "10001",
"createdDate": 1480401574496,
"updatedDate": 1480401574496,
"orderStatus": "FP",
"orderStatusDesc": "Pesanan sedang diproses"
}
}
qty Order item quantity information
orderDate Order creation date for merchant
autoCancelDate Order autocancel date in epoch format. If current order is not fulfilled after
autoCancelDate then specified order will canceled automatically
productItemName Product item name information for current order
productPrice Product sale price information
total Order total amount (order quantity * product sale price)
orderStatus Order status code information
orderStatusString Order status description
customerAddress Customer address information
Note. It’s not shipping address for current order.

customerEmail Customer email address information
logisticsService Order logistic service information.
currentLogisticService Logistic service code information for current order for regular order. Merchant
must hit 8.1 Fulfill Regular Order API to fulfill regular order.
If the order product type is BOPIS and Big Product, the value is:
• Big Product: merchant must hit 8.2 Fulfill Big Product Order API
• BOPIS: merchant must hit 8.3 Fulfill BOPIS Order API
pickupPoint Order pickup point code information
pickupPointName Pickup point name information

pickupPointCity Pickup point city information
pickupPointProvince Pickup point province information
pickupPointCountry Pickup point country information
pickupPointZipcode Pickup point zip code information
pickupPointAddress Order pickup point address information
gdnSku Product item SKU information
totalWeight Total weight for current order
merchantDeliveryType Merchant delivery type for current order:
• PICKUP: regular product and Blibli courrier will pickup the order to
merchant’s pickup point. Merchant hit 8.1 Fulfill Regular Order API
without awbNo attribute.
• DROPSHIP: regular product and merchant sends the order by himself.
Merchant hit 8.1 Fulfill Regular Order API with awbNo attribute
installationRequired To indicate that current order item is need to be installed or not. The goods that
need to be installed are: sport equipment, AC, etc
awbNumber Airwaybill number information for current order shipment
awbStatus Airwaybill status for current order shipment, the status are:
shippingStreetAddress The shipping street address information for current order.
Note. It’s the shipping address for current order

shippingCity The shipping city information for current order
shippingSubDistrict The shipping sub-district information for current order (kelurahan in Indonesia)
shippingDistrict The shipping district information for current order (kecamatan in Indonesia)
shippingProvince The shipping province information for current order
shippingZipCode The shipping zip code information for current order
shippingCost The shipping cost information for current order
shippingMobile The shipping recipient’s mobile number
shippingInsuredAmount The shipping insured amount for current package
startOperationalTime Start operational time for order shipment, it’s for package shipment by GOJEK,
etc
endOperationalTime End operational time for order shipment, it’s for package shipment by GOJEK, etc
issuer Issuer information that doing partial fulfill or OOS, the value will be:
• CUSTOMER : unfulfilled order is done by customer request
• FULFILLMENT : unfullfiled order is done by Blibli/Merchant
refundResolution Refund resolution information when merchant doing partial fulfill or OOS, the
value will be:
• REFUND_CASH : unfulfilled order will resolved by cash refund
• REFUND_VOUCHER : unfulfilled order will resolved by voucher refund
• RECREATE : unfulfilled order will resolved by recreating new order that
can be fulfilled
unFullFillReason The reason that caused unfulfilled order
unFullFillQuantity The unfulfilled order quantity
productTypeCode The product type based on shipping method, that is:
productTypeName Product name information
custNote Customer note information for specified order
shippingRecipientName Recipient name for current order shippment
destinationLongitude Order shippment destination longitude
destinationLatitude Order shippment destination latitude
logisticsProductCode Logistic service code information for current order.

If the value:
• “Big Product”: merchant must hit 8.2 Fulfill Big Product Order API
• “BOPIS”: merchant must hit 8.3 Fulfill BOPIS Order API
• Except “Big Product” and “BOPIS” merchant must hit 8.1 Fulfill Regular
Order API
logisticsProductName Logistic option code is the type of specified logistic product name. For example is
logistic option code Standard. Express, etc
logisticsOptionCode Logistic option code is the type of specified logistic product name. For example is
logisticsOptionName Logistic option name is the text description of logisticOptionCode value
orderHistory Order history list information
orderStatus Order status code
orderStatusDesc Order history status description
originLongitude Origin/warehouse longitude information, a place information that package will be
picked up
originLatitude Origin/warehouse latitude information, a place information that package will be
picked up
destinationLongitude Destination longitude information, a place information that package will be sent
destinationLatitude Destination latitude information, a place information that package will be sent
fulfillmentInfo Contain fulfillment information, it’s show the value that inputed by merchant
when doing fulfill Big Product order
deliveryDateStart Delivery start date for merchant shipment
deliveryDateEnd Delivery estimation end date for merchant shipment
installationDateStart Installation start date from merchant side
installationDateEnd Installation end date from merchant side
installationNote Installation note from merchant side
installationOfficerName Installation officer name, that PIC is assigned by merchant side
installationOfficerPhone Installation phone number, it’s assigned by merchant side
courierName Courrier name information, it’s assigned by merchant side. If merchant using
other third party logistic, merchant can assign with the default value, ex:
Merchant Courier JNE.
If merchant their own logistic, he can assign with the their identified courrier
name.
courierType Merchant courier type value must be:
• Merchant courier : if the product is delivered by merchant logistic
• 3PL : if the merchant using other third party logistic like: JNE, NCS, etc
settlementCode Settlement code information for current order
financeSettlementInfo It contain order settlement information, from Blibli to merchant
paymentDate Payment date when Blibli paid the merchant regarding the current order
transactionFee Transaction fee information
commission Commision information
pph23 PPH23 / tax information
merchantPromo Merchant promo amount information
totalPayment Total payment information
reportPath Link to download settlement report file
manifest Contains information about package shipment
logisticProviderCode Logistic provider information
airwaybill Airway bill status
status Delivery status, it’s vary depends on each logistic provider
timestamp Delivery date
picName PIC/courier name that deliver the package
picImageUrl PIC/courier photo profile that deliver the package
picContactInformation PIC/courier contact or phone information that deliver the package
createdDate Order created date, in epoch time format

createdBy Order creator information
updatedDate Order updated date, in epoch time format
updatedBy Order last update PIC information

2016\n/mtaapi/api/businesspartner/v1/order/orderDetail sandbox/api/businesspartner/v1/order/orderDetail

7.3 [GET] Download Shipping Label
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/downloadShippingLabel
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/downloadShippingLabel
Purpose : to download shipping label for current order
Note. Shipping label is available for :

Regular Pickup = shipping label will be available in PU (after merchant fulfill the order)
Regular Dropship = shipping label will be available in FP (new order for merchant) or PU (after merchant fulfill order)
Big Product & BOPIS = shipping label will be available in FP (new order for merchant) or BP (after merchant fulfill order)
Header request:
Parameter request:
orderItemId {order-item-id} Order item number for current order
Success response
{
"errorCode": null,
"success": true,
"value": {
"document": "JVBERi0xLjQNCjUgMCBvYmoNCjw8L1R5cGUgL1BhZ2UgL1BhcmVudCAzIDAgUiAvQ29udGVudHMgNiAwIFIgL01
lZGlhQm94IFswIDAgNTk1LjQ0IDg0MS42OF0gL0dyb3VwIDw8IC9DUyAvRGV2aWNlUkdCIC9TIC9UcmFuc3BhcmVuY3kgL1R5cGU
gL0dyb3VwID4+IC9SZXNvdXJjZXM8PC9Gb250PDwvRkFBQUJDIDEyIDAgUiAvRkFBQUFIIDcgMCBSIC9GQUFBQkggMTcgMCBSID4
+L0V4dEdTdGF0ZTw8L0dTMSAyMiAwIFIgL0dTMiAyNCAwIFIgL0dTMyAyNiAwIFIgPj4vWE9iamVjdDw8L1gxIrJDdc51MG4rMnsqu
v4mKtCwmtk2/9fV/15SqIddxU83oHtXmfhFhciV3PYlrOg0uBc7n"
}
}
success To indicate whether the download operation is success or not
document The shipping label .pdf document in base64 format

2016\n/mtaapi/api/businesspartner/v1/order/downloadShippingLabel sandbox/api/businesspartner/v1/order/downloadShippingLabel

7.4 [GET] Get Airway Bill Information
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/getAirwayBill
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/getAirwayBill
Purpose : to get airway bill information for current order
Note. Airwaybill document only available only for Regular Pickup Order and order status is PU (after fulfill order) or CX (in delivery)
Header request:
Parameter request:
orderItemNo {order-item-id} Order item number for current order
Success response
{
"errorCode": null,
"success": true,
"value": {
"productName": "Samsung Galaxy S7 SM G930 Smartphone - Hitam [32 GB] Jakarta Pusat - Plaza Indonesia Silver",
"quantity": 1,
"packageId": "10003067",
"airwaybillNo": "JNE0313562874",
"airwaybillStatus": "VALID",
"orderStatus": "Pesanan Telah Terkirim",
"logisticProvideName": "JNE YES",
"logisticProvideCode": "EXPRESS",
"logisticOptionName": "Standard",
"logisticOptionCode": "STANDARD",
"logisticEstimationDay": 2,
"originCodeId": "Origin-Jakarta",
"originCode": "CGK",
"destinationCode": "CGK10105",
"senderName": "Blibli.com - Toko QA CM 2",
"senderAddress": "Jalan Aipda K.S. Tubun II C No. 8, Daerah Khusus Ibukota Jakarta, Indonesia Cadasari - Kaduela Kab. Pandeglang",
"senderCity": "Jakarta",
"recipientSubDistrict": "Palmerah",
"recipientDistrict": "Palmerah",
"senderProvince": "Jakarta Barat",
"recipientCountry": "Indonesia",
"recipientEmail": "agiesatu@mailinator.com",
"recipientRegion": "Palmerah - Palmerah, Kota Jakarta Barat, DKI Jakarta",

"senderZipCode": "11410",
"senderPhone": "0804 1 871 871",
"recipientName": "Customer ABC",
"recipientAddress": "Blibli.com KS tubun 2C NO 8",
"recipientRegion": "Slipi - Palmerah, Kota Jakarta Barat, DKI Jakarta",
"recipientZipCode": "11410",
"pickupTime": 1480140958196,
"actualPickupTime": 1480140849363
}
}
quantity Product quantity information
packageId Package ID information
airwaybillNo Airway bill number information
airwaybillStatus Airwaybill status for current order shipment, the status are:
orderStatus Order status information
logisticProvideName Logistic provider name information
logisticProvideCode Logistic provider code information
logisticOptionCode Logistic option code is the type of specified logistic product name. For example is
logisticOptionName Logistic option name is the text description of logisticOptionCode value
logisticEstimationDay Logistic estimation day for package shipment
originCodeId Origin ID information
originCode Origin code information
destinationCode Destination code information
senderName Sender name information
senderAddress Sender address information
senderCity Sender city information
senderProvince Sender province information
senderZipCode Sender ZIP code information
senderPhone Sender phone information
recipientName Recipient name information
recipientAddress Recipient address information
recipientSubDistrict Recipient sub district information (keluarahan in Indonesia)
recipientDistrict Recipient district information (kecamatan in Indonesia)
recipientCountry Recipient country information
recipientEmail Recipient email information
recipientRegion Recipient region information, the pattern will be: sub-district – district, city country
recipientZipCode Recipient ZIP code information
pickupTime Pickup time information for current package
actualPickupTime Actial pickup time information for current package

2016\n/mtaapi/api/businesspartner/v1/order/getAirwayBill sandbox/api/businesspartner/v1/order/getAirwayBill

7.5 [GET] Get Combine Shipping List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/getCombineShipping
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/getCombineShipping
Purpose : to get combine shipping list for current order, so merchant able to do combine shipping for regular order and
built body for “8.1 Fulfill Regular Order API”
This API only return eligible combine shipping list for REGULAR PICKUP order.
Header request:
Parameter request:
orderItemNo {order-item-id} Order item number for current order
Success response
{
"errorCode": null,
"success": true,
"value": {
"alreadyCombined": false,
"maxCombinedWeight": 50,
"combineShipping": [
{
"orderNo": "25000013289",
"orderItemNo": "25000013316",
"qty": 1,
"gdnItemSku": "TOB-16791-00028-00001",
"productName": "Product Name 412",
"total": 400000,
"productWeight": 1,
"totalWeight": 1
},
{
"orderNo": "25000013278",
"orderItemNo": "25000013305",
"qty": 1,
"gdnItemSku": "TOB-16791-00045-00001",

"productName": "Product Name 4578",
"total": 400000,
"productWeight": 1,
"totalWeight": 1
}
]
}
}
alreadyCombined A flag that indicate whether current order is already combined or not. If the value is
true then the current order order is can’t to be combined twice
maxCombinedWeight Maximum weight of specified order for combine shipping, in kilograms
combineShipping List of eligible combine shipping for current order
qty Product’s quantity information for current eligible combine order
gdnItemSku Product item SKU information, it’s generated by Blibli
merchantSku Merchant SKU information, it’s generated by Merchant side
productPrice Product item price information for 1 item
total Total amount information for current eligible combine order
productTypeCode The product type based on shipping method, that is:
productTypeName Product name information
productWeight Shipping weight information for 1 item, in Kilogram
totalWeight Total shipping weight information for current eligible combine order in Kilogram

2016\n/mtaapi/api/businesspartner/v1/order/getCombineShipping sandbox/api/businesspartner/v1/order/getCombineShipping

7.6 [GET] Get Returned Order List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/getReturnedOrderSummary
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/getReturnedOrderSummary
Purpose : to get returned order list

Header request:
Parameter request:
page {page-list} Filter returned order list by page list index, the default value is 0
size {list-size} Filter returned order list by size list, the default value is 10
rmaNumber {returnNo} Filter returned order list by return number
orderIdOrItemId {orderIdOrOrderItemId} Filter returned order list by order number or order item number
returDate {createdDate} Filter returned order list by return created date
rmaResolution {returnResolution} Filter returned order list by return resolution
status {returnStatus} Filter returned order list by return status
Success response
{
"errorCode": null,
"success": true,
"content": [
{
"createdDate": 1505898403772,
"returnId": "56fa05c75c86205e8d6f16fb",
"returnNo": "RMA1041",
"orderNo": "25000013005",
"orderItemNo": "25000013013",
"customerName": "fefe qa",
"gdnSku": "TOQ-15130-00001-00001",
"productName": "Toko QA CM 2 Reguler 1",
"orderQuantity": 1,
"productSalePrice": 100000,
"orderLogistic": null,
"returnStatusCode": "RMA_REQUEST_APPROVAL",
"returnStatus": "Menunggu persetujuan permohonan retur",
"returnResolution": null,
"reason": "PRODUK_TIDAK_BERFUNGSI_DENGAN_BAIK"
},
{
"createdDate": 1505898403772,
"returnId": "56fa349ce4b01f68b053128d",

"orderNo": "25000013005",
"orderItemNo": "25000013013",
"gdnSku": "TOQ-15130-00001-00001",
"productName": "Toko QA CM 2 Reguler 1",
"orderQuantity": 1,
"orderLogistic": null,
"returnStatusCode": "RMA_PROCESS_STARTED",
"returnStatus": "Sedang dalam proses retur",
"returnResolution": "-",
"reason": "PRODUK_TIDAK_BERFUNGSI_DENGAN_BAIK"
}
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 14
}
}
createdDate Creation date for returned order
returnId Unique data identifier for returned order
returnNo Returned order number information
customerName Customer name information
gdnSku Product item SKU information for current returned order
orderQuantity Product’s quantity information for current returned order
productSalePrice Product’s sale price information for current returned order
orderLogistic Order logistic information for current returned order
returnStatusCode Return status code information for current returned order:
• RMA_REQUEST_APPROVAL: Menunggu persetujuan permohonan retur
• RMA_REQUEST_APPROVED: Permohonan retur disetujui
• RMA_REQUEST_CANCELLED: Permohonan retur ditolak
• RMA_PROCESS_STARTED: Sedang dalam proses retur
• RMA_PROCESS_FINISHED: Proses retur selesai
• RMA_PROCESS_CANCELLED: Proses retur ditolak
returnStatus Return status code information for current returned order:
returnResolution Return resolution information:
• NONE: no return resolution
• CASH_REFUND: Cash Refund
• VOUCHER_REFUND: Voucher Refund
• PRODUCT_REPLACEMENT: Product Replacement
• MANUAL: Other Manual Process
reason The reason information that cause returned order

2016\n/mtaapi/api/businesspartner/v1/order/getReturnedOrderSummary sandbox/api/businesspartner/v1/order/getReturnedOrderSummary

7.7 [GET] Get Returned Order Detail
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/getReturnedOrderDetail
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/getReturnedOrderDetail
Purpose : to get returned order detail
Header request:
Parameter request:
rmaId {rma-id} Unique data identifier for returned order, got from “Returned Order List API”
orderNo {order-no} Input of order number
orderItemNo {order-item-no} Input of order item number information
Success response
{
"errorCode": null,
"success": true,
"value": {
"id": "56e27afbe4b01cfcdf46a1af",
"storeId": "10001",
"createdDate": 1457683195698,
"createdBy": "user-dev-rma",
"updatedDate": 1457683195698,
"updatedBy": null,
"returnId": "56e27afbe4b01cfcdf46a1af",
"orderNo": "25000013005",
"orderItemNo": "25000013013",
"gdnSku": "TOQ-15130-00001-00001",
"productName": "Toko QA CM 2 Reguler 1 ",
"orderQuantity": 1,
"returnStatusCode": "RMA_REQUEST_APPROVAL",
"returnStatus": "Menunggu persetujuan permohonan retur",
"productType": "Regular",
"deliveredDate": null,
"returnReason": "PRODUK_TIDAK_BERFUNGSI_DENGAN_BAIK",
"customerAddress": "Jalan Aipda KS tubun 2C Slipi Jakarta Barat",
"customerVillages": "",
"customerDistricts": "",
"customerCity": "Kota Jakarta Barat",

"customerState": "DKI Jakarta",
"customerPostalCode": "11750",
"qcFileReady": false,
"businessPartnerCode": "TOQ-15130",
"productMerchantSku": "TOQ-15130-00001-00001",
"productShippingWeight": 10,
"responsibility": null
}
}
id Unique data indentifier for current retuned order
storeId Store id information
createdDate Creation date for current returned order
createdBy Creator for current returned order
updatedDate Last updated date for current returned order
updatedBy Last update initiator for current returned order
returnId Unique data identifier for returned order
returnNo Returned order number information
customerName Customer name information
gdnSku Product item SKU information for current returned order
orderQuantity Product’s quantity information for current returned order
productSalePrice Product’s sale price information for current returned order
orderLogistic Order logistic information for current returned order
returnStatusCode Return status code information for current returned order:
returnStatus Return status code information for current returned order:
productType The product type based on shipping method, that is:
deliveredDate Delivired date information for current returned order
returnReason Return reason for current order
customerAddress Customer address information
customerVillages Customer village information
customerDistricts Customer district information (kecamatan in Indonesia)
customerCity Customer city information
customerState Customer state information
customerPostalCode Customer ZIP code information
qcFileReady Value that indicated whether QC file is ready or not
businessPartnerCode Merchant code information for current product
productMerchantSku Product item SKU for returned order
productShippingWeight Product shipping weight for returned order

responsibility Value of who bear the returned order cost, that is:
• Blibli: returned order cost is borne by Blibli
• Customer: returned order cost is borne by customer
• Logistic partner: returned order cost is borne by logistic partner
• Merchant: returned order cost is borne by merchant
• 50/50 Logistic & Blibli: returned order cost is borne 50% by logistic partner
and 50% by Blibli

2016\n/mtaapi/api/businesspartner/v1/order/getReturnedOrderDetail sandbox/api/businesspartner/v1/order/getReturnedOrderDetail

7.8 [GET] Download Airway Bill Document
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/downloadAirwayBill
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/downloadAirwayBill
Purpose : to download airwaybill document
Note. Airwaybill document only available only for Regular Pickup Order and order status is PU (after fulfill order) or CX (in delivery)
Header request:
Parameter request:
orderItemNo {order-item-no} Order item number value
Success response
{
"errorCode": null,
"success": true,
"value": {
"document": "JVBERi0xLjQNCjUgMCBvYmoNCjw8L1R5cGUgL1BhZ2UgL1BhcmVudCAzIDAgUiAvQ29udGVudHMgNiAwIFIgL01
lZGlhQm94IFswIDAgNTk1LjQ0IDg0MS42OF0gL0dyb3VwIDw8IC9DUyAvRGV2aWNlUkdCIC9TIC9UcmFuc3BhcmVuY3kgL1R5cGU
gL0dyb3VwID4+IC9SZXNvdXJjZXM8PC9Gb250PDwvRkFBQUJDIDEyIDAgUiAvRkFBQUFIIDcgMCBSIC9GQUFBQkggMTcgMCBSID4
+L0V4dEdTdGF0ZTw8L0dTMSAyMiAwIFIgL0dTMiAyNCAwIFIgL0dTMyAyNiAwIFIgPj4vWE9iamVjdDw8L1gxIrJDdc51MG4rMnsqu
v4mKtCwmtk2/9fV/15SqIddxU83oHtXmfhFhciV3PYlrOg0uBc7n"
}
}
success To indicate whether the download operation is success or not
document The airway bill .pdf document in base64 format

2016\n/mtaapi/api/businesspartner/v1/order/downloadAirwayBill sandbox/api/businesspartner/v1/order/downloadAirwayBill

8. Fulfill Order API
8.1 [POST] Fulfill Regular Order
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/fulfillRegular
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/fulfillRegular
Purpose : to fulfill regular order, merchant also be able to do combine shipping with other regular order with same shipping
destination

Header request:
Body request for Merchant Delivery Type = DROPSHIP:
{
"type":1,
"awbNo" : "874101522869",
"orderNo":"25000027806",
"orderItemNo":"25000028640",
"combineShipping":[
{
"orderNo":"25000027806",
"orderItemNo":"25000028640"
},
{
"orderNo":"25000027811",
}
]
}
Body request for Merchant Delivery Type = PICKUP:
{
"type":1,
"orderNo":"25000027806",
"orderItemNo":"25000028640",
"combineShipping":[
{
"orderNo":"25000027806",
},
{
"orderNo":"25000027811",
}
]
}
type Order shipping type:
• 1: REGULAR: for regular product
• 2: BIG PRODUCT: for big product, the logistic service is handled by merchant
• 3: BOPIS: for BOPIS product, the logistic service is handled by merchant

awbNo Value of airway number for current order
Note: this value is assigned only for merchantDeliveryType = DROPSHIP, if the shipping is
handled by Blibli courrier (merchantDeliveryType = PICKUP) then you don’t need to assign this
attribute
combineShipping List of orders that want to be shipping combined, you can get the combine shipping data from
“7.5 Get Combine Shipping API”
Note: this value must contain at least 1 element for current order number and order item
number
Parameter request:
Success response:for REGULAR PICKUP

{
"errorCode": null,
"success": true,
"value": {
"productName": "Samsung Galaxy S7 SM G930 Smartphone - Hitam [32 GB] Jakarta Pusat - Plaza Indonesia Silver",
"quantity": 1,
"packageId": "10003067",
"airwaybillNo": "JNE0313562874",
"airwaybillStatus": "VALID",
"orderStatus": "Pesanan Telah Terkirim",
"logisticProvideName": "JNE YES",
"logisticProvideCode": "EXPRESS",
"logisticOptionName": "Standard",
"logisticOptionCode": "STANDARD",
"logisticEstimationDay": 2,
"originCodeId": "Origin-Jakarta",
"originCode": "CGK",
"destinationCode": "CGK10105",
"senderName": "Blibli.com - Toko QA CM 2",
"senderAddress": "Jalan Aipda K.S. Tubun II C No. 8, Daerah Khusus Ibukota Jakarta, Indonesia Cadasari - Kaduela Kab. Pandeglang",
"senderCity": "Jakarta",
"recipientSubDistrict": "Palmerah",
"recipientDistrict": "Palmerah",
"senderProvince": "Jakarta Barat",
"recipientCountry": "Indonesia",
"recipientEmail": "agiesatu@mailinator.com",
"recipientRegion": "Palmerah - Palmerah, Kota Jakarta Barat, DKI Jakarta",
"senderZipCode": "11410",
"senderPhone": "0804 1 871 871",
"recipientName": "Customer ABC",
"recipientAddress": "Blibli.com KS tubun 2C NO 8",
"recipientRegion": "Slipi - Palmerah, Kota Jakarta Barat, DKI Jakarta",
"recipientZipCode": "11410",
"pickupTime": 1480140958196,
"actualPickupTime": 1480140849363
}

}
Success response:for REGULAR DROPSHIP
{
"errorCode": null,
"success": true,
"value": null
}
quantity Product quantity information
packageId Package ID for current order
airwaybillNo Airway bill number information
airwaybillStatus Airwaybill status for current order shipment, the status are:
orderStatus Order status information
logisticProvideName Logistic provider name information
logisticProvideCode Logistic provider code information
logisticOptionCode Logistic option code is the type of specified logistic product name. For example is
logisticOptionName Logistic option name is the text description of logisticOptionCode value
logisticEstimationDay Logistic estimation day for package shipment
originCodeId Origin ID information
originCode Origin code information
destinationCode Destination code information
senderName Sender name information
senderAddress Sender address information
senderCity Sender city information
senderProvince Sender province information
senderZipCode Sender ZIP code information
senderPhone Sender phone information
recipientName Recipient name information
recipientAddress Recipient address information
recipientSubDistrict Recipient sub district information (keluarahan in Indonesia)
recipientDistrict Recipient district information (kecamatan in Indonesia)
recipientCountry Recipient country information
recipientEmail Recipient email information
recipientRegion Recipient region information, the pattern will be: sub-district – district, city country
recipientZipCode Recipient ZIP code information
recipientMobile Recipient mobile number information

2016\n/mtaapi/api/businesspartner/v1/order/fulfillRegular sandbox/api/businesspartner/v1/order/fulfillRegular

8.2 [POST] Fulfill Big Product Order
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/fulfillBigProduct
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/fulfillBigProduct
Purpose : to fulfill big product order

Header request:
Body request:
{
"orderItemId" : "25000026173",
"itemSkuCode" : "TOS-16005-00001-00001",
"settlementCode" : "MERCHANT-AWB-1234",
"isDeliveredByMerchant" : true,
"merchantCourierName" : "Merchant courier name",
"merchantCourierType" : "Merchant courier",
"merchantDeliveryDateStart" : 1479166599946,
"merchantDeliveryDateEnd" : 1479166599946,
"isInstallationRequired" : true,
"merchantInstallationDateStart" : 1479166599946,
"merchantInstallationDateEnd" : 1479166599946,
"merchantInstallationOfficer" : "Merchant installation officer",
"merchantInstallationMobile" : "085467894234",
"merchantInstallationNote" : "installation note"
}
orderItemId Order item number
itemSkuCode Blibli’s order item SKU
settlementCode Settlement code/airway bill number information for current package
isDeliveredByMerchant Is delivered by merchant status
merchantCourierName Courrier name information, it’s assigned by merchant side. If merchant using other third party
logistic, merchant can assign with the default value, ex: Merchant Courier JNE.
If merchant their own logistic, he can assign with the their identified courrier name.
Merchant courier type information, the value must be:
• Merchant courier : if the product is delivered by merchant logistic, if you use this
merchantCourierType
option then isDeliveredByMerchant flag must be true
• 3PL : if the merchant using other third party logistic like: JNE, NCS, etc
merchantDeliveryDateStart Merchant delivery start date in epoch time format
merchantInstallationDateEnd Merchant delivery end date in epoch time format
isInstallationRequired To indicate that current product is needs to installed
Merchant installation start date infomation, if isInstallationRequired flag is false then set this
merchantInstallationDateStart
value with null
Merchant installation end date infomation, if isInstallationRequired flag is false then set this value
merchantInstallationDateEnd
with null
Merchant installation officer information, if isInstallationRequired flag is false then set this value
merchantInstallationOfficer
with null

Merchant installation officed phone number infomation, if isInstallationRequired flag is false then
merchantInstallationMobile
set this value with null
Merchant installation note infomation, if isInstallationRequired flag is false then set this value
merchantInstallationNote
with null
Parameter request:
Success response
{
"errorCode": null,
"success": true
}
success To indicate whether the fulfill operation is success or not

2016\n/mtaapi/api/businesspartner/v1/order/fulfillBigProduct sandbox/api/businesspartner/v1/order/fulfillBigProduct

8.3 [POST] Fulfill BOPIS (Buy Online, Pickup In Store) Order
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/fulfillBopis
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/fulfillBopis
Purpose : to fulfill BOPIS order

Header request:
Body request:
{
"orderItemId" : "25000025943",
"itemSkuCode" : "TOQ-15130-00001-00001"
}
orderItemId Order item number
itemSkuCode Blibli’s order item SKU
Parameter request:
Success response
{
"errorCode": null,
"success": true
}

POST POST
bf74d5182b38d45238a23db8988571e0 bf74d5182b38d45238a23db8988571e0
application/json application/json
Mon May 16 14:07:15 WIB 2016 Mon May 16 14:07:15 WIB 2016
/mtaapi/api/businesspartner/v1/order/fulfillBopis /mtaapi-sandbox/api/businesspartner/v1/order/fulfillBopis

8.4 [POST] Partial Fulfill Order
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/partialFulfill
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/partialFulfill
Purpose : to do partial fulfill / out of stock fulfill for current order. Partial fulfill is a condition when merchant can’t fulfill all
of product’s quantity. If merchant do the partial fulfill, the current order item status will become FP and the quantity will set as
merchant complete quantity.
If merchant sent complete quantity = 0, then currect order item statux will become X (canceled). Merchant will get punishment if they
did partial fulfilll with zero quantity (OOS).
Header request:
Body request:
{
"orderNo":"25000025367",
"orderItemNo":"25000026170",
"completeQuantity": 2,
"reason":"stock is empty"
}
Complete quantity which able to fulfilled, if it set with 0 value so it’s mean that merchant do “out
completeQuantity
of stock” (OOS) fulfillment for current order
reason Partial / OOS reason
Parameter request:
Success response
{
"errorCode": null,
"success": true
}

2016\n/mtaapi/api/businesspartner/v1/order/partialFulfill sandbox/api/businesspartner/v1/order/partialFulfill

8.5 [POST] Settle Order
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/order/settleOrder
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/order/settleOrder
Purpose : to do settle order for Big Product and BOPIS type. Settle order is able to hit after merchant doing fulfill order,
settle order API should be hit when the order package is already arrived to the customer.

Header request:
Body request: for Big Product
{
"type":2,
"orderNo":"15000026173",
"orderItemNo":"25000026173",
"deliveredDate" : 1500023472449,
"recipientName" : "argo triwidodo",
"recipientStatus" : "friend"
}
Body request: for BOPIS
{
"type":3,
"orderNo":"15000026173",
"orderItemNo":"25000026173",
"settlementCode" : "358fc02d-7155-4465-b3ba-742660801b74"
}
deliveredDate Delivery date is gotten from the date when order package has been delivered to customer
recipientName Recipient name information that receive the order package
recipientStatus Recipient status that receive the order package, like: father, mother, friend of the recipient, etc
settlementCode Settlement code information, the settlement code is sent to the customer. So merchant must
asking the customer about the settlement code before doing settle order BOPIS.
For Big Product, merchant can assign the settlement code with free value based on merchant
needs, like: the merchant’s settlement code itself, merchant’s awb itself, etc.
For BOPIS order, merchant must ask the settlement code to customer. Then merchant can use
it to settle the order.
Parameter request:
Success response
{

"errorCode": null,
"success": true
}
success To indicate whether the settle order operation is success or not

2016\n/mtaapi/api/businesspartner/v1/order/settleOrder sandbox/api/businesspartner/v1/order/settleOrder

9. Utility API
9.1 [GET] Get Queue Feed API
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/feed/status
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/feed/status
Purpose : get queue feed information for specified bulk process ID

Header request:
Parameter request:
Success response
{
"errorCode": null,
"success": true,
"value": {
"status": "finished",
"action": "updateProduct",
"total": 2,
"success": 2,
"failed": 0
}
}
requestId Current request ID for bulk process
success To indicate that current operation is success or not
status Queue status information:
• finished: indicate that current bulk process is finished
• on process: indicate that current bulk process is not finished yet
action Bulk operation action type:
• createProduct: for bulk create product operation
• updateProduct: for bulk update product summary operation
• updateDetailProduct: for bulk update detail product operation
• postImage: for bulk upload image operation
total Number of total bulk operation in 1 bulk request
success Number of total success bulk operation
failed Number of total failed bulk operation

2016\n/mtaapi/api/businesspartner/v1/feed/status sandbox/api/businesspartner/v1/feed/status

9.2 [GET] Get Queue Feed List
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/feed/list
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/feed/list
Purpose : get all of queue feed list information by date
Header request:
Parameter request:
queueDate {queue-date} Filter queue list by date using format, YYYY-MM-DD, example: 2016-11-29
queueAction {queue-action} Filter queue list by queue action, that is:
• createProduct: queue of bulk action for 'Create Product API'
• updateProduct: queue of bulk action for 'Update Product Summary API'
• updateDetailProduct: queue of bulk action for 'Update Product Detail API'
• postImage: queue of bulk action for 'Upload Image API'
status {queue-status} Filter queue list by queue status, that is:
• in progress: current queue bulk action is in process
• finished: current queue bulk action is finished
page {page-list} Filter returned order list by page list index, the default value is 0
size {list-size} Filter returned order list by size list, the default value is 10
Success response
{
"requestId": "4aaf772e-ed91-4176-a056-cc8129e97f6f",
"errorCode": null,
"success": true,
"content": [
{
"requestId": "80c7f73f-8aae-43d0-9a58-c472c13133ec",
"action": "updateProduct",
"total": 4,
"successCount": 4,
"failedCount": 0,
"status": "finished",
"timeStamp": 1480420814000
},
{
"requestId": "8ab3ff23-e736-4bbc-9a18-44b1eeb4309e",
"action": "createProduct",
"total": 3,
"successCount": 1,
"failedCount": 0,
"status": "in progress",
"timeStamp": 1480420166000

}
],
"pageMetaData": {
"pageSize": 10,
"pageNumber": 0,
"totalRecords": 15
}
}
requestId Request ID for current bulk action, using this value merchant can check the bulk
action status/progress in 'Utility API'
action Bulk operation action type:
total Value of total product/image request in one bulk action
successCount Value of total successful exceution in one bulk action request
failedCount Value of total failed execution in one bulk action request
status Value of queue status, that is:
• in progress: current queue bulk action is in process
• finished: current queue bulk action is finished
timeStamp Value of creation date for current bulk action request in epoch time format

2016\n/mtaapi/api/businesspartner/v1/feed/list sandbox/api/businesspartner/v1/feed/list

9.3 [GET] Get Queue Feed Detail
URL Production : https://api.blibli.com/v2/proxy/mta/api/businesspartner/v1/feed/detail
URL Sandbox : https://apisandbox.blibli.com/v2/proxy/mtaapi-sandbox/api/businesspartner/v1/feed/detail
Purpose : get queue feed detail information
Header request:
Parameter request:
Success response
{
"errorCode": null,
"success": true,
"value": {
"queueFeed": {
"requestAction": "updateProduct",
"total": 1,
"timeStamp": 1480420166411
},
"queueHistory": [
{
"gdnSku": "TOS-16005-00005-00001",
"timestamp": 1480420168275,
"value": "Samsung Galaxy S7",
"isSuccess": true
},
{
"gdnSku": "TOS-16005-00045-00001",
"timestamp": 1480420168275,
"value": "Samsung Galaxy S7",
"isSuccess": false,
"errorMessage": "product sku is not found",
"errorCode": null
}
]
}
}
requestId Request ID for current bulk action, using this value merchant can check the bulk
action status/progress in 'Utility API'
requestAction Bulk operation action type:

total Value of total product/image request in one bulk action
timeStamp Value of creation date for current bulk action request in epoch time format
gdnSku Value of Blibli product item SKU, example: TOS-16005-00011-00001
value Value of product name or image context path response
isSuccess Value of identifier status whether current request is success or not

2016\n/mtaapi/api/businesspartner/v1/feed/detail sandbox/api/businesspartner/v1/feed/detail

Appendix
Appendix I: Create product flow
Appendix II: Update product flow

Appendix III: Order fulfillment flow

Blibli Merchant API Documentation v-3.6.0 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Blibli Merchant API Documentation v-3.6.0 PDF

Uploaded by

Copyright:

Available Formats

2 Dec 2018 MTA API

Page: 1 | Go to table of contents

Page: 2 | Go to table of contents

Page: 3 | Go to table of contents

2.1 API Token

Picture 2.1 Go to “Merchant API” page

Page: 4 | Go to table of contents

Picture 2.3 Set your client credential password

Page: 5 | Go to table of contents

2.2 API Signature

2.2.1 Build the raw signature based on request meta data

2.2.2 Get the API client secret

Page: 6 | Go to table of contents

2.2.3 Hash using HMAC SHA-256

Picture 2.6 Placing API signature using postman

Page: 7 | Go to table of contents

Page: 8 | Go to table of contents

Failed response due to invalid client api username/password

Page: 9 | Go to table of contents

Page: 10 | Go to table of contents

Page: 11 | Go to table of contents

Failed response due to invalid api username

Page: 12 | Go to table of contents

Page: 13 | Go to table of contents

Failed response due to invalid business partner/merchant code

Page: 14 | Go to table of contents

Page: 15 | Go to table of contents

Page: 16 | Go to table of contents

Page: 17 | Go to table of contents

Page: 18 | Go to table of contents

Page: 19 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 20 | Go to table of contents

Page: 21 | Go to table of contents

DESCRIPTIVE_ATTRIBUTE and PREDEFINED_ATTRIBUTE is used as product feature

Raw signature example Raw signature example (sandbox)

Page: 22 | Go to table of contents

Authorization request: No Auth

Page: 23 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 24 | Go to table of contents

Authorization request: No Auth

Raw signature example Raw signature example (sandbox)

Page: 25 | Go to table of contents

Authorization request: No Auth

Page: 26 | Go to table of contents

Page: 27 | Go to table of contents

Authorization request: No Auth

Page: 28 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 29 | Go to table of contents

Page: 30 | Go to table of contents

Page: 31 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 32 | Go to table of contents

Authorization request: No Auth

Page: 33 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 34 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 35 | Go to table of contents

Raw signature example Raw signature example (sandbox)

Page: 36 | Go to table of contents