PUT /integrations/maverick/ticket-type-mappings
Update ticket type mapping
Update an existing ticket type mapping
Authentication Required
Authorization: Bearer {token}
header string This header is required to access this endpoint
Required Parameters
x-account-id
header string Account ID for the request
Request Body
{ "id": 1, "pulseTicketTypeId": "tt-abc456", "pulseCategoryEnum": "technical"}{ "id": 1, "pulseTicketTypeId": "tt-abc456", "pulseCategoryEnum": "technical"}Try it out
Loading...
Output:
Responses
Description
Mapping updated successfully
{ "data": { "id": 1, "accountId": "2311", "maverickCategoryId": 123, "maverickCategoryName": "Chargebacks", "pulseTicketTypeId": "tt-xyz123", "pulseCategoryEnum": "billing", "createdBy": "admin@example.com", "updatedBy": "admin@example.com", "createdAt": "string", "updatedAt": "string", "ticketType": { "uniqueId": "tt-xyz123", "name": "Chargeback Disputes", "description": "Handle merchant chargeback inquiries", "category": "billing", "isActive": true } }, "message": "Ticket type mapping updated successfully"}Description
Invalid request data or mapping not found
Description
Insufficient permissions (requires account admin)
References
#/components/parameters/xAccountIdHeader
in: headername: x-account-idschema: type: stringdescription: Account ID for the requestrequired: trueexample: "2311"|export type xAccountIdHeader = any; // Schema type not fully supported#/components/schemas/TicketTypeMapping
type: objectproperties: id: type: integer description: Mapping unique identifier example: 1 accountId: type: string description: Pulse account ID example: "2311" maverickCategoryId: type: integer description: Maverick category ID example: 123 maverickCategoryName: type: string description: Maverick category name example: Chargebacks pulseTicketTypeId: type: string description: Pulse ticket type unique ID example: tt-xyz123 pulseCategoryEnum: type: string description: Pulse ticket category enum: - technical - billing - account - compliance - feature_request - underwriting - general_support - general_forms - retention - activations - fee_change_forms - bank_submissions example: billing createdBy: type: string description: Email of user who created mapping example: admin@example.com updatedBy: type: string description: Email of user who last updated mapping example: admin@example.com createdAt: type: string format: date-time description: Creation timestamp updatedAt: type: string format: date-time description: Last update timestamp ticketType: type: object nullable: true description: Associated Pulse ticket type details properties: uniqueId: type: string example: tt-xyz123 name: type: string example: Chargeback Disputes description: type: string example: Handle merchant chargeback inquiries category: type: string example: billing isActive: type: boolean example: true|export interface TicketTypeMapping { /** Mapping unique identifier */ id?: number; /** Pulse account ID */ accountId?: string; /** Maverick category ID */ maverickCategoryId?: number; /** Maverick category name */ maverickCategoryName?: string; /** Pulse ticket type unique ID */ pulseTicketTypeId?: string; /** Pulse ticket category */ pulseCategoryEnum?: | "technical" | "billing" | "account" | "compliance" | "feature_request" | "underwriting" | "general_support" | "general_forms" | "retention" | "activations" | "fee_change_forms" | "bank_submissions"; /** Email of user who created mapping */ createdBy?: string; /** Email of user who last updated mapping */ updatedBy?: string; /** Creation timestamp */ createdAt?: Date; /** Last update timestamp */ updatedAt?: Date; /** Associated Pulse ticket type details */ ticketType?: { uniqueId?: string; name?: string; description?: string; category?: string; isActive?: boolean; };}Route Source Code
Check out the source code for this route entrypoint here: /integrations/maverick/ticket-type-mappings/route.ts
Or the swagger.yaml spec this documentation was generated from:
/integrations/maverick/ticket-type-mappings/swagger.yaml