datawebotExtraction guide
Choose an API or public extraction
Match the access method to the data you are authorized to use.
01 / INPUTRequired fields + source ownership
02 / YOUR WORKFLOWCheck access, coverage and scope
03 / OUTPUTA documented retrieval choice
Keep the right fields.
Workflow field map| Field / step | Input | Rule |
|---|---|---|
| Merchant API | Authorized store credentials | Useful when the owner can grant access. |
| Public source | Public page or reviewed feed | Fields depend on what the source exposes. |
| Export | Authorized existing dataset | Check age, scope and reuse conditions. |
Before you use the output
Choose based on needed fields and access, not the word API alone. datawebot's API manages extraction; it does not grant access to a merchant's private data.
Check one record first.
Start with the smallest useful scope. Compare the returned record with its source, confirm variant identity and inspect missing fields before applying the mapping to a larger dataset.
Keep extraction warnings and the retrieval timestamp with downstream output. When a required field is missing, leave it unresolved or return to the source; do not fill it from an assumption.