Export DID Mappings of an Inbound Route

Records an export operation for the DID mappings of an inbound route. In the current implementation, the mapping file is generated on the client, and this interface only records an export audit entry with the file name.

Request URL

POST {base_url}/uc-cconfig/api/v1/inbound-routes/{id}/did-mappings/export

Request parameters

Headers


Parameter	Required	Type	Description
Authorization	Yes	String	The access token used for authentication. Format: Bearer `{access_token}`.
x-tenant-code	Yes	String	The tenant name. Note: You can obtain tenant name using the Query Tenants interface.

Path parameters


Parameter	Required	Type	Description
id	Yes	String	The ID of the inbound route. You can obtain the ID using the Search Inbound Routes interface. Set this parameter to `0` when exporting from the page of a new inbound route, in which case the route lookup is skipped and only the export audit entry is recorded.

Body parameters


Parameter	Required	Type	Description
fileName	No	String	The name of the exported file. The value is recorded in the export audit entry.

Response parameters


Parameter	Type	Description
requestId	String	The unique ID of the request, which can be used to quickly locate the request.
code	String	The HTTP status code of the request. `200`: Request succeeded. Non-200 value: Request failed.
message	String	The status message of the request.
detailMessage	String	The detailed error information. When the request is successful, this parameter returns empty.
result	Object<Export_Result>	The export result.

Export_Result


Parameter	Type	Description
taskId	String	The ID of the asynchronous export task. The current implementation returns an empty string because the file is generated on the client.

Example

Request example

POST /uc-cconfig/api/v1/inbound-routes/366500156627767296/did-mappings/export HTTP/1.1
Host: api.cn.novoone.com
Authorization: Bearer eyJraWQiOiJjbi0wLWtleS0xIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiJkaXN0cmlidXRvcmV4YW1wbGVAb3V0bG9vay5jb20iLCJhcHBfa2V5Ijoic2xOdnQzaHc1NXB2Vm5HRlNhR2ZOVTNmMWxYQ3lpa08iLCJncmFudF90eXBlIjoib3BlbmFwaSIsImNsaWVudF9leHQiOnsiZGVzY3JpcHRpb24iOiLnrKzkuInmlrnlkIjkvZzkvJnkvLTlupTnlKgiLCJwYXJ0bmVyIjoi56S65L6L5ZCI5L2c5LyZ5Ly0In0sImNsaWVudF90eXBlIjoib3BlbmFwaSIsImV4cCI6MTc5MzYzNzIxOSwiaWF0IjoxNzkzNjE1NjE5LCJqdGkiOiJiNWUzYTNmZi1mN2RmLTRmYjgtOWQ0Zi04NzUzNmU2OGUwZGQiLCJjbGllbnRfaWQiOiJub3ZvLW9wZW4tcGxhdGZvcm0iLCJ1c2VyX2V4dCI6eyJyb2xlSWRzIjpbM10sInN0eXBlIjoiQURNSU4iLCJ0ZW5hbnRDb2RlIjpudWxsLCJ0eXBlIjoiUF9BQ0NPVU5UIiwidXNlcklkIjozMDc2OTEzNjQ0OTE1OTk4NzIwLCJlbWFpbCI6ImRpc3RyaWJ1dG9yZXhhbXBsZUBvdXRsb29rLmNvbSIsInVzZXJuYW1lIjoiZGlzdHJpYnV0b3JleGFtcGxlQG91dGxvb2suY29tIiwidWNJZCI6MzA3NjkxMzY0NDg5MDgzMjg5Nn19.gVc8o7tevTHP2Ytwby78ZmEX3dcQIMOd9ADhGwNKwVlvXIQ2_TzP-g-rGu0T8rtT5dyZ_jvXErog5J-2RVXOzR9wE9TojkI8u1fDW8YujdsUZ-0nWJvm9JgtqxgoHpztOCWrxs8vQB1LdTWFLGb2ju7mFad3_9n7MIys13LqoLHVmgUl92oagEr2yHEi3fQPOfAbhQiQDxHNqPTtqV7eAIIHIEu8YZvHWaOeAkGl1sFO_bLe8k0P41MPM2ejTGrxJQ5XQ3dyRNf3gH5KykhAUOmvZV9gxgtXIFYzkAQiRGFBVFVmOliG9wBtHIV1xLroD8pLorXnvc6Ea4fvknWGMg
x-tenant-code: jint
Content-Type: application/json
{
  "fileName": "did-mappings-20261102.csv"
}

Response example

HTTP/1.1 200 OK
{
  "requestId": "55b17799e793ab811f7958ebc2df2e9c",
  "code": "200",
  "message": "SUCCESS",
  "detailMessage": "",
  "result": {
    "taskId": ""
  }
}

Note:

The response returns an empty taskId in the current implementation. No downloadable export task is created; use the Get DID Mappings of an Inbound Route interface to retrieve the current mappings.