Submit Additional Application
This endpoint allows an existing authenticated user to submit a new credit card application for a specific card product. It is used after initial registration when the user wants to apply for a different or additional card product. The application is evaluated based on the user's current profile and financial details already on file.
Endpoint
POST /api/users/submitAdditionalApplication/{cardProductId}
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when an existing Netevia user wants to apply for an additional or different credit card product beyond their initial card. This is appropriate when a partner offers multiple card products and the user is eligible to hold more than one, or when upgrading or diversifying card offerings for a customer. The card product must already exist within the Netevia platform and be accessible by the partner.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
cardProductId | string | Yes | The unique identifier of the credit card product the user is applying for. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
error | string | Error message if the operation failed; null on success. |
sucess | boolean | Indicates whether the application was submitted successfully. Note: field name is spelled sucess (single s) in the schema. |
data | object | The created application record. See fields below. |
data.id | integer (int32) | Internal record identifier. |
data.createdDate | string (date-time) | Timestamp when the application record was created. |
data.updatedDate | string (date-time) | null | Timestamp of the last update to the record, or null if never updated. |
data.profileId | integer (int32) | Internal profile ID of the user who submitted the application. |
data.partnerId | integer (int32) | null | Internal ID of the partner associated with this application. |
data.openApplicationId | string | null | The platform-assigned application identifier. |
data.applicationStatus | integer (int32) | Status code of the application. Enum values: 0, 1, 2, 3, 4 (maps to pending, approved, declined, etc.). |
data.applicationDate | string (date-time) | null | Timestamp when the application was submitted. |
data.approvalDate | string (date-time) | null | Timestamp when the application was approved, or null if not yet approved. |
data.cardProductId | string | null | The card product ID associated with this application. |
{
"error": null,
"sucess": true,
"data": {
"id": 10482,
"createdDate": "2025-11-14T09:22:31Z",
"updatedDate": null,
"profileId": 7731,
"partnerId": 42,
"openApplicationId": "app_8c3f2a1b9d4e7c60",
"applicationStatus": 1,
"applicationDate": "2025-11-14T09:22:31Z",
"approvalDate": "2025-11-14T09:23:05Z",
"cardProductId": "prod_visa_business_rewards"
}
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Invalid input data or missing required information |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to submit the application |
| 404 | The specified cardProductId does not exist |
| 500 | Internal server error while processing the request |
Common Mistakes
- Providing a
cardProductIdthat does not exist or is not accessible to the partner will result in a404error. - Forgetting to include the
Authorization: Bearer {token}header will result in a401 Unauthorizedresponse. - The response field for success is spelled
sucess(notsuccess) — match this exact spelling when parsing the response. - Submitting when the Bearer token has expired (tokens last 10 minutes); refresh via
POST /api/auth/refreshbefore calling this endpoint.
Related Endpoints
POST /api/auth/v2— Obtain a Bearer token for authenticationPOST /api/auth/refresh— Refresh an existing Bearer tokenGET /api/users/USERID— Retrieve user profile details before submitting an application
Example
curl -X POST https://api.banking.netevia.dev/api/users/submitAdditionalApplication/prod_visa_business_rewards \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"