---
title: "Get port-in fields JSON Schema"
method: GET
path: "/v1/port-ins/fields/{countryCode}/schema"
tags: ["Port-Ins"]
---

# Get port-in fields JSON Schema

`GET /v1/port-ins/fields/{countryCode}/schema`

## Request

- Base URL: `https://api.telgea.com`
- URL: `https://api.telgea.com/v1/port-ins/fields/{countryCode}/schema`
- Auth: API key in header `x-api-key`

Retrieves JSON Schema definitions for port-in fields, keyed by port-in type. Use these schemas for client-side validation of port-in form data before submission.

Each key in the response corresponds to a port-in type (e.g., "personal", "business"), and the value is a standard JSON Schema object that can be used with any JSON Schema validator.

A type whose market declares transfer dates also carries `$defs.executionDate`: check the port-in's `executionDate` against it. Its dates hold until the `executionDate.validUntil` the fields endpoint returns; fetch the schema again after it. Nothing in the schema's `properties` refers to it, so the schema validates `fields` alone.

## Path parameters

- `countryCode` string, required: ISO 3166-1 alpha-2 country code (e.g., "DK", "US", "GB")

## Response `200`

Successfully retrieved JSON Schema definitions for port-in fields.

- GetPortInFieldsSchemaResponse

## Other responses

- `400`: The countryCode is not a valid ISO 3166-1 alpha-2 code. Valid codes look like DK, US, GB or FR.
- `401`: Missing or invalid API key in the X-API-Key header
- `403`: Insufficient permissions to read port-in data
- `429`: The API key has used its request quota for the current window. `Retry-After` says how many seconds until it resets.
- `500`: Internal server error. Contact support if this persists.

---

[API](https://skmtc.dev/telgea/apis/telgea-api.md) - [All operations](https://skmtc.dev/telgea/apis/telgea-api/llms.txt) - [OpenAPI document](https://skmtc.dev/telgea/apis/telgea-api/revisions/4e8f8c04fe9e?raw)