-
Couldn't load subscription status.
- Fork 12
Conversations Inbox API proofreading #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversations Inbox API proofreading #103
Conversation
| type: array | ||
| items: | ||
| $ref: '#/components/schemas/events' | ||
| $ref: '#/components/schemas/event' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just see that this is major mistake
it's a list of strings
| custom | Custom event for specific customer purposes |
|---|---|
| echo | Outgoing messages sent by agents or assistants |
| handover | Handover event whenever a conversation is transferred to an assistant or agent |
| label | Label event whenever a conversation is labelled or unlabelled |
| message | Incoming messages from customers |
| note | Note creation or deletion event |
| postback | Postback event for WhatsApp button templates, Apple list pickers etc |
| receipt | Message receipt event |
| template_pack | Template updates whenever templates are approved, rejected etc. |
| typing | Typing indications when customers are typing a message |
| type: array | ||
| items: | ||
| $ref: '#/components/schemas/allLabelsResponse' | ||
| $ref: '#/components/schemas/labelResponse' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could not test it. Is this correct? Maybe it should be just an array of strings?
| message: | ||
| description: Outgoing message | ||
| type: object | ||
| example: | ||
| body: Hello world | ||
| type: text |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cannot test it. What is the proper fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like there is a bigger mistake as the labels, messaging and lists resource are mixed up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have noticed that you have pushed some changes to this object to the master branch already but still... Doesn't the message object need to have its properties documented?
| requestBody: | ||
| description: The message you would like to update | ||
| required: true | ||
| content: | ||
| application/json: | ||
| schema: | ||
| type: object | ||
| properties: | ||
| body: | ||
| description: Text of the automated message | ||
| type: string | ||
| example: 'Sorry, we are currently closed. Your question will be answered as soon as possible.' | ||
| enabled: | ||
| description: Is the automated message enabled? | ||
| type: boolean | ||
| example: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cannot test it. What is the proper fix? How does the request body look like?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed to the master so I guess that I have guessed that schema right... https://github.com/tyntec/api-collection/pull/106/files#diff-fa1b1ded6b1a42d44b72a651240624ebe14243d63d9999faf2dfac83d70a8ed5R945-R960 Have I?
0eb8303 to
9026996
Compare
| name: | ||
| description: "Contact's name" | ||
| type: object | ||
| properties: | ||
| firstName: | ||
| description: "Contact's first name" | ||
| type: string | ||
| example: 'John' | ||
| fullName: | ||
| description: "Contact's full name" | ||
| type: string | ||
| example: 'John Doe' | ||
| lastName: | ||
| description: "Contact's last name" | ||
| type: string | ||
| example: 'Doe' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could not test it. Is this correct? How does the request body look like?
f0af738 to
c5fa8eb
Compare
c5fa8eb to
e226bc9
Compare
Co-authored-by: Martin <[email protected]>
7d2b00d to
b72fa31
Compare
|
Ad |
| items: | ||
| $ref: '#/components/schemas/email' | ||
| example: [[email protected], [email protected], [email protected]] | ||
| email: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ridlees suggests renaming this to jid. What do you think?
a17f586 to
e0a27bf
Compare
|
|
This is now ready to be reviewed. Can you please take a look? |
I have been assigned a task to proofread the API Reference. Peter has suggested to me to create a pull request for all my findings.