From first form to a published wall.

1. Create an account and a project for your brand.
2. Create a collection form. Customize the questions, branding, consent wording, and optional reward, then publish it.
3. Share the form link, or invite customers by email from the form's Invites tab.
4. Review new submissions in Testimonials and approve the ones you want to show.
5. Publish a wall or create a widget and embed it on your site.

Forms collect a rating plus a written or video answer. Video can be recorded in the browser or uploaded; it is converted to web formats automatically, and you can retry processing from the testimonial page if it fails.

Invites. Paste up to 100 customers at a time, one per line, as email, Name <email>, or Name, email. Each person gets a personal link, reminders follow on the days you choose, and they stop once someone responds or unsubscribes.

Consent. Respondents choose whether their testimonial may be shown publicly. Only approved testimonials with public consent appear on walls and widgets.

Imports. Add testimonials manually or from a CSV file in Imports.

A wall is a hosted page at /your-project showing your approved testimonials. Pick a template, then choose testimonials automatically (by rating, type, or tag) or by hand. Additional walls live at /your-project/wall-slug.

Widgets show testimonials inside your own site: carousels, grids, marquees, rating badges, and floating popups or toasts.

Copy the snippet from a widget's Embed panel. It looks like this:

<div data-wol-widget="YOUR_WIDGET_ID"></div>
<script async src="https://walloflove.net/widget.js"></script>

To embed a collection form instead, use data-wol-form="your-form-slug". You can also use the web component <wall-of-love widget-id="…"></wall-of-love>. Widgets size themselves to their content; popups and toasts float in the corner you configured.

In Project settings → Domain, add a hostname such as love.yourcompany.com, create the CNAME record shown there with your DNS provider, then click Verify. Once the certificate is issued, your default wall is served at the root of that domain and other walls at /wall-slug.

Create a key in Integrations → API and send it as a bearer token. Keys are shown once; store them securely. A key acts with the permissions of the person who created it, inside its project only, and allows 1,000 requests per hour.

curl https://walloflove.net/api/v1/testimonials?status=approved&limit=25 \
  -H "Authorization: Bearer wol_live_…"

curl -X POST https://walloflove.net/api/v1/forms \
  -H "Authorization: Bearer wol_live_…" \
  -H "Content-Type: application/json" \
  -d '{"name":"Customer love","slug":"customer-love"}'

Responses are JSON: { data } on success, or { error } with a code such as INVALID_INPUT (400), INVALID_API_KEY (401), PRO_PLAN_REQUIRED (402), FORBIDDEN (403), …_NOT_FOUND (404), SLUG_TAKEN (409), or RATE_LIMITED (429). Lists page with limit and the nextCursor you get back as cursor.

Connect Claude, ChatGPT, or any assistant that supports remote MCP servers to https://walloflove.net/mcp. Sign in, pick a project, and choose what it may do: read approved public proof (always), see the whole workspace, make changes, or email customers invites. MCP is included on every plan, and you can revoke a connection anytime under Integrations → MCP.

With workspace access, an assistant can use the same operations as the REST API, except that respondents' email addresses are never shared with it:

get_projectget_overviewget_analyticslist_testimonialsget_testimonial_detailscreate_testimonialupdate_testimonialapprove_testimonialunapprove_testimonialrestore_testimonialdelete_testimoniallist_trashadd_testimonial_tagremove_testimonial_tagupdate_tagdelete_taglist_formsget_formcreate_formupdate_formpublish_formclose_formdelete_formlist_form_submissionsadd_form_questionupdate_form_questiondelete_form_questionreorder_form_questionsset_form_rewardlist_form_invitessend_form_inviteslist_all_wallsget_wallcreate_wallupdate_wallpublish_wallunpublish_walldelete_wallget_widgetupdate_widgetdelete_widgetget_brand_kitupdate_brand_kitlist_import_sourcessync_import_source

Add an HTTPS endpoint in Integrations → Webhooks (Pro) and choose events: testimonial.created, testimonial.updated, testimonial.approved, testimonial.deleted, form.submission, form.published, and wall.published. Failed deliveries are retried with backoff.

Each request carries x-wall-of-love-event, x-wall-of-love-delivery, and x-wall-of-love-signature: t=TIMESTAMP,v1=HEX. To verify, compute HMAC-SHA256 of TIMESTAMP.RAW_BODY with your signing secret and compare it to v1.