What authentication does Vendo Public APIs use?

Vendo Public APIs support both Basic Authentication (publicKey:privateKey base64 encoded) and Bearer token authentication. Through Jentic, credentials are stored in the encrypted vault and injected at execution time.

How do I change an appointment status?

POST /appointment/{appointment_id}/status accepts status (won, lost, pending, canceled), result_name, result_reason_name, optional selected_quote_id, and enable_events flag. This updates the appointment status and optionally triggers events/webhooks.

What does pulling quotes forward mean?

POST /appointment/{appointment_id}/{appointment_type} pulls quotes from a previous appointment into a new change_order or second_measure appointment. It accepts quote_ids array and returns pulled_quotes and not_pulled_quotes with error details.

Can I import WCP quotes?

Yes. POST /import-quote accepts WCP quote ID or number, sellers, optional appointment data, and settings (apply_adders, replace_quote_if_exist) to create or update Vendo appointments with pending status.

How do I retrieve payment details?

GET /appointment/{appointment_id}/payment-details returns an array of successful payment objects for the appointment. This provides financial tracking for completed transactions.

Can I limit what my agent is allowed to do with the Vendo API?

Yes. Because you run Jentic One yourself, your own rules decide which Vendo operations and credentials the agent may use. Since Vendo carries the appointment id in the URL path (/appointment/{appointment_id}/...), you can pin the agent to a single appointment so it only reads that appointment's details, differences, and payment details and updates its status. You choose the operations it may call, so account-wide writes such as user creation stay off unless you explicitly grant them.