Enrich vendor
Triggers AI-powered vendor enrichment for an existing vendor. Runs one or more enrichment stages (invoice scan, web search) based on the scope parameter. Can automatically apply extracted payment acceptance info and vendor contact information to the vendor record, or return raw results for manual review. Contact Payabli to enable this feature.
Authentication
Long-lived API token sent in the requestToken header. See API token authentication.
OAuth2 Bearer access token from the client-credentials flow. See OAuth authentication.
Path parameters
Request
Enrichment stages to run. Valid values are invoice_scan and web_search. Stages run in order: invoice scan first, then web search. If the vendor becomes payout-ready after invoice scan, web search is skipped.
When true (the default), extracted data is automatically written to the vendor record. Only empty fields are populated, existing values are never overwritten. When false, the vendor record isn’t modified. In both cases, enrichmentData in the response contains the extracted results. Use false for UI flows where users review and confirm changes before applying them with the update vendor endpoint.
PDF invoice file, Base64-encoded. Required when scope includes invoice_scan.
Payment method to apply if enrichment can’t find payment details. Values are check, ach, or card.
When true, Payabli schedules an AI outreach call to the vendor if the enrichment stages return insufficient payment acceptance info. The call collects the vendor’s preferred payment method and contact email. This is the third enrichment stage and is opt-in at the org level. See the schedule outreach call endpoint for behavior and requirements.
Response
Response text for operation: ‘Success’ or ‘Declined’.
Code for the response. Learn more in API Response Codes.
Field not in use on this endpoint. It always returns 0.
Boolean indicating whether the operation was successful. A true value
indicates success. A false value indicates failure.