All updates
Non-Breaking

MNP Spain — `service_provider_id` is now optional in Create Porting (ES)

·By ksanchez

Changes

The service_provider_id field inside donor_details of the Create Porting (ES) request body (CreatePortingES / CreateDonorDetailsES) is now optional.

Previously, service_provider_id was required when creating a porting request for Spain (country = "ES"). With this update, partners may omit the field and let the Connect API resolve the donor service provider automatically.

This is a non-breaking change. Requests that continue to include service_provider_id are processed exactly as before — the supplied value is used as-is and no lookup is performed.


Scope

  • API versions affected: 2026-02-05.
  • Schema affected: CreateDonorDetailsES (Spain only).
  • Other countries (DE, IE, NL, PL, UK, …) and other porting schemas are not affected.

Example — Create Porting (ES) without service_provider_id

{
  "direction": "in",
  "subscription_id": "subs_01J9XJ11WTYFWFH5JD2YM1S18S",
  "msisdn": "+34612345678",
  "country": "ES",
  "preferred_schedule": {
    "type": "specific_date",
    "preferred_porting_at": "2026-06-10T09:00:00Z"
  },
  "donor_details": {
    "account": {
      "type": "personal",
      "service_type": "prepaid",
      "iccid": "8934075500001234567"
    }
  }
}

When service_provider_id is omitted, porting resolves the donor service provider. If the lookup cannot identify the donor, the porting request will be rejected with the usual validation error and the caller may retry by supplying service_provider_id explicitly.


Summary of Changes

CapabilityChangeEndpoint / Contract
CreateDonorDetailsES.service_provider_id (ES)Now optionalPOST /portings — CreatePortingES request body