Fix: Make swagger doc compliant to OpenAPI (#3394)
This fixes issues in the swagger.json file. The motivation to do so is to be able to generate API clients using https://openapi-generator.tech Doing so will require further changes to the api spec, but this seems like a good first step since it is now "valid" according to editor.swagger.io and openapi-generator validate. Fixes #2806
This commit is contained in:
@@ -1,8 +1,9 @@
|
||||
type: object
|
||||
required:
|
||||
- inbox_id
|
||||
properties:
|
||||
inbox_id:
|
||||
type: number
|
||||
required: true
|
||||
name:
|
||||
type: string
|
||||
description: name of the contact
|
||||
@@ -12,7 +13,7 @@ properties:
|
||||
phone_number:
|
||||
type: string
|
||||
description: phone number of the contact
|
||||
identifier:
|
||||
identifier:
|
||||
type: string
|
||||
description: A unique identifier for the contact in external system
|
||||
custom_attributes:
|
||||
|
||||
@@ -1,9 +1,10 @@
|
||||
type: object
|
||||
required:
|
||||
- content
|
||||
properties:
|
||||
content:
|
||||
type: string
|
||||
description: The content of the message
|
||||
required: true
|
||||
message_type:
|
||||
type: string
|
||||
enum: ['outgoing', 'incoming']
|
||||
@@ -18,4 +19,3 @@ properties:
|
||||
content_attributes:
|
||||
type: object
|
||||
description: attributes based on your content type
|
||||
|
||||
|
||||
Reference in New Issue
Block a user