diff --git a/Bandwidth.Standard.sln b/Bandwidth.Standard.sln index 28da61d..fd270c0 100644 --- a/Bandwidth.Standard.sln +++ b/Bandwidth.Standard.sln @@ -2,7 +2,7 @@ Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 14 VisualStudioVersion = 14.0.25420.1 MinimumVisualStudioVersion = 10.0.40219.1 -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard", "src\Bandwidth.Standard\Bandwidth.Standard.csproj", "{B644B02A-2DAC-42EA-A361-EB14EAD13209}" +Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard", "src\Bandwidth.Standard\Bandwidth.Standard.csproj", "{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}" EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard.Test", "src\Bandwidth.Standard.Test\Bandwidth.Standard.Test.csproj", "{19F1DEBC-DE5E-4517-8062-F000CD499087}" EndProject @@ -12,10 +12,10 @@ Global Release|Any CPU = Release|Any CPU EndGlobalSection GlobalSection(ProjectConfigurationPlatforms) = postSolution - {B644B02A-2DAC-42EA-A361-EB14EAD13209}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {B644B02A-2DAC-42EA-A361-EB14EAD13209}.Debug|Any CPU.Build.0 = Debug|Any CPU - {B644B02A-2DAC-42EA-A361-EB14EAD13209}.Release|Any CPU.ActiveCfg = Release|Any CPU - {B644B02A-2DAC-42EA-A361-EB14EAD13209}.Release|Any CPU.Build.0 = Release|Any CPU + {FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Debug|Any CPU.ActiveCfg = Debug|Any CPU + {FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Debug|Any CPU.Build.0 = Debug|Any CPU + {FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Release|Any CPU.ActiveCfg = Release|Any CPU + {FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Release|Any CPU.Build.0 = Release|Any CPU {19F1DEBC-DE5E-4517-8062-F000CD499087}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {19F1DEBC-DE5E-4517-8062-F000CD499087}.Debug|Any CPU.Build.0 = Debug|Any CPU {19F1DEBC-DE5E-4517-8062-F000CD499087}.Release|Any CPU.ActiveCfg = Release|Any CPU diff --git a/api/openapi.yaml b/api/openapi.yaml index 30acc9a..9092b13 100644 --- a/api/openapi.yaml +++ b/api/openapi.yaml @@ -6361,6 +6361,8 @@ components: examples: messageSendingCallback: $ref: '#/components/examples/messageSendingCallbackExample' + messageSentCallback: + $ref: '#/components/examples/messageSentCallbackExample' smsMessageDeliveredCallback: $ref: '#/components/examples/smsMessageDeliveredCallbackExample' mmsMessageDeliveredCallback: @@ -6374,7 +6376,7 @@ components: description: |-

This Outbound Message Webhook is an envelope containing status information regarding a message sent (MT) from your message-enabled Bandwidth telephone number. -

The payload type will be one of message-sending, message-delivered, message-failed or message-read. +

The payload type will be one of message-sending, message-sent, message-delivered, message-failed or message-read.

Note that message-read callbacks are pertinent only for RBM messages sent from the /messages/multiChannel endpoint.

Please visit Webhooks

