Business Information
The POST /businessInfo endpoint allows authorized users to submit or update their business profile information within the Netevia Banking platform. It supports both initial onboarding of business details and subsequent updates to keep business records current. All changes are applied in real-time once the request is successfully processed.
Endpoint
POST /businessInfo
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 during the business customer onboarding flow to record key financial profile details such as the business start date and annual revenue. It is also used whenever a business customer needs to update these figures — for example, at the start of a new fiscal year or after a significant change in revenue. This information is used by Netevia for underwriting, account management, and compliance purposes.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| businessStartDate | string (date-time) | Yes | The date the business was established, in ISO 8601 date-time format (e.g., 2015-03-01T00:00:00Z) |
| annualBusinessRevenue | integer (int64) | Yes | The business's annual revenue in whole dollars. Must be 0 or greater. |
{
"businessStartDate": "2015-03-01T00:00:00Z",
"annualBusinessRevenue": 500000
}Response
200 OK
A 200 response confirms that the business profile information was successfully submitted or updated. The response body returns a success confirmation.
{
"success": true
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (businessStartDate or annualBusinessRevenue), invalid date-time format, or annualBusinessRevenue is negative |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions — authenticated user is not authorized to update this business profile |
| 404 | Business profile not found for the authenticated user |
| 500 | Internal server error |
Common Mistakes
- Sending
businessStartDatein a non-ISO 8601 format (e.g.,03/01/2015instead of2015-03-01T00:00:00Z) causes a 400 validation error. - Omitting either
businessStartDateorannualBusinessRevenue— both are required fields and the request will fail without them. - Sending
annualBusinessRevenueas a float or string instead of an integer (int64); use whole dollar amounts only. - Including extra fields not defined in the schema — the model uses
additionalProperties: false, so unexpected fields will be rejected.
Related Endpoints
POST /api/auth/v2— Obtain a Bearer token required for authenticationPOST /api/auth/refresh— Refresh an expiring Bearer tokenGET /businessInfo— Retrieve the current business profile information (if available)
Example
curl -X POST https://api.banking.netevia.dev/businessInfo \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"businessStartDate": "2015-03-01T00:00:00Z",
"annualBusinessRevenue": 500000
}' 200Success
