recipe · 6 fieldstri-party agreement for solar installation
tri-party agreement for solar installation
extraction api.
Agreement between the consumer, the discom and the solar installer.
what it reads
the fields.
Rename any of them, drop the ones you don't need, or add the one your form asks for. Each comes back with the text it was read from.
| field | key | type | notes |
|---|---|---|---|
| Customer / firm name | customer_name | Name | — |
| Consumer number | consumer_number | Text | — |
| Address line 1 | installed_address_line_1 | Address | — |
| Address line 2optional | installed_address_line_2 | Address | — |
| Area code | installed_area_code | PIN code | PIN code |
| Installed capacity in kW | installed_capacity_kw | Number | — |
the apia tri-party agreement for solar installation in,
a tri-party agreement for solar installation in,
json back.
Publish the recipe as a workflow and send it files. Each field returns its value, a clean normalised version, its status, the page and the source text.
curl https://api.patrapi.com/v1/workflows/wf_triparty/extractions \
-H "Authorization: Bearer $PATRAPI_KEY" \
-F file=@triparty-agreement-solar.pdf{ "status": "completed",
"document_type": "triparty_agreement_solar",
"fields": {
"customer_name": { "value": …, "status": "present", "page": 1 },
"consumer_number": { "value": …, "status": "present", "page": 1 },
"installed_address_line_1": { "value": …, "status": "present", "page": 1 },
"installed_address_line_2": { "value": …, "status": "present", "page": 1 },
"installed_area_code": { "value": …, "status": "present", "page": 1 },
… 1 more
} }