Skip to main content
The Feedback Management API lets you collect feedback from your customers by email. You design a reusable email template, then send a campaign to a list of recipients. Each email links to one of your feedback forms, and the responses you collect feed back into Partoo’s Feedback Management.

Prerequisites

Before sending feedback emails, ensure you have:
  • A valid API key with access to Feedback Management.
  • At least one feedback form configured for your organization. The campaign links recipients to this form.
  • A sender email whose domain is authorized for your organization and validated for email sending. Contact your Account Manager if you are unsure whether your domain is set up.

How sending works

A feedback email campaign ties together three things: an email template (how the email looks), a feedback form (where responses are collected), and a recipient list (who receives it). Validation is all-or-nothing: if the sender email or any recipient fails validation, the entire campaign is rejected and no emails are sent. The response body details every error so you can fix the list and retry.

Step 0 — Create an email template (optional)

This step is optional. Most teams design their templates visually with the WYSIWYG editor in the Partoo Web app. If you already have a template, skip to Step 1.
A successful response returns 201 Created with the template’s id. See the Create an email template API reference for the full field reference.

Step 1 — Get your email template ID

Templates built in the Partoo Web app are available to the API. List your organization’s templates to find the id you want to use.
See the List email templates API reference for the full response schema and pagination options.

Step 2 — Get your feedback form ID

Each campaign links recipients to one feedback form. Search your organization’s forms to find the feedback_form_id you want to use.

Step 3 — Get campaign requirements

Before sending, call the requirements endpoint with your feedback_form_id and template_id. It returns the exact recipient fields and template variables your payload must include, so you know which keys to provide for every recipient.
A typical response:
  • recipient_fields: Recipient-level fields supported by the send endpoint.
  • variable_fields: Template variable names each recipient must provide under variables (sorted alphabetically). In the example above, every recipient must supply first_name and store_code.
See the Get campaign requirements API reference for the full schema.

Step 4 — Validate with a dry run

A dry run uses the same send endpoint (POST /feedback/campaign/send) with is_dry_run: true. It validates the sender and recipients without sending any emails — the safest way to confirm your list is correct before a real send.
The send endpoint returns 200 OK for both accepted and rejected campaigns. Always inspect the status field rather than relying on the HTTP status code.
  • status: "accepted" — validation passed (emails enqueued, or skipped because is_dry_run was true).
  • status: "failed" — sender or recipient validation failed; no emails were sent. The error fields describe what to fix.
See the Send a feedback email campaign API reference for the complete request and response schema.

Step 5 — Send the campaign

Once the dry run returns status: "accepted", send for real by setting is_dry_run: false (or omitting it — it defaults to false). A successful response:
Batch limit: a single call accepts at most 1000 recipients. For larger lists, split them into batches and call the endpoint multiple times.
See the Send a feedback email campaign API reference for the complete request and response schema.