Skip to content
This repository was archived by the owner on Mar 30, 2026. It is now read-only.
This repository was archived by the owner on Mar 30, 2026. It is now read-only.

ENP Legacy V2 SMS Request Model Differs from Notification API #367

@keisterj-oddball

Description

@keisterj-oddball

User Story - Business Need

  • Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a
I want
So that

Additional Info and Resources

In ENP, the V2 SMS route request model has an optional sending_method property as part of the personalisation object when including an attachment. Notification-API only allows the file and filename properties.

Acceptance Criteria

  • This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

Potential Dependencies

Metadata

Metadata

Assignees

No one assigned

    Labels

    NotifyBoard triggerReady for ReviewsReady for reviews in preparation for Refinement.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions