[VIBE-367] Third Party subscription Fulfilment - Current

[linusnorton]

Migrated from VIBE-367

PROBLEM STATEMENT

Third Party users can subscribe to receive publications from CaTH. This ticket covers the Third Party Subscription fulfilment process.

 

AS A CaTH Third Party Subscriber 

I WANT to receive email notifications when hearing lists I’m subscribed to in CaTH are published

SO THAT I am aware when a new hearing list is published

AND can download a copy of this list

 

Pre-Condition

• A list of third parties with matched list types and sensitivity have been created in the account management system
• CaTH Third Party users can subscribe to receive specific hearing lists published in CaTH
• A new endpoint has been established from account-management to receive the list of subscribed third parties to notified

 

ACCEPTANCE CRITERIA

• When a CaTH Third Party user subscribes to publications in CaTH and a publication matching the users' subscriptions is uploaded to CaTH, the system fulfils the subscription by identifying the Third Party User ID subscribed to that publication and the channel/API to send the email notification to from the account management system. 
• The system retrieves the publication metadata from the data management system and sends the file in JSON format to the Third Party using the POST endpoint
• The system should push the file to the third party their API (P&I push) using the third party authorisation certificate
• An acknowledgment receipt should be issued in the form of a HTTP status return 
• Third Party Subscribers are notified when publications are uploaded, updated or manually deleted before expiry, using the correct status code
• Successful <**POST**>(https://hmcts.github.io/restful~~api~~standards/#post) requests will generate:
  ** 200 (if resources have been updated)
  ** 201 (if resources have been created)
  ** 202 (if the request was accepted but has not been finished yet)
  *** 204 with <**Location*>(https://tools.ietf.org/html/rfc7231#section-7.1.2) header (if the actual resource is not returned)
• Validation is established to ensure no publication is sent when the trigger has not been activated, to ensure that Non-subscribed JSON payload is not sent to the third party and to ensure that the system differentiates between newly uploaded and updated publication 
• Integration test and Unit test are performed 

---

Original JIRA Metadata

• Status: New
• Priority: 3-Medium
• Issue Type: Story
• Assignee: Unassigned
• Created: 1/22/2026
• Updated: 1/23/2026
• Original Labels: CaTH, tech-refinement