> ## Documentation Index > Fetch the complete documentation index at: https://developers.gonitro.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List document groups > Lists the document groups that packages and documents can be assigned to, returning each group's name and code. There is always at least one document group - "My Documents" (the name may differ) with code `00001`. This group is special: documents in it are only visible to the WebPortal user who uploaded them. For documents uploaded through the API, that is the user whose email address was supplied as the package **Initiator**. The `Code` field is a string. Its value may look numeric, but any leading zeroes are part of the value and must be preserved. ## OpenAPI ````yaml /nsev/api-reference/openapi.yaml get /documentGroups openapi: 3.0.0 info: title: NSEV WebPortal API version: 4.0.0 contact: name: NSEV Support Team url: https://connectivegroup.my.site.com/s/contactsupport?language=en_US description: > **Nitro Sign Enterprise Verified (NSEV) WebPortal API Version 4** A comprehensive digital signing API that enables secure document signing workflows. This API provides endpoints for managing packages, documents, elements, stakeholders, and signing processes within the NSEV platform. ## Authentication This API supports multiple authentication methods: ### Basic Authentication Traditional HTTP Basic Authentication using username and password. ### OAuth 2.0 **Client Credentials Flow (Machine-to-Machine)** - Full API access including administrative endpoints - Ideal for server-to-server integrations **Authorization Code Flow (User-based)** - Limited API access excluding administrative endpoints - Ideal for user-facing applications - Supports delegated user access scenarios ## API Variants This specification is available in two variants: - **Full API**: Complete API with all endpoints (BasicAuth + OAuth2 M2M) - **User API**: Limited API excluding admin endpoints (OAuth2 user-based only) Administrative endpoints (`/poisonqueue`, `/absenceperiods`, `/auditproofs`) are restricted to machine-to-machine authentication only. ## Versioning This API follows semantic versioning principles. Major version changes may introduce breaking changes, while minor and patch versions maintain backwards compatibility. servers: - url: '{baseUrl}/esig/webportalapi/v4' variables: baseUrl: default: https://your-tenant.sign.gonitro.com description: >- Your tenant-specific base URL, including scheme and host (e.g. https://acme.sign.gonitro.com). Each NSEV customer has a unique URL. Replace this with yours before sending a request. The esig path segment is required - the Web Application Firewall routes requests on it. security: - basicAuth: [] - bearerAuth: [] tags: - name: Configuration description: | Endpoints for retrieving system configuration settings, contact groups, templates and signing methods. - name: Packages description: | Core endpoints for creating, managing, and tracking packages throughout their lifecycle. - name: Documents description: | Endpoints for adding, removing, and managing documents within packages. Handles document upload, processing, and metadata management. - name: Elements description: | Endpoints for managing elements (fields) within documents, including signatures and other form elements. - name: Stakeholders description: | Endpoints for managing stakeholders (recipients) associated with packages and their roles in the package workflow. - name: Actors description: | Endpoints for managing individual actors within stakeholders, including their contact information and role preferences: Approver, FormFiller, Signer or Receiver - name: Process description: | Endpoints for managing the package process workflow, including process steps, parallel actions, and workflow orchestration. - name: AuditTrails description: | Modern endpoints for retrieving comprehensive audit trails as signed PDFs, verifying the integrity of audit trail data and retrieving audit events. - name: BulkActions description: | Endpoints for performing and managing bulk actions on multiple packages. - name: Users description: | Endpoints for managing user accounts, including user invitations. - name: AbsencePeriods description: | Administrative endpoints for managing user absence periods and delegation settings during out-of-office scenarios. **Access Level**: Machine-to-machine only (administrative access required) paths: /documentGroups: get: tags: - Configuration summary: List document groups description: >- Lists the document groups that packages and documents can be assigned to, returning each group's name and code. There is always at least one document group - "My Documents" (the name may differ) with code `00001`. This group is special: documents in it are only visible to the WebPortal user who uploaded them. For documents uploaded through the API, that is the user whose email address was supplied as the package **Initiator**. The `Code` field is a string. Its value may look numeric, but any leading zeroes are part of the value and must be preserved. operationId: listDocumentGroups parameters: - name: name description: The document group name (or part) to search for in: query required: false schema: type: string responses: '200': description: OK content: application/json: schema: description: Response for a list of document groups type: object properties: DocumentGroups: type: array description: The list of document groups items: description: Response for a document group type: object properties: Code: type: string description: The code of the document group Name: type: string description: The name of the document group examples: document-groups: summary: OK value: DocumentGroups: - Code: '00001' Name: My Documents - Code: '00007' Name: Contracts '401': $ref: '#/components/responses/UnAuthorized' components: responses: UnAuthorized: description: Caller is unauthorized to perform this operation securitySchemes: basicAuth: type: http scheme: basic bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > Bearer token authentication using JSON Web Tokens (JWT) or opaque tokens. **Usage**: Send the access token in the Authorization header: ``` Authorization: Bearer ``` ````