Skip to content

Commit 1d5ff8e

Browse files
band-swi-release-engineering[bot]DX-Bandwidth
band-swi-release-engineering[bot]
and
DX-Bandwidth
authored
Generate SDK with OpenAPI Generator Version (#198)
Co-authored-by: DX-Bandwidth <dx@bandwidth.com>
1 parent f42cc78 commit 1d5ff8e

8 files changed

Lines changed: 85 additions & 26 deletions

File tree

‎Bandwidth.Standard.sln‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ Microsoft Visual Studio Solution File, Format Version 12.00
22
# Visual Studio 14
33
VisualStudioVersion = 14.0.25420.1
44
MinimumVisualStudioVersion = 10.0.40219.1
5-
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard", "src\Bandwidth.Standard\Bandwidth.Standard.csproj", "{B644B02A-2DAC-42EA-A361-EB14EAD13209}"
5+
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard", "src\Bandwidth.Standard\Bandwidth.Standard.csproj", "{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}"
66
EndProject
77
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Bandwidth.Standard.Test", "src\Bandwidth.Standard.Test\Bandwidth.Standard.Test.csproj", "{19F1DEBC-DE5E-4517-8062-F000CD499087}"
88
EndProject
@@ -12,10 +12,10 @@ Global
1212
Release|Any CPU = Release|Any CPU
1313
EndGlobalSection
1414
GlobalSection(ProjectConfigurationPlatforms) = postSolution
15-
{B644B02A-2DAC-42EA-A361-EB14EAD13209}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
16-
{B644B02A-2DAC-42EA-A361-EB14EAD13209}.Debug|Any CPU.Build.0 = Debug|Any CPU
17-
{B644B02A-2DAC-42EA-A361-EB14EAD13209}.Release|Any CPU.ActiveCfg = Release|Any CPU
18-
{B644B02A-2DAC-42EA-A361-EB14EAD13209}.Release|Any CPU.Build.0 = Release|Any CPU
15+
{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
16+
{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Debug|Any CPU.Build.0 = Debug|Any CPU
17+
{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Release|Any CPU.ActiveCfg = Release|Any CPU
18+
{FCEE569B-02A9-4CA9-97FD-2DF8A3F03322}.Release|Any CPU.Build.0 = Release|Any CPU
1919
{19F1DEBC-DE5E-4517-8062-F000CD499087}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
2020
{19F1DEBC-DE5E-4517-8062-F000CD499087}.Debug|Any CPU.Build.0 = Debug|Any CPU
2121
{19F1DEBC-DE5E-4517-8062-F000CD499087}.Release|Any CPU.ActiveCfg = Release|Any CPU

‎api/openapi.yaml‎

Lines changed: 31 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6361,6 +6361,8 @@ components:
63616361
examples:
63626362
messageSendingCallback:
63636363
$ref: '#/components/examples/messageSendingCallbackExample'
6364+
messageSentCallback:
6365+
$ref: '#/components/examples/messageSentCallbackExample'
63646366
smsMessageDeliveredCallback:
63656367
$ref: '#/components/examples/smsMessageDeliveredCallbackExample'
63666368
mmsMessageDeliveredCallback:
@@ -6374,7 +6376,7 @@ components:
63746376
description: |-
63756377
<p>This Outbound Message Webhook is an envelope containing status information regarding a message sent (MT)
63766378
from your message-enabled Bandwidth telephone number.
6377-
<p>The payload type will be one of <code>message-sending</code>, <code>message-delivered</code>, <code>message-failed</code> or <code>message-read</code>.
6379+
<p>The payload type will be one of <code>message-sending</code>, <code>message-sent</code>, <code>message-delivered</code>, <code>message-failed</code> or <code>message-read</code>.
63786380
<p>Note that <code>message-read</code> callbacks are pertinent only for RBM messages sent from the <code>/messages/multiChannel</code> endpoint.
63796381
</p><p>Please visit <a href='/docs/messaging/webhooks/'>Webhooks</a></p>
63806382
required: true
@@ -6554,12 +6556,33 @@ components:
65546556
media:
65556557
- https://dev.bandwidth.com/images/bandwidth-logo.png
65566558
tag: your tag here
6559+
messageSentCallbackExample:
6560+
summary: An example of a message-sent callback body.
6561+
value:
6562+
time: 2024-06-25T18:42:36.979456Z
6563+
type: message-sent
6564+
to: "+15554443333"
6565+
description: Message sent to carrier
6566+
message:
6567+
id: 1593110555875xo7watq5px6rbe5d
6568+
owner: "+15552221111"
6569+
applicationId: cfd4fb83-7531-4acc-b471-42d0bb76a65c
6570+
time: 2024-06-25T18:42:35.876906Z
6571+
segmentCount: 1
6572+
direction: out
6573+
to:
6574+
- "+15554443333"
6575+
from: "+15552221111"
6576+
text: ""
6577+
media:
6578+
- https://dev.bandwidth.com/images/bandwidth-logo.png
6579+
tag: v2 lab
65576580
smsMessageDeliveredCallbackExample:
65586581
summary: An example of a sms message-delivered callback body.
65596582
value:
65606583
type: message-delivered
65616584
time: 2024-09-14T18:20:11.160744Z
6562-
description: Message delivered to carrier.
6585+
description: Message delivered to handset.
65636586
to: "+12345678902"
65646587
message:
65656588
id: 14762070468292kw2fuqty55yp2b2
@@ -6577,7 +6600,7 @@ components:
65776600
value:
65786601
type: message-delivered
65796602
time: 2024-09-14T18:20:24.160544Z
6580-
description: Message delivered to carrier.
6603+
description: Message delivered to handset.
65816604
to: "+12345678902"
65826605
message:
65836606
id: 14762070468292kw2fuqty55yp2b2
@@ -6597,7 +6620,7 @@ components:
65976620
value:
65986621
type: message-delivered
65996622
time: 2024-09-14T18:20:17.160544Z
6600-
description: Message delivered to carrier.
6623+
description: Message delivered to handset.
66016624
to: "+12345678902"
66026625
message:
66036626
id: 14762070468292kw2fuqty55yp2b2
@@ -10567,7 +10590,7 @@ components:
1056710590
type: string
1056810591
description:
1056910592
description: A detailed description of the event described by the callback.
10570-
example: Message delivered to carrier.
10593+
example: Message delivered to handset.
1057110594
type: string
1057210595
message:
1057310596
$ref: '#/components/schemas/statusCallbackMessage'
@@ -10628,11 +10651,13 @@ components:
1062810651
description: |-
1062910652
The possible status callbacks when sending an MT SMS or MMS or RBM message:
1063010653
- `message-sending` indicates that Bandwidth is sending the message to the upstream provider.
10631-
- `message-delivered` indicates that the message was successfully sent.
10654+
- `message-sent` indicates that the message has left the Bandwidth network and is in transit to the provider.
10655+
- `message-delivered` indicates that the message was successfully delivered to handset.
1063210656
- `message-failed` indicates that the message could not be sent to the intended recipient.
1063310657
- `message-read` indicates that the RBM message was read by the recipient.
1063410658
enum:
1063510659
- message-sending
10660+
- message-sent
1063610661
- message-delivered
1063710662
- message-failed
1063810663
- message-read

‎bandwidth.yml‎

Lines changed: 34 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2962,7 +2962,7 @@ components:
29622962
description:
29632963
type: string
29642964
description: A detailed description of the event described by the callback.
2965-
example: Message delivered to carrier.
2965+
example: Message delivered to handset.
29662966
message:
29672967
$ref: '#/components/schemas/statusCallbackMessage'
29682968
errorCode:
@@ -3018,7 +3018,11 @@ components:
30183018
- `message-sending` indicates that Bandwidth is sending the message to
30193019
the upstream provider.
30203020
3021-
- `message-delivered` indicates that the message was successfully sent.
3021+
- `message-sent` indicates that the message has left the Bandwidth
3022+
network and is in transit to the provider.
3023+
3024+
- `message-delivered` indicates that the message was successfully
3025+
delivered to handset.
30223026
30233027
- `message-failed` indicates that the message could not be sent to the
30243028
intended recipient.
@@ -3027,6 +3031,7 @@ components:
30273031
recipient.
30283032
enum:
30293033
- message-sending
3034+
- message-sent
30303035
- message-delivered
30313036
- message-failed
30323037
- message-read
@@ -8712,12 +8717,33 @@ components:
87128717
media:
87138718
- https://dev.bandwidth.com/images/bandwidth-logo.png
87148719
tag: your tag here
8720+
messageSentCallbackExample:
8721+
summary: An example of a message-sent callback body.
8722+
value:
8723+
time: '2024-06-25T18:42:36.979456Z'
8724+
type: message-sent
8725+
to: '+15554443333'
8726+
description: Message sent to carrier
8727+
message:
8728+
id: 1593110555875xo7watq5px6rbe5d
8729+
owner: '+15552221111'
8730+
applicationId: cfd4fb83-7531-4acc-b471-42d0bb76a65c
8731+
time: '2024-06-25T18:42:35.876906Z'
8732+
segmentCount: 1
8733+
direction: out
8734+
to:
8735+
- '+15554443333'
8736+
from: '+15552221111'
8737+
text: ''
8738+
media:
8739+
- https://dev.bandwidth.com/images/bandwidth-logo.png
8740+
tag: v2 lab
87158741
smsMessageDeliveredCallbackExample:
87168742
summary: An example of a sms message-delivered callback body.
87178743
value:
87188744
type: message-delivered
87198745
time: '2024-09-14T18:20:11.160744Z'
8720-
description: Message delivered to carrier.
8746+
description: Message delivered to handset.
87218747
to: '+12345678902'
87228748
message:
87238749
id: 14762070468292kw2fuqty55yp2b2
@@ -8735,7 +8761,7 @@ components:
87358761
value:
87368762
type: message-delivered
87378763
time: '2024-09-14T18:20:24.160544Z'
8738-
description: Message delivered to carrier.
8764+
description: Message delivered to handset.
87398765
to: '+12345678902'
87408766
message:
87418767
id: 14762070468292kw2fuqty55yp2b2
@@ -8755,7 +8781,7 @@ components:
87558781
value:
87568782
type: message-delivered
87578783
time: '2024-09-14T18:20:17.160544Z'
8758-
description: Message delivered to carrier.
8784+
description: Message delivered to handset.
87598785
to: '+12345678902'
87608786
message:
87618787
id: 14762070468292kw2fuqty55yp2b2
@@ -9787,7 +9813,7 @@ components:
97879813
information regarding a message sent (MT)
97889814
97899815
from your message-enabled Bandwidth telephone number.
9790-
<p>The payload type will be one of <code>message-sending</code>, <code>message-delivered</code>, <code>message-failed</code> or <code>message-read</code>.
9816+
<p>The payload type will be one of <code>message-sending</code>, <code>message-sent</code>, <code>message-delivered</code>, <code>message-failed</code> or <code>message-read</code>.
97919817
<p>Note that <code>message-read</code> callbacks are pertinent only for RBM messages sent from the <code>/messages/multiChannel</code> endpoint.
97929818
</p><p>Please visit <a
97939819
href='/docs/messaging/webhooks/'>Webhooks</a></p>
@@ -9798,6 +9824,8 @@ components:
97989824
examples:
97999825
messageSendingCallback:
98009826
$ref: '#/components/examples/messageSendingCallbackExample'
9827+
messageSentCallback:
9828+
$ref: '#/components/examples/messageSentCallbackExample'
98019829
smsMessageDeliveredCallback:
98029830
$ref: '#/components/examples/smsMessageDeliveredCallbackExample'
98039831
mmsMessageDeliveredCallback:

‎docs/StatusCallbackTypeEnum.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Bandwidth.Standard.Model.StatusCallbackTypeEnum
2-
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.
2+
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.
33

44
## Properties
55

‎src/Bandwidth.Standard/Model/RbmActionBase.cs‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ protected RbmActionBase() { }
7878
/// Base64 payload the customer receives when the reply is clicked.
7979
/// </summary>
8080
/// <value>Base64 payload the customer receives when the reply is clicked.</value>
81-
/// <example>[B@2041c9a3</example>
81+
/// <example>[B@50841932</example>
8282
[DataMember(Name = "postbackData", IsRequired = true, EmitDefaultValue = true)]
8383
public byte[] PostbackData { get; set; }
8484

‎src/Bandwidth.Standard/Model/RbmSuggestionResponse.cs‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ public partial class RbmSuggestionResponse : IValidatableObject
5757
/// Base64 payload the customer receives when the reply is clicked.
5858
/// </summary>
5959
/// <value>Base64 payload the customer receives when the reply is clicked.</value>
60-
/// <example>[B@2041c9a3</example>
60+
/// <example>[B@50841932</example>
6161
[DataMember(Name = "postbackData", EmitDefaultValue = false)]
6262
public byte[] PostbackData { get; set; }
6363

‎src/Bandwidth.Standard/Model/StatusCallback.cs‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ protected StatusCallback() { }
108108
/// A detailed description of the event described by the callback.
109109
/// </summary>
110110
/// <value>A detailed description of the event described by the callback.</value>
111-
/// <example>Message delivered to carrier.</example>
111+
/// <example>Message delivered to handset.</example>
112112
[DataMember(Name = "description", IsRequired = true, EmitDefaultValue = true)]
113113
public string Description { get; set; }
114114

‎src/Bandwidth.Standard/Model/StatusCallbackTypeEnum.cs‎

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,9 @@
2727
namespace Bandwidth.Standard.Model
2828
{
2929
/// <summary>
30-
/// The possible status callbacks when sending an MT SMS or MMS or RBM message: - &#x60;message-sending&#x60; indicates that Bandwidth is sending the message to the upstream provider. - &#x60;message-delivered&#x60; indicates that the message was successfully sent. - &#x60;message-failed&#x60; indicates that the message could not be sent to the intended recipient. - &#x60;message-read&#x60; indicates that the RBM message was read by the recipient.
30+
/// The possible status callbacks when sending an MT SMS or MMS or RBM message: - &#x60;message-sending&#x60; indicates that Bandwidth is sending the message to the upstream provider. - &#x60;message-sent&#x60; indicates that the message has left the Bandwidth network and is in transit to the provider. - &#x60;message-delivered&#x60; indicates that the message was successfully delivered to handset. - &#x60;message-failed&#x60; indicates that the message could not be sent to the intended recipient. - &#x60;message-read&#x60; indicates that the RBM message was read by the recipient.
3131
/// </summary>
32-
/// <value>The possible status callbacks when sending an MT SMS or MMS or RBM message: - &#x60;message-sending&#x60; indicates that Bandwidth is sending the message to the upstream provider. - &#x60;message-delivered&#x60; indicates that the message was successfully sent. - &#x60;message-failed&#x60; indicates that the message could not be sent to the intended recipient. - &#x60;message-read&#x60; indicates that the RBM message was read by the recipient.</value>
32+
/// <value>The possible status callbacks when sending an MT SMS or MMS or RBM message: - &#x60;message-sending&#x60; indicates that Bandwidth is sending the message to the upstream provider. - &#x60;message-sent&#x60; indicates that the message has left the Bandwidth network and is in transit to the provider. - &#x60;message-delivered&#x60; indicates that the message was successfully delivered to handset. - &#x60;message-failed&#x60; indicates that the message could not be sent to the intended recipient. - &#x60;message-read&#x60; indicates that the RBM message was read by the recipient.</value>
3333
[JsonConverter(typeof(StringEnumConverter))]
3434
public enum StatusCallbackTypeEnum
3535
{
@@ -39,23 +39,29 @@ public enum StatusCallbackTypeEnum
3939
[EnumMember(Value = "message-sending")]
4040
Sending = 1,
4141

42+
/// <summary>
43+
/// Enum Sent for value: message-sent
44+
/// </summary>
45+
[EnumMember(Value = "message-sent")]
46+
Sent = 2,
47+
4248
/// <summary>
4349
/// Enum Delivered for value: message-delivered
4450
/// </summary>
4551
[EnumMember(Value = "message-delivered")]
46-
Delivered = 2,
52+
Delivered = 3,
4753

4854
/// <summary>
4955
/// Enum Failed for value: message-failed
5056
/// </summary>
5157
[EnumMember(Value = "message-failed")]
52-
Failed = 3,
58+
Failed = 4,
5359

5460
/// <summary>
5561
/// Enum Read for value: message-read
5662
/// </summary>
5763
[EnumMember(Value = "message-read")]
58-
Read = 4
64+
Read = 5
5965
}
6066

6167
}

0 commit comments

Comments
 (0)