louiscklaw/004_comission
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update,

Browse Source
This commit is contained in:
louiscklaw
2025-01-31 19:43:32 +08:00
parent 2f811976ba
commit 564d46691e
19 changed files with 54 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
eyt278181/gitUpdate.bat Normal file
View File

@@ -0,0 +1,7 @@
git status .
@pause
git add .
git commit -m"update eyt278181,"
start git push

16
eyt278181/meta.md Normal file
View File

@@ -0,0 +1,16 @@
monitor-24.com
明白嘅，
咁我又假設有客人想做 integration ，
咁我想再問下有冇機會有 API doc 呢類文件可以望一望?
唔好意思先，我可能未帶到客仔比你住，不過傾開我想了解多 D 先
假設有客人買 1 lot (例如過千個 website monitor )咁先算啦
咁一般而言都唔會叫個客人一個一個咁督入去架嘛
咁所以好多時都有 D 叫 "API" 嘅野話比客仔可以點樣去 integrate 落去你地服務果度，咁果份 doc 就叫 "API doc".
Sorry in advance as i may not the right on to get customer to you but i would liek to know more by this chance.
so let say someone (possibly a corperate-customer) would like to subscribe one lot (let say 1000 website monitoring) service from you. how can you serve ? currently, AFAIK a popular model is leaving a API (endpoint) that can communiate with your system. when customer pass a HTTP request (with parameter/query) to this endpoint to your system. then your system parse those parameters, configure them accordingly (i.e. website monitoring --drive--> discord paging).
but most of the time this kind of process is expected full automatic. so is there any documentation to tell user/customer how to do that ?