Web Service Security
The following document contains a brief explanation about Web Services that will be used by the application to manage data transactions between Tokopedia and Partner.
See the below table to see the header requirements of each process request:
Process | Authorization | Signature | Key |
---|---|---|---|
Get Token | ![]() | ![]() | |
Health Check | ![]() | ![]() | ![]() |
Inquiry | ![]() | ![]() | ![]() |
Payment | ![]() | ![]() | ![]() |
Check Status | ![]() | ![]() | ![]() |
Get Balance | ![]() | ![]() | ![]() |
Callback | ![]() | ![]() | ![]() |
For each explanation of parameters can be found below :
Parameter | Value | Description |
---|---|---|
Authorization | Bearer Token | Given API Token (see 6.1. Get Token) |
Signature | Payload Signature | Generated based on request/response payload (see 8. Signature) |
Key | Encrypted Payload Decryption Key | The encrypted key that will be used for payload decryption (see 9. Encryption) |
Client-guid | Generated ID From Tokopedia | Identifier partner when do callback (see 6.7. Callback) |
Content-Type | application/octet-stream | Data type of content body (denoting encrypted payload (binary)) |