For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upload File

Endpoint: POST /v2/gc/files/upload

Description: Upload a supporting document (KYC, contract, logistics, payee proof, etc.) and obtain a reusable file path for use in other API calls.

Request

Request Form-Data Field Descriptions

Field Name
Type
Required
Description

bizType

string

Yes

Document category. Enum: PAYMENT | UPLOAD | REPORT | CUSTOMS_RECEIPT | NETWORK_ACCESS | COMMERCIAL | LOGISTICS | PAYEEINFO | OTHER

file

file

Yes

The binary document to upload (e.g. PDF, image).

Request sample

// multipart/form-data request — see the form-data field table above; no JSON body.

Response

Response Field Descriptions

Field Name
Type
Description

code

number

Response code.

state

number

State of the response.

data

object

Uploaded file details.

message

string

Response message.

neoResponseId

string

Unique NeoX response identifier.

data object fields:

Field Name
Type
Description

fileName

string

Original file name of the uploaded document.

path

string

Reusable file reference path. Pass this value in other API calls (e.g. kycFiles, contractFiles, paymentProofList, detailPath, frontPath).

Response sample

Example cURL

Notes

  • Requires Bearer token in the Authorization header.

  • The Accept-Language header can be used to specify the response language (Support: "vi", "en").

  • The request must be sent as multipart/form-data; do not use application/json.

  • The returned path value is used as a file reference in other API calls, including kycFiles, contractFiles, paymentProofList, detailPath, frontPath, and similar fields.

  • Choose the bizType value that best matches the document's intended purpose.

Last updated

Was this helpful?