> ## Documentation Index > Fetch the complete documentation index at: https://docs.smartsend.io/llms.txt > Use this file to discover all available pages before exploring further. # List all services > Returns all available shipping services. This is reference data not filtered by team. ## OpenAPI ````yaml /openapi-v2beta.json get /team/{team}/routing/services openapi: 3.1.0 info: title: Smart Send API description: >- Unified API for shipping operations including service points, routing, and rates. ## Localization The API performs language negotiation to determine the most suitable language for translatable content (such as service names, tracking descriptions, and error messages). The negotiation considers: 1. The `Accept-Language` request header (if provided) 2. The team's configured default language 3. English as the ultimate fallback The resolved language is used for all translatable strings in the response. ## Idempotency Write operations support **idempotency keys** so you can safely retry a request after a network error, timeout, or uncertain outcome without risking a duplicate side effect such as booking the same shipment twice. Idempotency is opt-in: include an `Idempotency-Key` header on a write request (`POST` or `DELETE`) to enable it. Requests sent without the header are not deduplicated. The key is a client-generated string of 16–128 characters (letters, digits, `.`, `_`, `-`) and is compared as-is, so it is case-sensitive. When a key is reused with an identical payload within 24 hours, the API returns the original response (status code and body) without re-executing the operation and sets the `Idempotency-Replayed: true` response header. Reusing a key with a different payload returns `422 Unprocessable Entity`. If the original request is still being processed, the retry returns `409 Conflict` with a `Retry-After` header indicating when to try again. Keys are scoped per client and expire automatically after the 24-hour window. See the [idempotency guide](https://docs.smartsend.io/api-reference/idempotency) for requirements and examples. ## User-Agent We recommend including a descriptive `User-Agent` header with every request, following the `Product/Version (Comments)` pattern from [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231#section-5.5.3). A good User-Agent helps us identify your integration and speeds up debugging when you contact support. Example: `smart-send-logistics/8.1.0 (WooCommerce/8.5.0; WordPress/6.4.2; PHP/8.1)` ## Request-ID We recommend including a unique `Request-ID` header with every request. The value is echoed back in the response and included in internal logs, making it possible to correlate logs from your implementation with logs in Smart Send. This is especially useful when contacting support about a specific request. version: 2.0.0-beta contact: name: Smart Send url: https://www.smartsend.io servers: - url: https://app.smartsend.io/api/v2 description: Production security: - bearerAuth: [] - oauth2: [] tags: - name: Teams description: Teams available to the authenticated user - name: Service Points description: Pickup points and delivery locations - name: Routing description: Reference data (carriers, services, addons) and route availability - name: Rates description: Shipping rates and pricing for specific shipments - name: Tracking description: Shipment tracking information and event history - name: Shipments description: Create and manage shipments - name: Booking description: Booking of shipments externalDocs: description: Booking documentation url: https://docs.smartsend.io/features/booking - name: Booking batches description: |- Batch operations for booking multiple shipments asynchronously. Processing operates after the _first-in-first-out_ principle. externalDocs: description: Batch booking documentation url: https://docs.smartsend.io/features/booking#batch-booking paths: /team/{team}/routing/services: get: tags: - Routing summary: List all services description: >- Returns all available shipping services. This is reference data not filtered by team. operationId: listServices parameters: - $ref: '#/components/parameters/team' - $ref: '#/components/parameters/Accept-Language' - $ref: '#/components/parameters/Request-ID' responses: '200': description: Services retrieved successfully headers: Correlation-ID: $ref: '#/components/headers/Correlation-ID' Request-ID: $ref: '#/components/headers/Request-ID' content: application/json: schema: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/Service' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalServerError' '503': $ref: '#/components/responses/ServiceUnavailable' security: - bearerAuth: [] - oauth2: - routing components: parameters: team: name: team in: path required: true schema: type: string minLength: 1 examples: - ad9546c1-393e-49a5-9a72-5cc146c9bec5 description: Team identifier. All resources are scoped to this team. Accept-Language: name: Accept-Language in: header required: false schema: type: string default: en examples: - da-DK, da;q=0.9, en;q=0.8 description: >- Preferred language(s) for translatable content using BCP 47 language tags. Supports quality values (q-factors) for priority ordering. The API negotiates the best available language based on this header, the team's configured language, and available translations. If omitted, the team's default language is used. Request-ID: name: Request-ID in: header required: false schema: type: string minLength: 1 maxLength: 128 pattern: ^[A-Za-z0-9._-]{1,128}$ description: >- Any value passed in this request will be returned in the same header. This can be used to correlate requests between client and server. examples: uuid: summary: UUID v4 value: 3f5d9a8e-8e6f-4d9b-9d9c-9c6b3db2d1a0 opaque: summary: Opaque client-generated key value: booking-12345-at-1768609378 headers: Correlation-ID: description: >- Unique identifier for the request, useful for debugging and support. The id is automatically assigned to each request and can helps trace the request in system logs. Provide this value in case of any errors helps debugging. schema: type: string format: uuid examples: - 550e8400-e29b-41d4-a716-446655440000 Request-ID: description: >- If the request contained a `Request-ID` then the same value is returned as the `Request-ID`. This can be used to correlate requests between client and server. schema: type: string Retry-After: description: Number of seconds to wait before retrying the request. schema: type: integer examples: - 30 schemas: Service: type: object description: >- Base shipping service definition with carrier information and routing flags (no addons). required: - service_code - service_name - carrier_code - carrier_name - carrier_logo_url - carrier_icon_url - is_pickup - is_return properties: service_code: type: string description: Full service code (carrier_code + '_' + carrier-specific code) examples: - postnord_agent service_name: type: string description: Localized human-readable service name examples: - Pickup Point carrier_code: type: string description: Unique carrier code examples: - postnord carrier_name: type: string description: Human-readable carrier name examples: - PostNord carrier_logo_url: type: string format: uri description: URL to the carrier's logo image carrier_icon_url: type: string format: uri description: URL to the carrier's icon image is_pickup: type: boolean description: Whether this service delivers to pickup points is_return: type: boolean description: Whether this is a return service ErrorResponse: type: object required: - message properties: message: type: string description: Human-readable error message examples: - Something unexpected happened. RateLimitErrorResponse: type: object required: - message properties: message: type: string description: Human-readable error message indicating rate limit exceeded responses: Unauthorized: description: Authentication credentials were missing or invalid headers: Correlation-ID: $ref: '#/components/headers/Correlation-ID' Request-ID: $ref: '#/components/headers/Request-ID' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Forbidden: description: The authenticated user does not have permission to perform this action headers: Correlation-ID: $ref: '#/components/headers/Correlation-ID' Request-ID: $ref: '#/components/headers/Request-ID' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' TooManyRequests: description: Rate limit exceeded. Wait before retrying. headers: Correlation-ID: $ref: '#/components/headers/Correlation-ID' Request-ID: $ref: '#/components/headers/Request-ID' Retry-After: $ref: '#/components/headers/Retry-After' content: application/json: schema: $ref: '#/components/schemas/RateLimitErrorResponse' InternalServerError: description: An unexpected error occurred on the server headers: Correlation-ID: $ref: '#/components/headers/Correlation-ID' Request-ID: $ref: '#/components/headers/Request-ID' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' ServiceUnavailable: description: The service is temporarily unavailable. Please try again later. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer oauth2: type: oauth2 description: OAuth 2.0 Authorization Code flow for API access flows: authorizationCode: authorizationUrl: https://app.smartsend.io/oauth/authorize tokenUrl: https://app.smartsend.io/oauth/token scopes: service_points: Access service points and pickup locations routing: Access routing information (carriers, services, addons, routes) tracking:read: Access shipment tracking information rates:read: Get shipping rates and pricing shipment:read: Read shipment information shipment:write: Create and manage shipments ````