Skip to content

Commit 9184fab

Browse files
ckoegelckoegel
committed
fix spaces
1 parent f486c8b commit 9184fab

File tree

11 files changed

+142
-125
lines changed

11 files changed

+142
-125
lines changed

‎api/openapi.yaml‎

Lines changed: 62 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -322,8 +322,8 @@ paths:
322322
schema:
323323
type: string
324324
style: simple
325-
- description: |
326-
General-header field is used to specify directives that MUST be obeyed by all caching mechanisms along the request/response chain.
325+
- description: General-header field is used to specify directives that MUST
326+
be obeyed by all caching mechanisms along the request/response chain.
327327
example: no-cache
328328
explode: false
329329
in: header
@@ -408,8 +408,11 @@ paths:
408408
schema:
409409
type: string
410410
style: simple
411-
- description: |
412-
The ID of the message to search for. Special characters need to be encoded using URL encoding. Message IDs could come in different formats, e.g., 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6 and 1589228074636lm4k2je7j7jklbn2 are valid message ID formats. Note that you must include at least one query parameter.
411+
- description: "The ID of the message to search for. Special characters need\
412+
\ to be encoded using URL encoding. Message IDs could come in different\
413+
\ formats, e.g., 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6 and 1589228074636lm4k2je7j7jklbn2\
414+
\ are valid message ID formats. Note that you must include at least one\
415+
\ query parameter."
413416
example: 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6
414417
explode: true
415418
in: query
@@ -418,8 +421,10 @@ paths:
418421
schema:
419422
type: string
420423
style: form
421-
- description: |
422-
The phone number that sent the message. Accepted values are: a single full phone number a comma separated list of full phone numbers (maximum of 10) or a single partial phone number (minimum of 5 characters e.g. '%2B1919').
424+
- description: "The phone number that sent the message. Accepted values are:\
425+
\ a single full phone number a comma separated list of full phone numbers\
426+
\ (maximum of 10) or a single partial phone number (minimum of 5 characters\
427+
\ e.g. '%2B1919')."
423428
example: '%2B15554443333'
424429
explode: true
425430
in: query
@@ -428,8 +433,10 @@ paths:
428433
schema:
429434
type: string
430435
style: form
431-
- description: |
432-
The phone number that received the message. Accepted values are: a single full phone number a comma separated list of full phone numbers (maximum of 10) or a single partial phone number (minimum of 5 characters e.g. '%2B1919').
436+
- description: "The phone number that received the message. Accepted values\
437+
\ are: a single full phone number a comma separated list of full phone numbers\
438+
\ (maximum of 10) or a single partial phone number (minimum of 5 characters\
439+
\ e.g. '%2B1919')."
433440
example: '%2B15554443333'
434441
explode: true
435442
in: query
@@ -438,8 +445,8 @@ paths:
438445
schema:
439446
type: string
440447
style: form
441-
- description: |
442-
The status of the message. One of RECEIVED QUEUED SENDING SENT FAILED DELIVERED ACCEPTED UNDELIVERED.
448+
- description: The status of the message. One of RECEIVED QUEUED SENDING SENT
449+
FAILED DELIVERED ACCEPTED UNDELIVERED.
443450
explode: true
444451
in: query
445452
name: messageStatus
@@ -455,8 +462,9 @@ paths:
455462
schema:
456463
$ref: '#/components/schemas/listMessageDirectionEnum'
457464
style: form
458-
- description: |
459-
The name of the carrier used for this message. Possible values include but are not limited to Verizon and TMobile. Special characters need to be encoded using URL encoding (i.e. AT&T should be passed as AT%26T).
465+
- description: The name of the carrier used for this message. Possible values
466+
include but are not limited to Verizon and TMobile. Special characters need
467+
to be encoded using URL encoding (i.e. AT&T should be passed as AT%26T).
460468
example: Verizon
461469
explode: true
462470
in: query
@@ -482,8 +490,8 @@ paths:
482490
schema:
483491
type: integer
484492
style: form
485-
- description: |
486-
The start of the date range to search in ISO 8601 format. Uses the message receive time. The date range to search in is currently 14 days.
493+
- description: The start of the date range to search in ISO 8601 format. Uses
494+
the message receive time. The date range to search in is currently 14 days.
487495
example: 2022-09-14T18:20:16.000Z
488496
explode: true
489497
in: query
@@ -492,8 +500,8 @@ paths:
492500
schema:
493501
type: string
494502
style: form
495-
- description: |
496-
The end of the date range to search in ISO 8601 format. Uses the message receive time. The date range to search in is currently 14 days.
503+
- description: The end of the date range to search in ISO 8601 format. Uses
504+
the message receive time. The date range to search in is currently 14 days.
497505
example: 2022-09-14T18:20:16.000Z
498506
explode: true
499507
in: query
@@ -530,8 +538,8 @@ paths:
530538
schema:
531539
type: string
532540
style: form
533-
- description: |
534-
The maximum records requested in search result. Default 100. The sum of limit and after cannot be more than 10000.
541+
- description: The maximum records requested in search result. Default 100.
542+
The sum of limit and after cannot be more than 10000.
535543
example: 50
536544
explode: true
537545
in: query
@@ -5017,8 +5025,8 @@ components:
50175025
type: string
50185026
style: simple
50195027
cacheControl:
5020-
description: |
5021-
General-header field is used to specify directives that MUST be obeyed by all caching mechanisms along the request/response chain.
5028+
description: General-header field is used to specify directives that MUST be
5029+
obeyed by all caching mechanisms along the request/response chain.
50225030
example: no-cache
50235031
explode: false
50245032
in: header
@@ -5038,8 +5046,11 @@ components:
50385046
type: string
50395047
style: simple
50405048
messageId:
5041-
description: |
5042-
The ID of the message to search for. Special characters need to be encoded using URL encoding. Message IDs could come in different formats, e.g., 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6 and 1589228074636lm4k2je7j7jklbn2 are valid message ID formats. Note that you must include at least one query parameter.
5049+
description: "The ID of the message to search for. Special characters need to\
5050+
\ be encoded using URL encoding. Message IDs could come in different formats,\
5051+
\ e.g., 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6 and 1589228074636lm4k2je7j7jklbn2\
5052+
\ are valid message ID formats. Note that you must include at least one query\
5053+
\ parameter."
50435054
example: 9e0df4ca-b18d-40d7-a59f-82fcdf5ae8e6
50445055
explode: true
50455056
in: query
@@ -5049,8 +5060,9 @@ components:
50495060
type: string
50505061
style: form
50515062
sourceTn:
5052-
description: |
5053-
The phone number that sent the message. Accepted values are: a single full phone number a comma separated list of full phone numbers (maximum of 10) or a single partial phone number (minimum of 5 characters e.g. '%2B1919').
5063+
description: "The phone number that sent the message. Accepted values are: a\
5064+
\ single full phone number a comma separated list of full phone numbers (maximum\
5065+
\ of 10) or a single partial phone number (minimum of 5 characters e.g. '%2B1919')."
50545066
example: '%2B15554443333'
50555067
explode: true
50565068
in: query
@@ -5060,8 +5072,10 @@ components:
50605072
type: string
50615073
style: form
50625074
destinationTn:
5063-
description: |
5064-
The phone number that received the message. Accepted values are: a single full phone number a comma separated list of full phone numbers (maximum of 10) or a single partial phone number (minimum of 5 characters e.g. '%2B1919').
5075+
description: "The phone number that received the message. Accepted values are:\
5076+
\ a single full phone number a comma separated list of full phone numbers\
5077+
\ (maximum of 10) or a single partial phone number (minimum of 5 characters\
5078+
\ e.g. '%2B1919')."
50655079
example: '%2B15554443333'
50665080
explode: true
50675081
in: query
@@ -5071,8 +5085,8 @@ components:
50715085
type: string
50725086
style: form
50735087
messageStatus:
5074-
description: |
5075-
The status of the message. One of RECEIVED QUEUED SENDING SENT FAILED DELIVERED ACCEPTED UNDELIVERED.
5088+
description: The status of the message. One of RECEIVED QUEUED SENDING SENT
5089+
FAILED DELIVERED ACCEPTED UNDELIVERED.
50765090
explode: true
50775091
in: query
50785092
name: messageStatus
@@ -5090,8 +5104,9 @@ components:
50905104
$ref: '#/components/schemas/listMessageDirectionEnum'
50915105
style: form
50925106
carrierName:
5093-
description: |
5094-
The name of the carrier used for this message. Possible values include but are not limited to Verizon and TMobile. Special characters need to be encoded using URL encoding (i.e. AT&T should be passed as AT%26T).
5107+
description: The name of the carrier used for this message. Possible values
5108+
include but are not limited to Verizon and TMobile. Special characters need
5109+
to be encoded using URL encoding (i.e. AT&T should be passed as AT%26T).
50955110
example: Verizon
50965111
explode: true
50975112
in: query
@@ -5120,8 +5135,8 @@ components:
51205135
type: integer
51215136
style: form
51225137
fromDateTime:
5123-
description: |
5124-
The start of the date range to search in ISO 8601 format. Uses the message receive time. The date range to search in is currently 14 days.
5138+
description: The start of the date range to search in ISO 8601 format. Uses
5139+
the message receive time. The date range to search in is currently 14 days.
51255140
example: 2022-09-14T18:20:16.000Z
51265141
explode: true
51275142
in: query
@@ -5131,8 +5146,8 @@ components:
51315146
type: string
51325147
style: form
51335148
toDateTime:
5134-
description: |
5135-
The end of the date range to search in ISO 8601 format. Uses the message receive time. The date range to search in is currently 14 days.
5149+
description: The end of the date range to search in ISO 8601 format. Uses the
5150+
message receive time. The date range to search in is currently 14 days.
51365151
example: 2022-09-14T18:20:16.000Z
51375152
explode: true
51385153
in: query
@@ -5173,8 +5188,8 @@ components:
51735188
type: string
51745189
style: form
51755190
limit:
5176-
description: |
5177-
The maximum records requested in search result. Default 100. The sum of limit and after cannot be more than 10000.
5191+
description: The maximum records requested in search result. Default 100. The
5192+
sum of limit and after cannot be more than 10000.
51785193
example: 50
51795194
explode: true
51805195
in: query
@@ -6177,8 +6192,8 @@ components:
61776192
example: default
61786193
type: string
61796194
messageStatusEnum:
6180-
description: |
6181-
The status of the message. One of RECEIVED QUEUED SENDING SENT FAILED DELIVERED ACCEPTED UNDELIVERED.
6195+
description: The status of the message. One of RECEIVED QUEUED SENDING SENT
6196+
FAILED DELIVERED ACCEPTED UNDELIVERED.
61826197
enum:
61836198
- RECEIVED
61846199
- QUEUED
@@ -6504,8 +6519,8 @@ components:
65046519
format: date-time
65056520
type: string
65066521
segmentCount:
6507-
description: |
6508-
The number of segments the original message from the user is broken into before sending over to carrier networks.
6522+
description: The number of segments the original message from the user is
6523+
broken into before sending over to carrier networks.
65096524
example: 2
65106525
type: integer
65116526
direction:
@@ -6523,8 +6538,10 @@ components:
65236538
example: "+15553332222"
65246539
type: string
65256540
media:
6526-
description: |
6527-
The list of media URLs sent in the message. Including a `filename` field in the `Content-Disposition` header of the media linked with a URL will set the displayed file name. This is a best practice to ensure that your media has a readable file name.
6541+
description: The list of media URLs sent in the message. Including a `filename`
6542+
field in the `Content-Disposition` header of the media linked with a URL
6543+
will set the displayed file name. This is a best practice to ensure that
6544+
your media has a readable file name.
65286545
example:
65296546
- https://dev.bandwidth.com/images/bandwidth-logo.png
65306547
items:
@@ -6571,7 +6588,7 @@ components:
65716588
\ Sender IDs can contain up to 11 characters, upper-case letters A-Z,\
65726589
\ lower-case letters a-z, numbers 0-9, space, hyphen -, plus +, underscore\
65736590
\ _ and ampersand &. Alphanumeric Sender IDs must contain at least one\
6574-
\ letter.\n"
6591+
\ letter."
65756592
example: "+15551113333"
65766593
type: string
65776594
text:
@@ -6581,7 +6598,7 @@ components:
65816598
maxLength: 2048
65826599
type: string
65836600
media:
6584-
description: |
6601+
description: |-
65856602
A list of URLs to include as media attachments as part of the message.
65866603
Each URL can be at most 4096 characters.
65876604
example:
@@ -6600,7 +6617,7 @@ components:
66006617
priority:
66016618
$ref: '#/components/schemas/priorityEnum'
66026619
expiration:
6603-
description: |
6620+
description: |-
66046621
A string with the date/time value that the message will automatically expire by. This must be a valid RFC-3339 value, e.g., 2021-03-14T01:59:26Z or 2021-03-13T20:59:26-05:00. Must be a date-time in the future.
66056622
Not supported on MMS.
66066623
example: 2021-02-01T11:29:18-05:00

0 commit comments

Comments
 (0)