find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/nedap-authorization-provisioning-userduties-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Nedap Authorization.provisioning.User Duties API
  version: 0.0.0
  description: 'Operations tagged authorization.provisioning.UserDuties across 2 of this provider''s published API definitions: nedap-ons-deprecated-openapi-original.json, nedap-ons-openapi-original.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api-development.ons.io
tags:
- name: authorization.provisioning.UserDuties
paths:
  /t/authorization/provisioning/users/{user_uuid}/duties:
    put:
      tags:
      - authorization.provisioning.UserDuties
      summary: This endpoint is meant to assign roles with a certain scope to a user
      description: 'Provide the complete set of all roles that should be assigned to the user. Roles should be provided together with flags to reflect the scoping policy that states what clients and/or employees should be accessible.

        As this API is idempotent, the state provided in the last call is the final state. Any roles previously assigned but not specified in the body will be revoked.

        The connector is only able to control roles which are assigned by the connector itself (identified by the connector_name and connector_source).

        The changes can be seen in the Ons Autorisatie UI if you navigate to the specific user. The added roles are listed in the role overview. All the roles added by a specific connector are marked as such.

        More explanation can be found here: https://ons-api.nl/support/Shield.html.

        This endpoint replaces PUT /users endpoint.'
      operationId: authorization.provisioning.UserDutiesAPI.update
      parameters:
      - name: user_uuid
        in: path
        description: Identifier of User to update.
        required: true
        schema:
          type: string
      requestBody:
        description: User to update
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/authorization.provisioning.UserDuties'
        required: true
      responses:
        '200':
          description: No response was specified
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/authorization.provisioning.UserDuties'
      x-cupido-common-method: true
      x-replaced-by: /v0/authorization/provisioning/users/{user_uuid}/duties
      deprecated: true
      x-deprecated-since: 19-11-2025
    servers:
    - url: https://api-development.ons.io
  /v0/authorization/provisioning/users/{user_uuid}/duties:
    put:
      tags:
      - authorization.provisioning.UserDuties
      summary: This endpoint is meant to assign roles with a certain scope to a user
      description: 'Provide the complete set of all roles that should be assigned to the user. Roles should be provided together with flags to reflect the scoping policy that states what clients and/or employees should be accessible.

        As this API is idempotent, the state provided in the last call is the final state. Any roles previously assigned but not specified in the body will be revoked.

        The connector is only able to control roles which are assigned by the connector itself (identified by the connector_name and connector_source).

        The changes can be seen in the Ons Autorisatie UI if you navigate to the specific user. The added roles are listed in the role overview. All the roles added by a specific connector are marked as such.

        More explanation can be found here: https://ons-api.nl/support/Shield.html.

        This endpoint replaces PUT /users endpoint.'
      operationId: authorization.provisioning.UserDutiesAPI.update
      parameters:
      - name: user_uuid
        in: path
        description: Identifier of User to update.
        required: true
        schema:
          type: string
      requestBody:
        description: User to update
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/authorization.provisioning.UserDuties'
        required: true
      responses:
        '200':
          description: No response was specified
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/authorization.provisioning.UserDuties'
      x-cupido-common-method: true
      x-replacement-for:
      - /t/authorization/provisioning/users/{user_uuid}/duties
    servers:
    - url: https://api-development.ons.io
components:
  schemas:
    authorization.provisioning.UserDuty:
      type: object
      properties:
        roleUuid:
          type: string
        validFrom:
          type: string
          format: date-time
        validTo:
          type: string
          format: date-time
        locationIds:
          type: array
          items:
            type: integer
            format: int32
        teamIds:
          type: array
          items:
            type: integer
            format: int32
        myself:
          type: boolean
        allEmployees:
          type: boolean
        allClients:
          type: boolean
        myPlanning:
          type: boolean
        myRoster:
          type: boolean
        myAgendaClients:
          type: boolean
        myTeams:
          type: boolean
        myLocations:
          type: boolean
        roleScope:
          type: boolean
        employeesOnMyRoster:
          type: boolean
        clientEmployeeRelationTypeIds:
          type: array
          items:
            type: integer
            format: int32
      description: "Duty is a role assigned to the user. It consists of roleUuid, the validity timeline, and scoping policy options, determining what clients and/or employees will be accessible in the context of that role.\n Options myTeams, myLocations, and roleScope are only available within the pilot for the new scoping system."
      example:
        roleUuid: ea9e0f20-2232-4087-9a43-8f894e79b6f0
        validFrom: '2018-03-01T00:00:00.000+01:00'
        validTo: '2019-03-01T00:00:00.000+01:00'
        locationIds:
        - 1
        - 2
        - 3
        teamIds:
        - 4
        - 5
        - 6
        myself: true
        allEmployees: true
        allClients: false
        myPlanning: true
        myRoster: true
        myAgendaClients: true
        myTeams: true
        myLocations: true
        roleScope: true
        employeesOnMyRoster: true
        clientEmployeeRelationTypeIds:
        - 7
        - 8
        - 9
    authorization.provisioning.UserDuties:
      type: object
      properties:
        userUuid:
          type: string
          x-cupido-id: true
        source:
          type: string
        duties:
          type: array
          items:
            $ref: '#/components/schemas/authorization.provisioning.UserDuty'
      description: ''
      example:
        userUuid: 1b9243a9-83b5-4edf-ab93-507f88fdcb01
        source: Koppelingnaam
        duties:
        - roleUuid: ea9e0f20-2232-4087-9a43-8f894e79b6f0
          validFrom: '2018-03-01T00:00:00.000+01:00'
          validTo: '2019-03-01T00:00:00.000+01:00'
          locationIds:
          - 1
          - 2
          - 3
          teamIds:
          - 4
          - 5
          - 6
          myself: true
          allEmployees: true
          allClients: false
          myPlanning: true
          myRoster: true
          myAgendaClients: true
          myTeams: true
          myLocations: true
          roleScope: true
          employeesOnMyRoster: true
          clientEmployeeRelationTypeIds:
          - 7
          - 8
          - 9
x-refined-from:
- nedap-ons-deprecated-openapi-original.json
- nedap-ons-openapi-original.json