> ## Documentation Index > Fetch the complete documentation index at: https://docs.xerobi.com/llms.txt > Use this file to discover all available pages before exploring further. # Get speed test configuration > Returns configuration for running speed tests against Xerobi's nearest server. The server selection is automatic based on the customer's location. **Use Cases:** - Implement custom speed test tools - Verify connection performance - Troubleshoot bandwidth issues **Implementation Notes:** - Use the latency endpoint for ping tests (typically 10 requests) - Download/upload tests should run for at least 10 seconds for accuracy - Tests should be performed during off-peak hours for best results Returns configuration for running speed tests against Xerobi's nearest server. The server selection is automatic based on the customer's location. **Use Cases:** * Implement custom speed test tools * Verify connection performance * Troubleshoot bandwidth issues **Implementation Notes:** * Use the latency endpoint for ping tests (typically 10 requests) * Download/upload tests should run for at least 10 seconds for accuracy * Tests should be performed during off-peak hours for best results ## OpenAPI ````yaml GET /consumer/speedtest/config openapi: 3.1.0 info: title: Xerobi Fiber API description: >- API for Xerobi Fiber customers and business clients. ## Overview The Xerobi Fiber API provides two distinct interfaces: - **Consumer API**: Simple, user-friendly endpoints for residential customers to check their network status, account details, usage statistics, and run speed tests. - **Business API**: Advanced endpoints for enterprise clients to manage IP assignments, monitor bandwidth usage, and automate network operations. ## Authentication All endpoints require Bearer token authentication. Include your JWT token in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` Tokens can be obtained from your Xerobi account dashboard. ## Versioning All requests must include the `Hixe-Version` header with the API version date (format: YYYY-MM-DD). Current version: `2026-01-01` ## Rate Limiting - Consumer endpoints: 100 requests per minute - Business endpoints: 1000 requests per minute Rate limit information is included in response headers: - `X-RateLimit-Limit`: Maximum requests allowed - `X-RateLimit-Remaining`: Requests remaining in current window - `X-RateLimit-Reset`: Unix timestamp when the limit resets version: '2026-01-01' contact: name: Xerobi API Support email: support@xerobi.com url: https://support.hixbe.com license: name: Proprietary url: https://hixbe.com/terms servers: - url: https://api.hixbe.com/fiber description: Production API security: - bearerAuth: [] tags: - name: Consumer description: Endpoints for residential customers - name: Business description: Endpoints for enterprise clients paths: /consumer/speedtest/config: get: tags: - Consumer summary: Get speed test configuration description: >- Returns configuration for running speed tests against Xerobi's nearest server. The server selection is automatic based on the customer's location. **Use Cases:** - Implement custom speed test tools - Verify connection performance - Troubleshoot bandwidth issues **Implementation Notes:** - Use the latency endpoint for ping tests (typically 10 requests) - Download/upload tests should run for at least 10 seconds for accuracy - Tests should be performed during off-peak hours for best results operationId: getSpeedTestConfig parameters: - $ref: '#/components/parameters/hixeVersionHeader' responses: '200': description: Successfully retrieved speed test configuration content: application/json: schema: $ref: '#/components/schemas/SpeedTestConfig' example: server: speedtest-ny.hixbe.com latency_endpoint: https://speedtest-ny.hixbe.com/latency download_endpoint: https://speedtest-ny.hixbe.com/download upload_endpoint: https://speedtest-ny.hixbe.com/upload recommended_duration_seconds: 10 '401': $ref: '#/components/responses/UnauthorizedError' '429': $ref: '#/components/responses/RateLimitError' components: parameters: hixeVersionHeader: name: Hixe-Version in: header description: 'API version in YYYY-MM-DD format. Current version: 2026-01-01' required: true schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-01-01' schemas: SpeedTestConfig: type: object description: Configuration for running speed tests against Xerobi servers properties: server: type: string description: Primary speed test server hostname example: speedtest-ny.hixbe.com latency_endpoint: type: string description: Endpoint for latency/ping tests example: https://speedtest-ny.hixbe.com/latency download_endpoint: type: string description: Endpoint for download speed tests example: https://speedtest-ny.hixbe.com/download upload_endpoint: type: string description: Endpoint for upload speed tests example: https://speedtest-ny.hixbe.com/upload recommended_duration_seconds: type: integer description: Recommended test duration for accurate results example: 10 default: 10 required: - server - latency_endpoint - download_endpoint - upload_endpoint Error: type: object description: Standard error response properties: error: type: object properties: code: type: string description: Error code for programmatic handling example: invalid_request message: type: string description: Human-readable error message example: The Hixe-Version header is required details: type: object description: Additional error details nullable: true required: - code - message required: - error responses: UnauthorizedError: description: Authentication failed - invalid or missing token content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: unauthorized message: Invalid or expired authentication token RateLimitError: description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: rate_limit_exceeded message: Too many requests. Please retry after 60 seconds headers: X-RateLimit-Limit: schema: type: integer description: Maximum requests allowed per window X-RateLimit-Remaining: schema: type: integer description: Requests remaining in current window X-RateLimit-Reset: schema: type: integer description: Unix timestamp when rate limit resets Retry-After: schema: type: integer description: Seconds to wait before retrying securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT token obtained from Xerobi account dashboard ```` ## Related topics - [Get Test Result](https://docs.xerobi.com/speed-api/endpoint/get-result.md) - [Speed Test Server](https://docs.xerobi.com/more/speed-test.md) - [Get Statistics](https://docs.xerobi.com/speed-api/endpoint/get-statistics.md) - [Xerobi Speed Test API](https://docs.xerobi.com/speed-api/introduction.md) - [Download Speed Test](https://docs.xerobi.com/speed-api/endpoint/download-test.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.