Publisert - 19.11.2026

PTS Registry API - Release Notes

All notable changes to the PTS Registry API will be documented in this file.

Subscribe to notifications on #ext-utv-pts on Slack to be notified when we announce new releases.

You'll also notice we often use icons to visualize our changes and their effect, but we've limited ourselves to the following;

  • 🌱 New Feature
  • πŸƒ Improvement
  • πŸ”§ Bug Fix
  • πŸ’₯ Breaking Change
  • πŸ”’ Security

Only changes that reach a public surface are listed.

1.0.6

dev test prod

  • πŸ’₯ The subject's identifier is now value, as in every other reference to a person: { "system": …, "value": … }.
  • πŸ’₯ create answers 201 Created, not 200 OK.
  • πŸ’₯ A restriction no longer carries links. They held only a self path, and may come back as a proper addition.
  • πŸ’₯ query is paged like GET /api/v1/restrictions: it answers at most pageSize restrictions (5 to 500, default 25) and a next while there are more. Send next back as cursor, with the same subject.
  • πŸ’₯ The OpenAPI document now states what is accepted, so generated clients change. resource is required on create and revoke, resource.value is required on create, and provision.system lists 9604 only. revoke's resource is its own schema, RestrictionResourceSelectorDto, whose value stays optional. The API accepts exactly what it did.
  • πŸ’₯ A property the API doesn't know is rejected with 400, as is a number where an enum's name is expected. Both were accepted before.
  • πŸ’₯ A subject, a person actor and the person asking in resolve must be 11 digits under their own system: a personnummer (first digit 0 to 3) or a D-nummer (first digit 4 to 7).
  • πŸ’₯ create answers 409 for a subject number the person no longer uses, and for a subject dead more than 31 days, or marked dead with no date of death. revoke is allowed on both.
  • πŸ’₯ One create naming the same practitioner by D-nummer and by personnummer is refused as a duplicate actor.
  • πŸ’₯ Statuses: a subject or person actor nobody owns is 400 (was 404). A value that may not follow the one in force, and a revoke with nothing in force, are 409 (were 400). A failed lookup in a service we depend on is always 500 (was 403, 400 or 409). 404 is only for GET /api/v1/restrictions/{restrictionId}.
  • 🌱 The subject gains name, alongside dateOfBirth and identifiers. identifiers holds the personnummer and D-nummer the person has now, retired ones included, sorted by system, then value, and so does a person actor's. A number nobody owns is shown by itself, with no name or date of birth.
  • 🌱 A revoke of what is already revoked answers 409, apart from one with nothing in force.
  • πŸƒ A restriction is stored on the personnummer or D-nummer you send, and read across every number its owner has: a restriction set through someone's D-nummer is in force through their personnummer too. compact, resolve and every response combine them.
  • πŸƒ A person actor stands for its owner, so a revoke naming a practitioner by either number ends a restriction naming them by the other. revoke needs something in force across the owner, and appends its revocation on the number sent.
  • πŸƒ A write is judged again against what is in force when it lands. One that collides with a concurrent change to the same person answers 409, as does one whose rule fails because what it would follow has changed.
  • πŸ”§ resolve no longer lets a revoked restriction hide the active one beneath it: revoking a restriction named at the subject no longer lifts a restriction named at a capacity the subject holds.
  • πŸ”§ resolve returns a restriction covering the whole domain for a question about a type or a resource in it. PVK's PPS-SPERRE-HARD is written that way, and was missing from those answers.

1.0.5

dev test prod

  • πŸ’₯ A restriction carries at most one period. conditions.periods is now conditions.period.
  • πŸ’₯ Removed the rule that periods must not overlap, and the limit of twenty periods per restriction.

1.0.4

dev date test prod

  • πŸ’₯ The two models inside a resolution are now named RestrictionResolutionPersonActorDto and RestrictionResolutionCapacityActorDto, so the generated OpenAPI schema names match the code rather than reading RestrictionActorDtoRestrictionPersonActorDto.

1.0.3

dev date test prod

  • πŸ’₯ resolve requires a domain and a resource type alongside a resource identifier.
  • πŸ’₯ Removed breadth from the API. How much a restriction covers is derived from the domain and resource it names, and writing one too wide is refused with a 400.
  • πŸ’₯ Removed the last of the target vocabulary, flattening the snapshot compact returns.

1.0.2

dev date test prod

  • πŸ’₯ Replaced appliesTo with a reach, and allowed a provision to reach the descendants of a resource rather than only the resource itself.
  • πŸ’₯ Flattened the domain and the resource out of the wrapped target and onto the restriction itself, and collapsed the polymorphic provision class.
  • πŸ’₯ A resource is optional, so a restriction may cover a whole domain or a whole resource type.
  • πŸ’₯ Breadth is permitted per code system, so 9603 and 9604 differ in how wide they may be written.
  • πŸ’₯ Replaced DiagnosticReport with ServiceRequest throughout.
  • πŸ’₯ Removed the parts of the API surface that existed only to fit 9603.

1.0.1

dev date test prod

  • πŸ’₯ Every restriction target carries a domain and a resource type.
  • πŸ’₯ Replaced directives with provisions.
  • πŸ’₯ revoke takes a provision selector, so it names which provision is being lifted.
  • πŸ’₯ Conditions may carry a duration, for a provision whose window is counted from a resource that does not exist yet.
  • πŸ’₯ The subject's date of birth travels with a restriction, taken from Pts.Person.Api, replacing the age windows this registry used to compute. The age threshold belongs to Helsedirektoratet, not here.
  • πŸ’₯ Added appliesTo to say how far a restriction reaches.
  • πŸ’₯ Removed the supersession ordinal from every public surface.

1.0.0

dev date test prod

The first version the service reported.

It was reached without any released predecessor, so this section describes the surface rather than a set of changes.

  • πŸ’₯ /api/v1/restrictions with create, query, compact, resolve and revoke, plus a cursor-paged list and a get-by-id.
  • πŸ’₯ Restrictions are the aggregate root, with the subject embedded, and provision values are strongly typed and polymorphic.
  • πŸ’₯ compact returns what is in force per resource and code system; resolve answers for one actor.
  • πŸ’₯ HelseID with DPoP, and CORS for the developer portal.

SΓΈk i Utviklerportalen

SΓΈket er fullfΓΈrt!