required: true @@ -6554,12 +6556,33 @@ components: media: - https://dev.bandwidth.com/images/bandwidth-logo.png tag: your tag here + messageSentCallbackExample: + summary: An example of a message-sent callback body. + value: + time: 2024-06-25T18:42:36.979456Z + type: message-sent + to: "+15554443333" + description: Message sent to carrier + message: + id: 1593110555875xo7watq5px6rbe5d + owner: "+15552221111" + applicationId: cfd4fb83-7531-4acc-b471-42d0bb76a65c + time: 2024-06-25T18:42:35.876906Z + segmentCount: 1 + direction: out + to: + - "+15554443333" + from: "+15552221111" + text: "" + media: + - https://dev.bandwidth.com/images/bandwidth-logo.png + tag: v2 lab smsMessageDeliveredCallbackExample: summary: An example of a sms message-delivered callback body. value: type: message-delivered time: 2024-09-14T18:20:11.160744Z - description: Message delivered to carrier. + description: Message delivered to handset. to: "+12345678902" message: id: 14762070468292kw2fuqty55yp2b2 @@ -6577,7 +6600,7 @@ components: value: type: message-delivered time: 2024-09-14T18:20:24.160544Z - description: Message delivered to carrier. + description: Message delivered to handset. to: "+12345678902" message: id: 14762070468292kw2fuqty55yp2b2 @@ -6597,7 +6620,7 @@ components: value: type: message-delivered time: 2024-09-14T18:20:17.160544Z - description: Message delivered to carrier. + description: Message delivered to handset. to: "+12345678902" message: id: 14762070468292kw2fuqty55yp2b2 @@ -10567,7 +10590,7 @@ components: type: string description: description: A detailed description of the event described by the callback. - example: Message delivered to carrier. + example: Message delivered to handset. type: string message: $ref: '#/components/schemas/statusCallbackMessage' @@ -10628,11 +10651,13 @@ components: description: |- The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - - `message-delivered` indicates that the message was successfully sent. + - `message-sent` indicates that the message has left the Bandwidth network and is in transit to the provider. + - `message-delivered` indicates that the message was successfully delivered to handset. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. enum: - message-sending + - message-sent - message-delivered - message-failed - message-read diff --git a/bandwidth.yml b/bandwidth.yml index fd39c5c..52ceffd 100644 --- a/bandwidth.yml +++ b/bandwidth.yml @@ -2962,7 +2962,7 @@ components: description: type: string description: A detailed description of the event described by the callback. - example: Message delivered to carrier. + example: Message delivered to handset. message: $ref: '#/components/schemas/statusCallbackMessage' errorCode: @@ -3018,7 +3018,11 @@ components: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - - `message-delivered` indicates that the message was successfully sent. + - `message-sent` indicates that the message has left the Bandwidth + network and is in transit to the provider. + + - `message-delivered` indicates that the message was successfully + delivered to handset. - `message-failed` indicates that the message could not be sent to the intended recipient. @@ -3027,6 +3031,7 @@ components: recipient. enum: - message-sending + - message-sent - message-delivered - message-failed - message-read @@ -8712,12 +8717,33 @@ components: media: - https://dev.bandwidth.com/images/bandwidth-logo.png tag: your tag here + messageSentCallbackExample: + summary: An example of a message-sent callback body. + value: + time: '2024-06-25T18:42:36.979456Z' + type: message-sent + to: '+15554443333' + description: Message sent to carrier + message: + id: 1593110555875xo7watq5px6rbe5d + owner: '+15552221111' + applicationId: cfd4fb83-7531-4acc-b471-42d0bb76a65c + time: '2024-06-25T18:42:35.876906Z' + segmentCount: 1 + direction: out + to: + - '+15554443333' + from: '+15552221111' + text: '' + media: + - https://dev.bandwidth.com/images/bandwidth-logo.png + tag: v2 lab smsMessageDeliveredCallbackExample: summary: An example of a sms message-delivered callback body. value: type: message-delivered time: '2024-09-14T18:20:11.160744Z' - description: Message delivered to carrier. + description: Message delivered to handset. to: '+12345678902' message: id: 14762070468292kw2fuqty55yp2b2 @@ -8735,7 +8761,7 @@ components: value: type: message-delivered time: '2024-09-14T18:20:24.160544Z' - description: Message delivered to carrier. + description: Message delivered to handset. to: '+12345678902' message: id: 14762070468292kw2fuqty55yp2b2 @@ -8755,7 +8781,7 @@ components: value: type: message-delivered time: '2024-09-14T18:20:17.160544Z' - description: Message delivered to carrier. + description: Message delivered to handset. to: '+12345678902' message: id: 14762070468292kw2fuqty55yp2b2 @@ -9787,7 +9813,7 @@ components: information regarding a message sent (MT) from your message-enabled Bandwidth telephone number. -

The payload type will be one of message-sending, message-delivered, message-failed or message-read. +

The payload type will be one of message-sending, message-sent, message-delivered, message-failed or message-read.

Note that message-read callbacks are pertinent only for RBM messages sent from the /messages/multiChannel endpoint.

Please visit Webhooks

