1"use strict";(self["webpackChunknxcloud"]=self["webpackChunknxcloud"]||[]).push([[3635],{33635:function(e,n,t){t.r(n),n["default"]='# Initialize Journey Token\nGet Zalo Journey Token through API\n\n- URLï¼`https://api.nxcloud.com/v1/zalo/initJourneyToken`\n- Methodï¼`POST`\n- Content-Typeï¼`application/json`\n- Authentication requiredï¼`Yes`\n\n## Authentication Mechanism\n\nPlease refer to the authentication rules at the specified addressï¼[[The API interface invocation conventions]](/document-en/common/interface-contract)\n\n### Parameters Headerï¼\n\n| **Parameter** | **Datatype** | **Mandatory** | **Example Value** | **Description** |\n| ------------ | ------------ | ------------ | -------------------------------- | ------------------------------------------------------------ |\n| accessKey | String | yes | fme2na3kdi3ki | User identity identifier |\n| ts | String | yes | 1655710885431 | The current timestamp of the request (units: milliseconds). The NXCLOUD server allows a maximum time deviation of 60 seconds for client requests |\n| bizType | String | yes | 9 | The Zalo business type, set to a fixed valueâ9â |\n| action | String | yes | mt | Send Zalo ZNS requestï¼set to a fixed valueâmtâ |\n| sign | String | yes | 6e9506557d1f289501d333ee2c365826 | The API input parameter signatureï¼[Signature algorithm](API%20auth%20basics.pdf) |\n\n### Receipt Parameters\n- body parameters:\n\nParameter | Datatype | Mandatory | Example Value | Description\n-- | -- | -- | -- | --\nappkey | String | yes | pem28kje | Application appkey\nphone | String | yes | 86158xxxx1795 | The Zalo phone number of the message recipient must include the country code. For example, 86158xxxx1795\ntokenType | String | yes | token_logistics_7 | Journey Token Type: <br> **token_logistics_7**<br>**token_logistics_30**<br>**token_coach_bus_7**<br>**token_coach_bus_30** \n\n### Receipt Examples\n\n```json\n{\n "appkey": "cWF32dfsa",\n "phone": "848xxxx1795",\n "tokenType": "token_logistics_7"\n}\n```\n\n## Example Respond\n\n### Successful Example\n```json\n{\n "code": 0,\n "message": "Success",\n "data": {\n "journeyId": "1257624175686111232",\n "token": "HmXFqeO5jM1Mw96XuhlVwR1uQQQAxvu8faW8LtTFhXaHuDrywWweA9Zt5bmFCy0JZOMG_2uo3ZWdRDS1rBeJ7NnOZgiLtw78NzDehSkeEyWJCETRMvHCF-8PVSI16UjNuEMVkAkP21p-xCcMcba7l74cJuouUgZlyW1sMIx1Dm6yu6aKswXaeG3zSCb5mYwJb-AZvxsFd8U1BJhmNQYKPe78TyRz5NphTrX-bI8wF5bOpYDxv4DmkcDDgABP6n6E"\n }\n}\n```\n\n### Failure Example\n```json\n{\n "code": -1,\n "message": "Failure",\n "traceId": "77f8709b545f4fee93fd7f098be9df04"\n}\n```\n<a name="xymsm"></a>\n\n## Status code description\n\nCode | Message | Description\n-- | -- | --\n0 | Success | \n-1 | Failure | Please contact technical personnel to troubleshoot the issue.\n1000~100X | Authentication failed | For more information, please refer to the API authentication section.\n1100 | Customer does not exist / Status is unavailable | Account status abnormal. Please contact the business personnel to resolve the account issue.\n9000 | Request parameter error | Parameter missing. Please check the required parameters.\n9001 | System business error | System business error. Please contact technical personnel to troubleshoot the issue.\n9002 | Phone number error | Illegal number. Please check the correctness of the number.\n9003 | Customer APP does not exist / Status is unavailable | Application status abnormal. Please contact the business personnel to address the cloud platform application creation/disabling issue.\n9004 | Destination not enabled on your rate plan. | Application pricing missing. Please contact the business personnel to address the application pricing issue.\n9005 | Missing customer APP routes | Application routing missing. Please contact technical personnel to investigate the route.\n9010 | Rate limit exceeded | Rate limit exceeded\n17009 | Zalo vendor token does not exist | Vendor Journey Token quotation does not exist\n17010 | Zalo vendor token status is unavailable | Vendor Journey Token quotation status is unavailable\n9999 | Unknown error | Please contact technical personnel to troubleshoot the issue.'}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.