Create regulation

Creates a new regulation.

Note: This endpoint requires a user-scoped OAuth token. A pure client_credentials token without user context will be rejected. The treating user is automatically derived from the token and cannot be set manually.

Request

POST /api/oauth/v2/resource/regulations

Header

Header	Value
Authorization	Bearer {access_token}
Content-Type	application/json

Body parameters

Field	Type	Required	Description
customerUuid	string	Yes	UUID of the assigned customer (must belong to the token's company)
services	string	No	Prescribed services
diagnose	string	No	Diagnosis (ICD code or free text)
receiverName	string	No	Name of the receiving party
receiverStreet	string	No	Street of the receiving party
receiverZip	string	No	Postal code of the receiving party
receiverCity	string	No	City of the receiving party
date	string	No	Issue date (YYYY-MM-DD, default: today)
printed	boolean	No	Whether the regulation has been printed

Response

Success (201 Created)

{
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "services": "Physiotherapy, Occupational therapy",
    "diagnose": "M54.5",
    "receiverName": "Dr. Klaus Berger",
    "receiverStreet": "Landstraße 12",
    "receiverZip": "4020",
    "receiverCity": "Linz",
    "date": "2026-06-09",
    "printed": false,
    "customer": {
      "id": "f0e1d2c3-b4a5-6789-fedc-ba9876543210",
      "firstName": "Anna",
      "lastName": "Muster"
    },
    "treatingUser": {
      "id": "c3d4e5f6-a7b8-9012-cdef-123456789012",
      "firstName": "Dr. Maria",
      "lastName": "Huber"
    }
  }
}

Response fields

See Get regulation for the full field description.

Beispiele

bash

curl -X POST "https://my.offisy.at/api/oauth/v2/resource/regulations" \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "customerUuid": "b2c3d4e5-f6a7-8901-bcde-f01234567890",
    "services": "beispiel",
    "diagnose": "beispiel",
    "receiverName": "Muster GmbH",
    "receiverStreet": "Musterstraße 1",
    "receiverZip": "4020",
    "receiverCity": "Linz",
    "date": "2026-04-15T10:00:00",
    "printed": "beispiel"
  }'

Server

Client-ID

Client-Secret

Parameter

customerUuid *string

services string

diagnose string

receiverName string

receiverStreet string

receiverZip string

receiverCity string

date string

printed boolean

Zuerst Token anfordern

Possible errors

Status	Code	Description
400	validation_error	Invalid request data (e.g. customerUuid missing)
401	invalid_client	Invalid or missing access token
403	insufficient_scope	Scope medicals not present
404	not_found	Customer not found