Upload File by FileType in Request

The POST /Files/UploadFile endpoint allows partners to upload files of specific types to the Netevia platform using multipart form-data. Files can represent user avatars, identity documents, business registration materials, tax forms, insurance documents, and more. Optionally, a file can be associated with a specific transaction or a business subprofile authorized user.

Endpoint

POST /Files/UploadFile

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a customer or partner needs to attach supporting documents to their account or to a specific transaction — for example, uploading a government-issued ID during KYC verification, submitting a business license for underwriting, or attaching a receipt image to a transaction record. This endpoint is also used to set profile and card icon images. For business customers, files can be scoped to a specific authorized user (subprofile) by including SubProfileId.

Request Body

Content-Type: multipart/form-data

Supported FileType values:

Response

200 OK

Returns a boolean true when the file was uploaded successfully.

true

400 Bad Request

Returns a problem details object when the file could not be uploaded due to a validation error.

{
  "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
  "title": "Bad Request",
  "status": 400,
  "detail": "The FileType field is required.",
  "instance": "/Files/UploadFile"
}

Error Codes

Common Mistakes

• Omitting the FileType field — it is required and must exactly match one of the supported enum string values (case-sensitive).
• Sending the request as application/json instead of multipart/form-data — the File binary field requires multipart encoding.
• Including TransactionId without an actual matching transaction in the system, which results in a 400 or 404 error.
• Using SubProfileId for personal customer accounts — subprofiles are only available for business customers.
• Sending FileType: TransactionIcon without providing a valid TransactionId — the transaction association is required for that file type.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an expiring Bearer token
• GET /Files/{fileId} — Retrieve a previously uploaded file by its ID
• POST /Customers/Business — Create a business customer whose documents may be uploaded via this endpoint
• POST /Customers/Personal — Create a personal customer whose identity documents may be uploaded via this endpoint

Example

curl -X POST https://api.banking.netevia.dev/Files/UploadFile \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -F "File=@/path/to/drivers_license.pdf" \
  -F "FileType=DriverLicense"

Upload a transaction receipt associated with a specific transaction:

curl -X POST https://api.banking.netevia.dev/Files/UploadFile \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -F "File=@/path/to/receipt.jpg" \
  -F "FileType=TransactionIcon" \
  -F "TransactionId=txn_abc123def456"

Upload a business license for a subprofile authorized user:

curl -X POST https://api.banking.netevia.dev/Files/UploadFile \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -F "File=@/path/to/business_license.pdf" \
  -F "FileType=BusinessLicense" \
  -F "SubProfileId=42"