“Trust in the Lord with all your heart, and do not lean on your own understanding.”

— Proverbs 3:5
Start free trial

title: WordPress description: How to receive DailyLife content on a WordPress site today. public: true reviewed: 24082026

WordPress

There is no DailyLife WordPress plugin, and no date for one. This page previously said one was planned, which is a fair description of an intention and a poor description of what you can install today. If a plugin is built, this page will describe it and how to get it. Until then, the supported route is the webhook, and it works with WordPress today.

What to build instead

Your site receives approved gallery posts, events and vacancies as a signed HTTP request. On WordPress that is a REST route in a small custom plugin or in your theme's functions file. It needs to do four things:

  1. Verify the signature before doing anything else, and reject the request if it does not match. The website webhook page gives the exact scheme and a worked example.
  2. Check whether you have seen this delivery before. Each request carries a delivery identifier, in the body and in a header. Store the ones you have processed and discard repeats, because a retry after a network timeout looks identical to a fresh publication.
  3. Download the images on receipt. Image links in the payload are signed and expire after 24 hours. Fetch them and store them in your own media library rather than linking to them, or the pictures will disappear from your site the next day.
  4. Map the content to a post type. Gallery entries, events and vacancies each arrive with their own fields, so most implementations map them to three custom post types.

Two things to get right

Return a success status only once you have actually stored the content. If you acknowledge the request and then fail, we have no way of knowing, and the retry that would have fixed it never happens.

Respect the withdrawal case. Content can be held back between approval and delivery, most often because someone in a photograph withdrew their consent. That means a post you were expecting may never arrive, and it is correct that it did not. It also means content already published on your site is not automatically removed: if you are told a consent has been withdrawn, take the post down.

Full request format, headers, signature scheme and field-by-field payload: website webhook.