> ## Documentation Index > Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get ticket > Retrieve a single ticket by ID with optional notes. The ID can be either the internal ticket ID or the PSA ticket number. ## OpenAPI ````yaml /openapi.json get /api/public/v1/tickets/{id} openapi: 3.0.3 info: title: MSPortal Public API version: 1.0.0 description: >- Public API for MSPortal - provides programmatic access to tenant data. ## Authentication All endpoints require authentication via API key passed as a Bearer token: ``` Authorization: Bearer ``` API keys can be created in the MSPortal dashboard under Settings → Integrations → API Access. **Important:** Do not include cookies in API requests. The public API uses stateless authentication only. ## Scopes API keys are granted specific scopes that determine what operations they can perform. Each endpoint documents its required scope(s). ## Rate Limiting API calls are rate limited per API key. Rate limit information is returned in response headers: - `X-RateLimit-Limit`: Maximum requests per minute - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: When the rate limit resets (ISO 8601) ## Request ID All responses include an `X-Request-Id` header for debugging and support. You can also pass your own `X-Request-Id` header to correlate requests. contact: name: MSPortal Support email: support@msportal.ai license: name: Proprietary servers: - url: https://app.msportal.ai description: Production environment security: - BearerAuth: [] tags: - name: Budgets description: >- Budget management - create, track, and forecast budgets with line items, categories, and products - name: Calendar description: Calendar and meeting management - events, participants, and meeting types - name: Companies description: Company management endpoints - name: Company Users description: Company user management - client portal contacts (read-only, paginated) - name: Compliance description: Compliance check management - runs, assigned checks, and status updates - name: Dashboards description: Dashboard management - external iframe resources and internal dashboards - name: Devices description: Device management - inventory, types, and locations - name: Goals description: Goal management - create, track, and manage goals with tasks and updates - name: NPS Surveys description: >- NPS survey management - Net Promoter Score surveys, responses, and analytics - name: Reports description: >- Report management - create, manage, and schedule reports with templates and types - name: Planner description: >- Planner item management - tasks, roadmap items, and project planning with linked goals, compliance, and projects - name: Surveys description: >- General survey management - multi-question surveys, responses, and statistics - name: Tickets description: Ticket management - view and filter tickets from PSA integrations - name: Training description: >- Training management - courses, enrollments, certificates, and progress tracking - name: Users description: Tenant user management - internal staff and team members (read-only) - name: Automation Rules description: >- Automation rule management - create, configure, and monitor automation rules with triggers, conditions, and actions - name: Analytics description: >- Analytics and reporting - company audit data, training analytics, user activity, and portfolio metrics paths: /api/public/v1/tickets/{id}: get: tags: - Tickets summary: Get ticket description: >- Retrieve a single ticket by ID with optional notes. The ID can be either the internal ticket ID or the PSA ticket number. parameters: - schema: type: string description: Ticket ID or PSA ticket number required: true description: Ticket ID or PSA ticket number name: id in: path - schema: type: boolean nullable: true default: true description: Include ticket notes required: false description: Include ticket notes name: includeNotes in: query - schema: type: number minimum: 1 maximum: 100 default: 50 description: Maximum notes to return required: false description: Maximum notes to return name: noteLimit in: query responses: '200': description: Ticket details with notes content: application/json: schema: $ref: '#/components/schemas/TicketSingleResponse' '400': description: Invalid parameters content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden - Missing required scope (tickets.read) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Ticket not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: schemas: TicketSingleResponse: type: object properties: data: $ref: '#/components/schemas/TicketDetail' required: - data ErrorResponse: type: object properties: error: type: string description: Error message requestId: type: string description: Request correlation ID details: nullable: true description: Additional error details code: type: string description: Error code required: - error TicketDetail: allOf: - $ref: '#/components/schemas/Ticket' - type: object properties: notes: type: array items: $ref: '#/components/schemas/TicketNote' description: Ticket notes/comments required: - notes Ticket: type: object properties: id: type: string description: Unique ticket identifier ticketNumber: type: string description: Human-readable ticket number title: type: string description: Ticket title/summary description: type: string nullable: true description: Ticket description companyId: type: string nullable: true description: Associated company ID companyName: type: string nullable: true description: Associated company name contactName: type: string nullable: true description: Contact name contactEmail: type: string nullable: true description: Contact email status: type: string nullable: true description: Current status isClosed: type: boolean description: Whether the ticket is closed priority: type: string nullable: true description: Priority level assignedTo: type: string nullable: true description: Assigned technician/resource boardName: type: string nullable: true description: Service board/queue name queueName: type: string nullable: true description: Queue name typeName: type: string nullable: true description: Ticket type categoryName: type: string nullable: true description: Category name issueTypeName: type: string nullable: true description: Issue type hoursBudgeted: type: number nullable: true description: Budgeted hours hoursActual: type: number nullable: true description: Actual hours worked createdAt: type: string format: date-time description: Creation timestamp (ISO 8601) updatedAt: type: string nullable: true format: date-time description: Last update timestamp (ISO 8601) daysOpen: type: number nullable: true description: Number of days the ticket has been open provider: type: string description: PSA provider (connectwise, halo, syncro, autotask) externalId: type: string nullable: true description: External ID in the PSA system source: type: string nullable: true description: Ticket source required: - id - ticketNumber - title - description - companyId - companyName - contactName - contactEmail - status - isClosed - priority - assignedTo - boardName - queueName - typeName - categoryName - issueTypeName - hoursBudgeted - hoursActual - createdAt - updatedAt - daysOpen - provider - externalId - source TicketNote: type: object properties: id: type: string description: Note identifier text: type: string description: Note content isInternal: type: boolean description: Whether this is an internal note createdAt: type: string format: date-time description: Creation timestamp (ISO 8601) createdBy: type: string nullable: true description: Name of the note creator required: - id - text - isInternal - createdAt - createdBy securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Use your API key as a Bearer token. API keys can be generated in Settings → Integrations → API Access. ````