mirror of
https://github.com/friuns2/BlackFriday-GPTs-Prompts.git
synced 2026-05-03 07:23:53 +07:00
2024 chatgpt update
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
|
||||
[![SchemaGPT for app structure planning [GPT-4]](https://flow-prompt-covers.s3.us-west-1.amazonaws.com/icon/vintage/vint_1.png)](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22y_CAdOcNNWjvuqecmvkui%22%2C%22flow%22%3Atrue%7D%7D)
|
||||
|
||||
# SchemaGPT for app structure planning [GPT-4] | [Start Chat](https://gptcall.net/chat.html?data=%7B%22contact%22%3A%7B%22id%22%3A%22y_CAdOcNNWjvuqecmvkui%22%2C%22flow%22%3Atrue%7D%7D)
|
||||
The idea of this prompt is to build a swagger-like schema. It can be used on development early stages to get an example structure of app.
|
||||
|
||||
@@ -41,6 +41,95 @@ Input: API for a Facebook-like app
|
||||
I'd like you to assist in building a schema for a web app based on the business logic input.\nSchema:\n{METHOD} {PATH}\nAuth: {IS AUTH REQUIRED}\nHeaders: {UNIQUE HEADERS}\nBody: {BODY IF METHOD SUPPORTS}\nDescription: {DESCRIPTION}\n\nInput: api for messaging app
|
||||
```
|
||||
|
||||
## Welcome Message
|
||||
Sure, here's an example schema for a messaging app API:
|
||||
|
||||
|
||||
|
||||
Schema:
|
||||
|
||||
POST /messages
|
||||
|
||||
Auth: Required
|
||||
|
||||
Headers:
|
||||
|
||||
- Authorization: Bearer {access_token}
|
||||
|
||||
- Content-Type: application/json
|
||||
|
||||
Body:
|
||||
|
||||
- recipient_id: string
|
||||
|
||||
- message_text: string
|
||||
|
||||
Description: Send a new message to a user identified by recipient_id.
|
||||
|
||||
|
||||
|
||||
GET /conversations
|
||||
|
||||
Auth: Required
|
||||
|
||||
Headers:
|
||||
|
||||
- Authorization: Bearer {access_token}
|
||||
|
||||
Body: N/A
|
||||
|
||||
Description: Get a list of conversations for the authenticated user.
|
||||
|
||||
|
||||
|
||||
GET /conversations/{conversation_id}/messages
|
||||
|
||||
Auth: Required
|
||||
|
||||
Headers:
|
||||
|
||||
- Authorization: Bearer {access_token}
|
||||
|
||||
Body: N/A
|
||||
|
||||
Description: Get all messages for a specific conversation.
|
||||
|
||||
|
||||
|
||||
PUT /conversations/{conversation_id}/messages/{message_id}
|
||||
|
||||
Auth: Required
|
||||
|
||||
Headers:
|
||||
|
||||
- Authorization: Bearer {access_token}
|
||||
|
||||
- Content-Type: application/json
|
||||
|
||||
Body:
|
||||
|
||||
- message_text: string
|
||||
|
||||
Description: Update an existing message in a specific conversation.
|
||||
|
||||
|
||||
|
||||
DELETE /conversations/{conversation_id}/messages/{message_id}
|
||||
|
||||
Auth: Required
|
||||
|
||||
Headers:
|
||||
|
||||
- Authorization: Bearer {access_token}
|
||||
|
||||
Body: N/A
|
||||
|
||||
Description: Delete an existing message in a specific conversation.
|
||||
|
||||
|
||||
|
||||
Note that this is just an example schema and should be adapted to fit your specific requirements. Additionally, you will need to implement appropriate authentication mechanisms and obtain any necessary permissions and credentials from your messaging service provider.
|
||||
|
||||
## Conversation
|
||||
|
||||
**ASSISTANT**: Sure, here's an example schema for a messaging app API:
|
||||
@@ -131,4 +220,3 @@ Description: Delete an existing message in a specific conversation.
|
||||
|
||||
Note that this is just an example schema and should be adapted to fit your specific requirements. Additionally, you will need to implement appropriate authentication mechanisms and obtain any necessary permissions and credentials from your messaging service provider.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user