Upload a file
post
/api/erp/integrations/resources/v1/{locale}/files/upload
Uploads files to the specified locale on the server.
Request
Path Parameters
-
locale(required): string
The locale for which the file is being uploaded.
Supported Media Types
- multipart/form-data
Root Schema : schema
Type:
Show Source
object
-
dateformat(required): string
The date format used in the file.
-
file: string
(binary)
The file to be uploaded. Required if `forceTrigger` and `fileId` are not provided.
-
fileId: string
ID of the existing file. Optional. Required if `file` is not provided.
-
flowName(required): string
The name of the flow associated with the upload.
-
forceTrigger: boolean
Flag to force the trigger. Optional.
Match One Schema
Show Source
Response
Supported Media Types
- application/json
201 Response
File uploaded and processed successfully.
Root Schema : schema
Type:
Show Source
object
-
dateFormat: string
The date format to be used for the file being uploaded.Example:
YYYY-MM-DD
-
fileID: string
The unique identifier of the file.Example:
501984260292120576
-
flowName: string
The name of the flow for which the service is being invoked.Example:
fah-import
-
uploadedTime: string
(date-time)
The date and time when the file was uploaded.Example:
2024-12-19T05:51:04.615257040Z
-
zipFileName: string
The name of the zip file that was uploaded.Example:
ORACPTASSWQY.ORCLFSN.JPM_VC_STATEMENT.12152024111212.csv.zip
400 Response
Bad Request. Invalid parameters or file.
401 Response
Unauthorized. Bearer token is missing or invalid.
500 Response
Internal Server Error. Something went wrong on the server.
Root Schema : schema
Type:
Show Source
object
-
errorCode: integer
The error code used to identify the type of error.Example:
5110
-
errorDescription: string
A brief description of an error.Example:
The ERP_AP_VCC_CARD_STATEME process can't be completed. Please contact your help desk.