Base URL and Headers
All REST API requests share the same base URL and header conventions; this page explains how {baseUrl} is constructed and which headers are required.
Service Address
{baseUrl} is the service domain and does not include /wlte/v1. Only HTTPS endpoints are supported.
text
https://openapi.svnwi.comThe full request URL is composed of {baseUrl} plus the endpoint path. Environment-specific addresses are provided during delivery.
General Request Rules
- Endpoints with a request body use
Content-Type: application/json - All endpoints are recommended to use
Accept: application/json - Authenticated endpoints must include
Authorization: Bearer {accessToken} - JSON fields use camelCase
- Time fields use RFC3339 UTC strings
- Time fields must not use internal millisecond timestamps or non-standard string formats
Integration Requirements
This API is for server-side integration only. It is not intended to be called directly from browsers, mobile apps, or other client-side environments.
Customers must manage credentials and API calls within their own backend services, then provide the required capabilities to upstream applications through their own services.
Security Rules
- Machine credentials must be stored on the customer's server side
- Do not embed
clientSecretin browser code, mobile apps, or public repositories - Access tokens should be treated as secrets and should not be written to public logs
- Credential rotation and environment-specific domains are provided during delivery
Request Trace ID
- The server must return
requestIdin the response envelope - Clients should record
requestIdfor troubleshooting and support cases
