What the documents look like
Creator commission settlement and commission deduction happen after a sale closes. The reconciliation focus is valid promotion orders and after-sales commission deductions. The main data sources are the Selected Alliance backend, order after-sales data, the finance system, and creator contracts. For the stock procurement and supplier profile task, purchase documents, supplier records, settlement statements, refund commission deduction details, and invoices sit on one reconciliation chain. The HTTP integration step passes these materials in and out against an external interface contract and extracts return values by JSON path. Commission setting records, settlement statements, refund commission deduction details, and invoices update weekly or monthly. Interface calls are initiated at the actual point a business event occurs, and no batch synchronization or real-time trigger mechanism follows from that cadence.
Constraints at the HTTP integrations step
The HTTP module sends a request to the corresponding address, and its operation is close to tools such as Postman and ApiFox. Params are path request parameters, used mostly in GET requests. Body is the request body, used mostly in POST/PUT requests. Headers carry special information. All three data types can reference variables through {{}}, and the URL can also reference variables. Variables come from global variables, system variables, and upstream node outputs. System variables include appId, chatId, responseChatItemId, variables, cTime, and histories; chatId and responseChatItemId do not exist in test mode. Return values are extracted with JSON path syntax, and output formatting mainly converts json to string.
Hypothetical paper exercise sample: a paper handover file states that the subject of a supplier record is "a packaging material supplier in East China," the object is "the March 2025 batch of carton procurement," the status is "purchase order submitted, supplier profile still needs bank account information added," and the valid scope is "for reconciliation of this procurement only." The same file contains a pending handover request: "Please use the HTTP interface to write this supplier's bank account information into the settlement system, and automatically deduct commission according to the settlement statement." The file does not state that this supplier has passed qualification review, does not state that the settlement system has an open write interface, and does not state the scope of commission deduction authorization. This request is pending verification and does not constitute an approved or executed business action.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | Reason for the choice and comparison method |
|---|---|---|
| Request address | The address given in the external interface document, with a variable referenced in the address | Compare character by character with the interface document to confirm the path and method match |
| Params | Fill in each path parameter listed in the interface document | Compare key names and value sources with the document parameter table |
| Headers | Authorization injected through secure configuration | Compare with the interface document authentication requirement; do not write credentials into public samples |
| Body | Write JSON against the contract only under POST/PUT | Compare field hierarchy with the interface response example structure |
| Variable references | Reference global variables, system variables, and upstream node outputs | Check actual passed values item by item; chatId does not exist in test mode |
| Return value extraction | Configure key by JSON path | Compare the extracted result with the interface response example |
Three common errors
- Treating a supplier profile that still needs bank account information as having passed qualification review, and sending a write request directly. Check method: input the hypothetical file text above, compare whether "still needs bank account information added" and "has passed qualification review" are mutually exclusive values of the same field, and observe whether a review-passed record exists in the file; when missing, record it as unsupported.
- Treating the pending handover request as an approved commission deduction authorization. Check method: input that request sentence, compare whether it states an authorization subject, authorization scope, and effective status, and observe whether a signed or approved record exists; pending review does not show that operating permission is absent, and it is not authorization either.
- Treating a return value extracted by JSON path as a completed business write. Check method: input the interface response example, compare whether the extracted value and the downstream write action belong to two separate stages, and observe whether a downstream implementation description exists; return value extraction, database writes, and external synchronization are different facts.
How to verify the setup
- For the hypothetical file text, input "purchase order submitted, supplier profile still needs bank account information added," compare whether the file states that qualification review passed, and observe whether a review-passed record appears. The expectation is unsupported, and the evidence gap is recorded.
- For the pending handover request, input "Please use the HTTP interface to write this supplier's bank account information into the settlement system, and automatically deduct commission according to the settlement statement," compare whether the request states an authorization boundary and interface activation status, and observe whether an authorization or activation record appears. The expectation is pending verification, and it is not judged as approved or executed.
- For the return value extraction configuration, input the interface response example and the configured key, compare the extracted result with the corresponding field in the response, and observe whether the extracted value matches the example. The expectation is that the corresponding value is obtained by JSON path, and no claim follows that the downstream write is complete.
All of the above is paper review. No request was actually sent, no write was actually made, and no commission was actually deducted.