> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set published-network priority order

> Sets your organization's preferred ranking of other providers' published charger networks, replacing the whole list in one go. Spirii uses this ranking only when a charger can be reached through more than one network. Each network you list has to be one your organization can actually access. Send an empty list to clear your preference and let Spirii choose the order.



## OpenAPI

````yaml /openapi/emsp-tenant/openapi.yaml put /emsp/v1/tenant/published-network-priority-order
openapi: 3.0.0
info:
  title: Spirii EMSP - Tenant Management API
  description: 'Manages the EMSP tenant aggregate: tenant profile, EMP-Identities.'
  version: v1
  contact: {}
servers:
  - url: https://api.spirii.com
    description: Production
security: []
tags:
  - name: Tenant
    description: Tenant profile and published-network priority order
  - name: EMP Identity
    description: Register and manage a tenant’s EMP identities
paths:
  /emsp/v1/tenant/published-network-priority-order:
    put:
      tags:
        - Tenant
      summary: Set published-network priority order
      description: >-
        Sets your organization's preferred ranking of other providers' published
        charger networks, replacing the whole list in one go. Spirii uses this
        ranking only when a charger can be reached through more than one
        network. Each network you list has to be one your organization can
        actually access. Send an empty list to clear your preference and let
        Spirii choose the order.
      operationId: tenant_set_published_network_priority_order
      parameters:
        - name: Idempotency-Key
          in: header
          description: >-
            Client-generated unique key per operation intent (UUID). Same key +
            identical body replays the original response; same key + different
            body returns 409.
          required: true
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PublishedNetworkPriorityOrderDto'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PublishedNetworkPriorityOrderDto'
        '400':
          description: Request validation failed
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetailDto'
        '404':
          description: Tenant not found
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetailDto'
components:
  schemas:
    PublishedNetworkPriorityOrderDto:
      type: object
      properties:
        network_ids:
          description: Ordered list of Published Base Network IDs in tiebreak preference
          type: array
          items:
            type: string
            format: uuid
      required:
        - network_ids
    ProblemDetailDto:
      type: object
      properties:
        type:
          type: string
          example: about:blank
          description: >-
            URI identifying the problem type (about:blank until the docs site is
            live)
        title:
          type: string
          example: Tenant not found
        status:
          type: number
          example: 404
        detail:
          type: string
          example: No tenant exists with id 0192...c3.
        instance:
          type: string
          example: /v1/tenant/profile
        code:
          type: string
          example: tenant_not_found
          description: Stable machine-readable error code
        trace_id:
          type: string
          example: abc123def456
          description: Correlation id; matches dd.trace_id in Datadog
        timestamp:
          type: string
          example: '2026-06-10T09:30:00.000Z'
          format: date-time
        errors:
          description: Field-level validation errors (validation failures only)
          type: array
          items:
            $ref: '#/components/schemas/ProblemFieldErrorDto'
      required:
        - type
        - title
        - status
        - detail
        - instance
        - code
        - trace_id
        - timestamp
    ProblemFieldErrorDto:
      type: object
      properties:
        field:
          type: string
          example: workspace_id
        code:
          type: string
          example: is_uuid
        message:
          type: string
          example: workspace_id must be a UUID
      required:
        - field
        - code
        - message

````