123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294 |
- import { CodeGroup } from '../code.tsx'
- import { Row, Col, Properties, Property, Heading, SubProperty, Paragraph } from '../md.tsx'
- # Completion App API
- For high-quality text generation, such as articles, summaries, and translations, use the completion-messages API with user input. Text generation relies on the model parameters and prompt templates set in Dify Prompt Engineering.
- <div>
- ### Authentication
- Service API of Dify authenticates using an `API-Key`.
- It is suggested that developers store the `API-Key` in the backend instead of sharing or storing it in the client side to avoid the leakage of the `API-Key`, which may lead to property loss.
- All API requests should include your `API-Key` in the **`Authorization`** HTTP Header, as shown below:
- <CodeGroup title="Code">
- ```javascript
- Authorization: Bearer {API_KEY}
- ```
- </CodeGroup>
- </div>
- ---
- <Heading
- url='/completion-messages'
- method='POST'
- title='Create Completion Message'
- name='#Create-Completion-Message'
- />
- <Row>
- <Col>
- Create a Completion Message to support the question-and-answer mode.
- ### Request Body
- <Properties>
- <Property name='inputs' type='object' key='inputs'>
- (Optional) Provide user input fields as key-value pairs, corresponding to variables in Prompt Eng. Key is the variable name, Value is the parameter value. If the field type is Select, the submitted Value must be one of the preset choices.
- <ul>
- {!!props.variables.length && props.variables.map(
- val => (
- <SubProperty name={val.key} type={val.type} key={val.key}>
- {val.name ? `${val.name}` : ''}
- </SubProperty>
- )
- )}
- </ul>
- </Property>
- <Property name='response_mode' type='string' key='response_mode'>
- - Blocking type, waiting for execution to complete and returning results. (Requests may be interrupted if the process is long)
- - streaming returns. Implementation of streaming return based on SSE (**[Server-Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events)**).
- </Property>
- <Property name='user' type='string' key='user'>
- The user identifier, defined by the developer, must ensure uniqueness within the app.
- </Property>
- <Property name='files' type='array[object]' key='files'>
- Uploaded files.
- - `type` file type: currently only `image` is supported.
- - `transfer_method` transfer method:
- - `remote_url`: Image address.
- - `local_file`: upload file.
- - `upload_file_id` Upload file ID. Required when `transfer_method` is `local_file`.
- - `url` image address. Required when `transfer_method` is `remote_url`.
- </Property>
- </Properties>
- </Col>
- <Col sticky>
- <CodeGroup title="Request" tag="POST" label="/completion-messages" targetCode={`curl --location --request POST '${props.appDetail.api_base_url}/completion-messages' \\\n--header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \\\n--header 'Content-Type: application/json' \\\n--data-raw '{\n "inputs": ${JSON.stringify(props.inputs)},\n "response_mode": "streaming"\n "user": "abc-123"\n}'\n`}>
- ```bash {{ title: 'cURL' }}
- curl --location --request POST '${props.appDetail.api_base_url}/completion-messages' \
- --header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \
- --header 'Content-Type: application/json' \
- --data-raw '{
- "inputs": {},
- "response_mode": "streaming",
- "user": "abc-123"
- }'
- ```
- </CodeGroup>
- ### blocking
- <CodeGroup title="Response">
- ```json {{ title: 'Response' }}
- {
- "id": "0b089b9a-24d9-48cc-94f8-762677276261",
- "answer": "how are you?",
- "created_at": 1679586667
- }
- ```
- </CodeGroup>
- ### streaming
- <CodeGroup title="Response">
- ```streaming {{ title: 'Response' }}
- data: {"id": "5ad4cb98-f0c7-4085-b384-88c403be6290", "answer": " I", "created_at": 1679586595}
- data: {"id": "5ad4cb98-f0c7-4085-b384-88c403be6290", "answer": " I", "created_at": 1679586595}
- ```
- </CodeGroup>
- </Col>
- </Row>
- ---
- <Heading
- url='/messages/{message_id}/feedbacks'
- method='POST'
- title='Message feedback (like)'
- name='#feedbacks'
- />
- <Row>
- <Col>
- Rate received messages on behalf of end-users with likes or dislikes. This data is visible in the Logs & Annotations page and used for future model fine-tuning.
- ### Path Params
- <Properties>
- <Property name='message_id' type='string' key='message_id'>
- Message ID
- </Property>
- </Properties>
- ### Request Body
- <Properties>
- <Property name='rating' type='string' key='rating'>
- like or dislike, null is undo
- </Property>
- <Property name='user' type='string' key='user'>
- The user identifier, defined by the developer, must ensure uniqueness within the app.
- </Property>
- </Properties>
- </Col>
- <Col sticky>
- <CodeGroup title="Request" tag="POST" label="/messages/{message_id}/feedbacks" targetCode={`curl --location --request POST '${props.appDetail.api_base_url}/messages/{message_id}/feedbacks \\\n--header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \\\n--header 'Content-Type: application/json' \\\n --data-raw '{ \n "rating": "like",\n "user": "abc-123"\n}'`}>
- ```bash {{ title: 'cURL' }}
- curl --location --request POST '${props.appDetail.api_base_url}/messages/{message_id}/feedbacks' \
- --header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \
- --header 'Content-Type: application/json' \
- --data-raw '{
- "rating": "like",
- "user": "abc-123"
- }'
- ```
- </CodeGroup>
- <CodeGroup title="Response">
- ```json {{ title: 'Response' }}
- {
- "has_more": false,
- "data": [
- {
- "id": "WAz8eIbvDR60rouK",
- "username": "FrankMcCallister",
- "phone_number": "1-800-759-3000",
- "avatar_url": "https://assets.protocol.chat/avatars/frank.jpg",
- "display_name": null,
- "conversation_id": "xgQQXg3hrtjh7AvZ",
- "created_at": 692233200
- },
- {
- "id": "hSIhXBhNe8X1d8Et"
- // ...
- }
- ]
- }
- ```
- </CodeGroup>
- </Col>
- </Row>
- ---
- <Heading
- url='/files/upload'
- method='POST'
- title='Upload files'
- name='#files-upload'
- />
- <Row>
- <Col>
- Upload files to the server for text generation and dialogue. Uploaded files are only available to the current end user.
- ### Request Body
- The request method is `multipart/form-data`
- <Properties>
- <Property name='file' type='file' key='file'>
- The file to upload. Currently supports png, jpg, jpeg, webp, gif format files.
- </Property>
- <Property name='user' type='string' key='user'>
- User ID, rules are defined by the developer, and it is necessary to ensure that the user ID is unique within the application.
- </Property>
- </Properties>
- </Col>
- <Col sticky>
- <CodeGroup title="Request" tag="POST" label="/files/upload" targetCode={`curl --location --request POST '${props.appDetail.api_base_url}/files/upload' \\\n--header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \\\n--form 'file=@localfile;type=image/[png|jpeg|jpg|webp|gif] \\\n--form 'user=abc-123'`}>
- ```bash {{ title: 'cURL' }}
- curl --location --request POST '${props.appDetail.api_base_url}/files/upload' \
- --header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY' \
- --form 'file=@"/path/to/file"'
- ```
- </CodeGroup>
- <CodeGroup title="Response">
- ```json {{ title: 'Response' }}
- {
- "id": "72fa9618-8f89-4a37-9b33-7e1178a24a67",
- "name": "example.png",
- "size": 1024,
- "extension": "png",
- "mime_type": "image/png",
- "created_by": 123,
- "created_at": 1577836800,
- }
- ```
- </CodeGroup>
- </Col>
- </Row>
- ---
- <Heading
- url='/parameters'
- method='GET'
- title='Obtain application parameter information'
- name='#parameters'
- />
- <Row>
- <Col>
- Content include:
- 1. Retrieve configured Input parameters, including variable names, field names, types, and default values. Typically used for displaying these fields in a form or filling in default values after the client loads.
- 2. Configuration of uploading images, including whether to enable image uploading, the number of uploaded images and the uploading method. Note: This configuration is only available when using a model that supports multimodality.
- ### Query
- <Properties>
- <Property name='user' type='string' key='user'>
- The user identifier, defined by the developer, must ensure uniqueness within the app.
- </Property>
- </Properties>
- </Col>
- <Col sticky>
- <CodeGroup title="Request" tag="GET" label="/parameters" targetCode={`curl --location --request GET '${props.appDetail.api_base_url}/parameters?user=abc-123' \\\n--header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY'`}>
- ```bash {{ title: 'cURL' }}
- curl --location --request GET '${props.appDetail.api_base_url}/parameters?user=abc-123' \
- --header 'Authorization: Bearer ENTER-YOUR-SECRET-KEY'
- ```
- </CodeGroup>
- <CodeGroup title="Response">
- ```json {{ title: 'Response' }}
- {
- "introduction": "nice to meet you",
- "user_input_form": [
- {
- "text-input": {
- "label": "a",
- "variable": "a",
- "required": true,
- "max_length": 48,
- "default": ""
- }
- }
- {
- // ...
- }
- ],
- "file_upload": {
- "image": {
- "enabled": true,
- "number_limits": 3,
- "transfer_methods": [
- "remote_url",
- "local_file"
- ]
- }
- }
- }
- ```
- </CodeGroup>
- </Col>
- </Row>
|