@@ -9798,6 +9824,8 @@ components: examples: messageSendingCallback: $ref: '#/components/examples/messageSendingCallbackExample' + messageSentCallback: + $ref: '#/components/examples/messageSentCallbackExample' smsMessageDeliveredCallback: $ref: '#/components/examples/smsMessageDeliveredCallbackExample' mmsMessageDeliveredCallback: diff --git a/docs/StatusCallbackTypeEnum.md b/docs/StatusCallbackTypeEnum.md index bbd2c88..3acb3d0 100644 --- a/docs/StatusCallbackTypeEnum.md +++ b/docs/StatusCallbackTypeEnum.md @@ -1,5 +1,5 @@ # Bandwidth.Standard.Model.StatusCallbackTypeEnum -The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-delivered` indicates that the message was successfully sent. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. +The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-sent` indicates that the message has left the Bandwidth network and is in transit to the provider. - `message-delivered` indicates that the message was successfully delivered to handset. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. ## Properties diff --git a/src/Bandwidth.Standard/Model/RbmActionBase.cs b/src/Bandwidth.Standard/Model/RbmActionBase.cs index c622267..e1c2586 100644 --- a/src/Bandwidth.Standard/Model/RbmActionBase.cs +++ b/src/Bandwidth.Standard/Model/RbmActionBase.cs @@ -78,7 +78,7 @@ protected RbmActionBase() { } /// Base64 payload the customer receives when the reply is clicked. /// /// Base64 payload the customer receives when the reply is clicked. - /// [B@2041c9a3 + /// [B@50841932 [DataMember(Name = "postbackData", IsRequired = true, EmitDefaultValue = true)] public byte[] PostbackData { get; set; } diff --git a/src/Bandwidth.Standard/Model/RbmSuggestionResponse.cs b/src/Bandwidth.Standard/Model/RbmSuggestionResponse.cs index b443fb9..8b7047a 100644 --- a/src/Bandwidth.Standard/Model/RbmSuggestionResponse.cs +++ b/src/Bandwidth.Standard/Model/RbmSuggestionResponse.cs @@ -57,7 +57,7 @@ public partial class RbmSuggestionResponse : IValidatableObject /// Base64 payload the customer receives when the reply is clicked. /// /// Base64 payload the customer receives when the reply is clicked. - /// [B@2041c9a3 + /// [B@50841932 [DataMember(Name = "postbackData", EmitDefaultValue = false)] public byte[] PostbackData { get; set; } diff --git a/src/Bandwidth.Standard/Model/StatusCallback.cs b/src/Bandwidth.Standard/Model/StatusCallback.cs index 0c08f5c..bff063c 100644 --- a/src/Bandwidth.Standard/Model/StatusCallback.cs +++ b/src/Bandwidth.Standard/Model/StatusCallback.cs @@ -108,7 +108,7 @@ protected StatusCallback() { } /// A detailed description of the event described by the callback. /// /// A detailed description of the event described by the callback. - /// Message delivered to carrier. + /// Message delivered to handset. [DataMember(Name = "description", IsRequired = true, EmitDefaultValue = true)] public string Description { get; set; } diff --git a/src/Bandwidth.Standard/Model/StatusCallbackTypeEnum.cs b/src/Bandwidth.Standard/Model/StatusCallbackTypeEnum.cs index 325e4a3..663c2a9 100644 --- a/src/Bandwidth.Standard/Model/StatusCallbackTypeEnum.cs +++ b/src/Bandwidth.Standard/Model/StatusCallbackTypeEnum.cs @@ -27,9 +27,9 @@ namespace Bandwidth.Standard.Model { /// - /// The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-delivered` indicates that the message was successfully sent. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. + /// The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-sent` indicates that the message has left the Bandwidth network and is in transit to the provider. - `message-delivered` indicates that the message was successfully delivered to handset. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. /// - /// The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-delivered` indicates that the message was successfully sent. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. + /// The possible status callbacks when sending an MT SMS or MMS or RBM message: - `message-sending` indicates that Bandwidth is sending the message to the upstream provider. - `message-sent` indicates that the message has left the Bandwidth network and is in transit to the provider. - `message-delivered` indicates that the message was successfully delivered to handset. - `message-failed` indicates that the message could not be sent to the intended recipient. - `message-read` indicates that the RBM message was read by the recipient. [JsonConverter(typeof(StringEnumConverter))] public enum StatusCallbackTypeEnum { @@ -39,23 +39,29 @@ public enum StatusCallbackTypeEnum [EnumMember(Value = "message-sending")] Sending = 1, + /// + /// Enum Sent for value: message-sent + /// + [EnumMember(Value = "message-sent")] + Sent = 2, + /// /// Enum Delivered for value: message-delivered /// [EnumMember(Value = "message-delivered")] - Delivered = 2, + Delivered = 3, /// /// Enum Failed for value: message-failed /// [EnumMember(Value = "message-failed")] - Failed = 3, + Failed = 4, /// /// Enum Read for value: message-read /// [EnumMember(Value = "message-read")] - Read = 4 + Read = 5 } }