Skip to content

Conversation

@radekholy24
Copy link
Contributor

@radekholy24 radekholy24 commented Dec 20, 2021

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.

type: array
items:
$ref: '#/components/schemas/events'
$ref: '#/components/schemas/event'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this correct?

Copy link
Contributor

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'
Copy link
Contributor Author

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?

Comment on lines 1480 to 1524
message:
description: Outgoing message
type: object
example:
body: Hello world
type: text
Copy link
Contributor Author

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?

Copy link
Contributor

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

Copy link
Contributor Author

@radekholy24 radekholy24 Jan 11, 2022

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?

Comment on lines 925 to 960
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
Copy link
Contributor Author

@radekholy24 radekholy24 Jan 3, 2022

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?

Copy link
Contributor Author

@radekholy24 radekholy24 Jan 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@radekholy24 radekholy24 force-pushed the proofreading-support-inbox branch from 0eb8303 to 9026996 Compare January 3, 2022 21:37
Comment on lines 2436 to 2474
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'
Copy link
Contributor Author

@radekholy24 radekholy24 Jan 4, 2022

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?

@radekholy24 radekholy24 force-pushed the proofreading-support-inbox branch 3 times, most recently from f0af738 to c5fa8eb Compare January 18, 2022 15:10
@radekholy24 radekholy24 force-pushed the proofreading-support-inbox branch from c5fa8eb to e226bc9 Compare January 18, 2022 15:51
@radekholy24 radekholy24 force-pushed the proofreading-support-inbox branch 2 times, most recently from 7d2b00d to b72fa31 Compare January 20, 2022 13:25
@radekholy24
Copy link
Contributor Author

radekholy24 commented Feb 10, 2022

https://github.com/radekholy24/tyntec-api-collection/blob/proofreading-support-inbox/third-party/eazy/v1/openapi.yaml#L2827

Ad components parameter, it is a string at the moment. Shouldn't it be an array? I cannot test it.

items:
$ref: '#/components/schemas/email'
example: [[email protected], [email protected], [email protected]]
email:
Copy link
Contributor Author

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?

@radekholy24
Copy link
Contributor Author

  • In contactResponse, there is a notes property that refers #/components/schemas/note. However, there is no note schema. Can you provide the schema?

@radekholy24 radekholy24 marked this pull request as ready for review May 2, 2022 11:52
@radekholy24
Copy link
Contributor Author

This is now ready to be reviewed. Can you please take a look?

@radekholy24 radekholy24 changed the title Support Inbox API proofreading Conversations Inbox API proofreading May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants