zernio-sdk 0.0.733 → 0.0.735
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/docs/InboxWebhookMessage.md +1 -1
- data/docs/WebhookPayloadMessageMessage.md +1 -1
- data/docs/WebhookPayloadMessageSentMessage.md +1 -1
- data/lib/zernio-sdk/models/inbox_webhook_message.rb +1 -0
- data/lib/zernio-sdk/models/upload_token_status_response.rb +1 -0
- data/lib/zernio-sdk/models/webhook_payload_message_message.rb +1 -0
- data/lib/zernio-sdk/models/webhook_payload_message_sent_message.rb +1 -0
- data/lib/zernio-sdk/version.rb +1 -1
- data/openapi.yaml +4 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ad78ea19ea8742d26f513f2a82b93cab468e7c8a883d32e64718ae7bcf1cc0b0
|
|
4
|
+
data.tar.gz: ab477092fc5840a8da953e820cbe904bc1cb164a08f9fe10daa784244769f7dd
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: c39a398452c96bea78af0cb178ceed58f112f1955b350c97b764f3fa5e4d23953bed492e08de57d38fa8340169675f3ff821a54595faf4a7de6654e4d00fd7b5
|
|
7
|
+
data.tar.gz: 0ad15ea775b0b6cd57b875c0c3724a828477ed2e9de5fe3ea3a5353cd255baf2f4faf8468737302f553dab9649bbd7b0bac6984745dc58952b46e1aa26bcb619
|
data/docs/InboxWebhookMessage.md
CHANGED
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
| **text** | **String** | Message text content (retained on deleted messages for API consumers; Zernio dashboard UI hides this) | |
|
|
13
13
|
| **attachments** | [**Array<InboxWebhookMessageAttachmentsInner>**](InboxWebhookMessageAttachmentsInner.md) | | |
|
|
14
14
|
| **sender** | [**InboxWebhookMessageSender**](InboxWebhookMessageSender.md) | | |
|
|
15
|
-
| **sent_at** | **Time** |
|
|
15
|
+
| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. | |
|
|
16
16
|
| **is_read** | **Boolean** | | |
|
|
17
17
|
|
|
18
18
|
## Example
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
| **text** | **String** | Message text content | |
|
|
13
13
|
| **attachments** | [**Array<WebhookPayloadMessageMessageAttachmentsInner>**](WebhookPayloadMessageMessageAttachmentsInner.md) | | |
|
|
14
14
|
| **sender** | [**WebhookPayloadMessageMessageSender**](WebhookPayloadMessageMessageSender.md) | | |
|
|
15
|
-
| **sent_at** | **Time** |
|
|
15
|
+
| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. | |
|
|
16
16
|
| **is_read** | **Boolean** | | |
|
|
17
17
|
|
|
18
18
|
## Example
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
| **text** | **String** | Message text content | |
|
|
13
13
|
| **attachments** | [**Array<WebhookPayloadMessageSentMessageAttachmentsInner>**](WebhookPayloadMessageSentMessageAttachmentsInner.md) | | |
|
|
14
14
|
| **sender** | [**WebhookPayloadMessageSentMessageSender**](WebhookPayloadMessageSentMessageSender.md) | | |
|
|
15
|
-
| **sent_at** | **Time** |
|
|
15
|
+
| **sent_at** | **Time** | When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order. | |
|
|
16
16
|
| **is_read** | **Boolean** | | |
|
|
17
17
|
| **source** | **String** | WhatsApp send origin. whatsapp_business_app when sent from the WhatsApp Business phone app on a Coexistence number; cloud_api when sent through Zernio (dashboard, API, or broadcasts). Absent on non-WhatsApp platforms. This is not the inbox metadata.source lineage field. | [optional] |
|
|
18
18
|
|
|
@@ -36,6 +36,7 @@ module Zernio
|
|
|
36
36
|
|
|
37
37
|
attr_accessor :sender
|
|
38
38
|
|
|
39
|
+
# When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
|
|
39
40
|
attr_accessor :sent_at
|
|
40
41
|
|
|
41
42
|
attr_accessor :is_read
|
|
@@ -35,6 +35,7 @@ module Zernio
|
|
|
35
35
|
|
|
36
36
|
attr_accessor :sender
|
|
37
37
|
|
|
38
|
+
# When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
|
|
38
39
|
attr_accessor :sent_at
|
|
39
40
|
|
|
40
41
|
attr_accessor :is_read
|
|
@@ -35,6 +35,7 @@ module Zernio
|
|
|
35
35
|
|
|
36
36
|
attr_accessor :sender
|
|
37
37
|
|
|
38
|
+
# When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.
|
|
38
39
|
attr_accessor :sent_at
|
|
39
40
|
|
|
40
41
|
attr_accessor :is_read
|
data/lib/zernio-sdk/version.rb
CHANGED
data/openapi.yaml
CHANGED
|
@@ -3287,6 +3287,7 @@ components:
|
|
|
3287
3287
|
sentAt:
|
|
3288
3288
|
type: string
|
|
3289
3289
|
format: date-time
|
|
3290
|
+
description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
|
|
3290
3291
|
isRead:
|
|
3291
3292
|
type: boolean
|
|
3292
3293
|
InboxWebhookConversation:
|
|
@@ -3588,6 +3589,7 @@ components:
|
|
|
3588
3589
|
sentAt:
|
|
3589
3590
|
type: string
|
|
3590
3591
|
format: date-time
|
|
3592
|
+
description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
|
|
3591
3593
|
isRead:
|
|
3592
3594
|
type: boolean
|
|
3593
3595
|
conversation:
|
|
@@ -3929,6 +3931,7 @@ components:
|
|
|
3929
3931
|
sentAt:
|
|
3930
3932
|
type: string
|
|
3931
3933
|
format: date-time
|
|
3934
|
+
description: 'When the message was sent, as reported by the platform and passed through unmodified. Full ISO 8601 date-time: Instagram and Facebook carry millisecond precision, while some platforms (for example WhatsApp and Telegram) report whole seconds. Use this field as the chronological ordering key. If two messages share the same value, fetch the conversation messages with sortOrder=desc for the deterministic order.'
|
|
3932
3935
|
isRead:
|
|
3933
3936
|
type: boolean
|
|
3934
3937
|
source:
|
|
@@ -7398,7 +7401,7 @@ components:
|
|
|
7398
7401
|
$ref: '#/components/schemas/UploadedFile'
|
|
7399
7402
|
createdAt: { type: string, format: date-time }
|
|
7400
7403
|
expiresAt: { type: string, format: date-time }
|
|
7401
|
-
completedAt: { type: string, format: date-time }
|
|
7404
|
+
completedAt: { type: [string, "null"], format: date-time }
|
|
7402
7405
|
QueueSlotsResponse:
|
|
7403
7406
|
type: object
|
|
7404
7407
|
description: Single queue response (default behavior)
|