API Reference: Topics endpoints

• GET /api/Topics – Bearer JWT (TicketAccessOrPhoneAuth)
  List topics with pagination and sorting. Optional query channelId limits results to topics allowed for that channel; phone-auth requests use the token channel.
• GET /api/Topics/{id} – Bearer JWT (TicketAccessOrPhoneAuth)
  Read one topic. Optional channelId applies the same channel allow-list and returns 404 when the topic is not allowed for that channel.
• POST /api/Topics – Bearer JWT (ManageSettings)
  Create one topic. The server sets customer scope and validates phone model overrides before saving.
• PUT /api/Topics/{id} – Bearer JWT (ManageSettings)
  Update topic name, description and phone settings. Legacy customFieldRequirements input is ignored because requirements are now derived from linked documents.
• DELETE /api/Topics/{id} – Bearer JWT (ManageSettings)
  Delete one owned topic. Returns 204 on success or 404 when the topic is missing.

• GET /api/TopicChannels – Bearer JWT (ManageSettings)
  List topic-channel relevance links. Query supports topicId, channelId, pageNumber, pageSize, sortBy and sortOrder. pageNumber is normalized and pageSize is clamped to 1-100.
• GET /api/TopicChannels/{id} – Bearer JWT (ManageSettings)
  Read one topic-channel link in the authenticated customer scope.
• POST /api/TopicChannels – Bearer JWT (ManageSettings)
  Create one default relevance link between a topic and either a concrete channel or a special channel type. Duplicate combinations return 409 Conflict.
• POST /api/TopicChannels/bulk – Bearer JWT (ManageSettings)
  Create multiple topic-channel links. Duplicate input rows and already existing combinations are skipped by the service.
• DELETE /api/TopicChannels/{id} – Bearer JWT (ManageSettings)
  Delete one topic-channel relevance link.
• DELETE /api/TopicChannels/bulk – Bearer JWT (ManageSettings)
  Delete multiple topic-channel links. The request body is an array of TopicChannelID values; an empty body returns 400.

• GET /api/TopicActions – Bearer JWT
  List topic-action links. Filters include topicId, actionId, hookName, channelId, isActive, pagination and sorting.
• GET /api/TopicActions/{id} – Bearer JWT
  Read one topic-action link with resolved topic, action and channel names.
• POST /api/TopicActions – Bearer JWT
  Create one topic-action link. Use actionID for the reusable action definition and priority for execution order.
• POST /api/TopicActions/bulk – Bearer JWT
  Create multiple topic-action links. Existing matching combinations are skipped.
• PUT /api/TopicActions/{id} – Bearer JWT
  Update only the priority field of an existing link.
• DELETE /api/TopicActions/{id} – Bearer JWT
  Delete one topic-action link.

• GET /api/TopicDocuments – Bearer JWT
  List topic-document links. Filters include topicId, documentId, channelId, hookName, isHook, pagination and sorting.
• GET /api/TopicDocuments/{id} – Bearer JWT
  Read one topic-document link scoped to the authenticated customer.
• POST /api/TopicDocuments – Bearer JWT
  Create one link between a document and a topic, special topic, channel or special channel. Duplicate combinations return 409 Conflict.
• POST /api/TopicDocuments/bulk – Bearer JWT
  Create multiple topic-document links. Current bulk create returns a server error if the database rejects duplicate combinations.
• PUT /api/TopicDocuments/{id} – Bearer JWT
  Update document, topic/special topic and channel/special channel fields for one link.
• DELETE /api/TopicDocuments/{id} – Bearer JWT
  Delete one topic-document link.

• GET /api/PageTopicMappings – Bearer JWT
  List URL-to-topic mappings with the shared pagination parameters.
• GET /api/PageTopicMappings/{id} – Bearer JWT
  Read one page-topic mapping in the authenticated customer scope.
• POST /api/PageTopicMappings – Bearer JWT
  Create one mapping from a URL pattern and path scope to a topic or special topic. The server stores creator and creation timestamp.
• PUT /api/PageTopicMappings/{id} – Bearer JWT
  Update URL pattern, match type, path scope, topic/special topic and channel scope. The server stores last-modified metadata.
• DELETE /api/PageTopicMappings/{id} – Bearer JWT
  Delete one page-topic mapping.

• POST /api/ConditionalRules/from-text – Bearer JWT
  Related automation helper. Converts a natural-language instruction into JSON conditional rules. The authenticated customer must have an OpenAI API key configured.

Protected AnswerPal API endpoints use JWT Bearer authentication. The topic list/detail routes can also accept phone-auth context through TicketAccessOrPhoneAuth; settings routes require ManageSettings.

• List routes return PaginatedResult<T> with items, totalCount and totalPages.
• Successful create routes usually return 201 Created or 200 OK for bulk creates. Successful update and delete routes usually return 204 No Content.
• 400 is used for validation errors, 403 for forbidden phone-auth/channel mismatches, 404 for missing or inaccessible resources and 409 for duplicate single-link creates where the API handles conflicts.
• Phone-auth topic reads are bound to the token channel. Supplying a different channelId returns 403.