Manajemen Keyword Auto Reply
API kami dirancang untuk mempermudah Anda mengatur keyword balasan otomatis (auto reply) di setiap perangkat. Kami sudah mengembangkan sistem auto reply yang interaktif dengan lima mode pencocokan pesan canggih:
🟢 Exact: Balasan terkirim hanya jika pesan sama persis dengan keyword (huruf besar/kecil berpengaruh). 🟢 Contains: Pesan apa pun yang mengandung keyword akan memicu balasan. 🟢 Startswith: Balasan aktif jika pesan dimulai dengan keyword tertentu. 🟢 Endswith: Jika pesan diakhiri dengan keyword, balasan akan terkirim. 🟢 Regex: Gunakan ekspresi reguler untuk pencocokan pesan yang sangat kompleks dan fleksibel.
Dengan pilihan ini, Anda bisa memastikan sistem auto reply Anda bekerja lebih akurat dan sesuai kebutuhan.
Menambah keyword baru
api_key
caption
from
keyword
match_type
response_reply
status
type
POST /api/addKeyword HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 166
"apiKey='api_key'&caption='caption'&from='from'&keyword='keyword'&match_type='match_type'&response_reply='response_reply'&status='status'&type='type'"
Response 200
{
"status": true,
"data": {
"id": "xxxxx",
"apiKey": "xxxxxx",
"keyword": "xxxxxx",
"response_reply": "xxxxx",
"type": "text",
"match_type": "exact", // exact, contains, startswith, endswith, regex
"status": true
}
}
Mengubah keyword
api_key
caption
id_device
keyword
match_type
response_reply
status
type
POST /api/editKeyword HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 169
"apiKey='api_key'&caption='caption'&id='id_device'&keyword='keyword'&match_type='match_type'&response_reply='response_reply'&status='status'&type='type'"
Response 200
{
"status": true,
"data": {
"id": "xxxxx",
"apiKey": "xxxxxx",
"keyword": "xxxxxx",
"response_reply": "xxxxx",
"type": "text",
"match_type": "exact", // exact, contains, startswith, endswith, regex
"status": true
}
}
Menampilkan seluruh data keyword yang sudah terdaftar
api_key
POST /api/getKeyword HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 20
"apiKey='api_key'"
Response 200
{
"status": true,
"data": [
{
"id": "xxxx",
"apiKey": "xxxx",
"keyword": "xxxx",
"response_reply": "https://xxxxxx",
"type": "image",
"match_type": "exact", // exact, contains, startswith, endswith, regex
"status": true,
"caption": "testa",
"createdAt": "2023-10-20T03:19:10.444Z",
"updatedAt": "2024-04-02T12:56:30.399Z"
}
]
}
Melihat detail keyword
api_key
id_device
POST /api/detailKeyword HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 37
"apiKey='api_key'&id='id_device'"
Response 200
{
"status": true,
"data": {
"id": "xxxxx",
"apiKey": "xxxxxx",
"keyword": "xxxxxx",
"response_reply": "https://xxxxxx",
"type": "image",
"match_type": "exact", // exact, contains, startswith, endswith, regex
"status": true,
"caption": "testa",
"createdAt": "2023-10-20T03:19:10.444Z",
"updatedAt": "2024-04-02T12:56:30.399Z"
}
}
Menghapus keyword
api_key
id_device
POST /api/deleteKeyword HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded
Accept: */*
Content-Length: 37
"apiKey='api_key'&id='id_device'"
Response 200
{
"message": "Keyword deleted successfully",
"status": true
}