Digest and notification settings

Prokure sends a daily digest of matched opportunities and, separately, alerts when an opportunity you have seen is amended. Both are configurable per account, from the portal’s Prok Settings page or through the API.

curl "https://app.prokure.ca/api/v1/settings/notifications" \
  -H "Authorization: Bearer $PROKURE_API_KEY"

Reading requires the settings:read scope; changing requires settings:write. A PATCH takes any subset of the writable fields and returns the full resource:

curl -X PATCH "https://app.prokure.ca/api/v1/settings/notifications" \
  -H "Authorization: Bearer $PROKURE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"digest_days":[1,2,3,4,5],"digest_hour":8,"digest_tz":"America/Toronto"}'

Schedule

Field	Meaning
digest_days	ISO weekdays (1 = Monday … 7 = Sunday). An empty list pauses the digest.
digest_hour	Hour of the day, 0–23, in digest_tz.
digest_tz	An IANA time zone name such as America/Vancouver.

The response also carries last_digest_sent_at and next_digest_at. next_digest_at is null when no send is scheduled — normally because the digest is paused. Matches keep accumulating while the digest is paused; the best of them, up to your cap and floor, are included the next time it sends, and the rest, except grouped duplicates, appear in Opportunities as screened.

What the digest includes

Field	Meaning
digest_min_score	Lowest match score included in the email, 0–100.
digest_max_items	Maximum number of opportunities in one email, 3–15.

Matches the digest considered but did not email — below the floor, beyond the cap, or ruled out by your decision rules — appear in your Opportunities list flagged as screened (a grouped duplicate is not listed at all), and the email’s footer tells you how many were left out by your floor and cap. The cap tops out at 15 because Gmail clips messages above roughly 102 KB, which a longer digest would exceed.

Duplicate listings

The same tender is often published on more than one source. Prokure groups duplicate listings of the same opportunity so only one appears, in the digest and in your Opportunities list alike: the portal’s Opportunities page and GET /api/v1/opportunities leave the other copies out under every filter, sort, status, archive view and page.

Listings are grouped in two ways:

• By solicitation number. Listings that share a solicitation number are grouped. A solicitation number is matched within its buyer’s identity: different buyers using the same number are not treated as one opportunity on that number alone.
• By title, buyer and closing date. Listings whose title, buyer and closing date all match are grouped. The comparison ignores letter case, punctuation, accents, HTML entities such as &, and a municipal prefix such as “City of” on the buyer’s name. A matching title does not group two listings that carry different solicitation numbers.

The listing from the tender’s originating source is preferred over a republished copy.

Grouping does not delete the underlying listings. A grouped copy’s own link, such as the one in an older digest email, still opens it, and GET /api/v1/opportunities/{id} with its id still returns it.

Recipients

notification_emails holds up to 10 addresses. Addresses are stored lower-cased and de-duplicated. When the list is empty, the digest goes to your account’s contact address — the response’s effective_recipients shows exactly who will receive the next one.

Receiving notifications does not grant permission to instruct Prok by email. Email-agent access is provisioned separately by the Prokure team; changing notification_emails does not grant or revoke that access. Disabling a portal member also prevents that member from using Prok by email, even if their address remains on the notification list.

Revoking agent access does not unsubscribe an address from notifications. When offboarding someone, also update the notification recipients and verify effective_recipients, including the contact-address fallback.

For an address authorized to act for more than one company, reply to that company’s existing Prok email thread. A new message without a company-bound thread is rejected when the sender’s company cannot be determined uniquely.

Delayed email processing

Accepting an incoming email for background processing does not mean its requested action has finished. Temporary queue failures can delay processing; the pending handoff is retained for retry. If a reply remains unhandled, contact the Prokure team with the original message’s date and subject before repeatedly sending it again. A fresh email is a new request, not necessarily a retry of the same action.

Digest delivery recovery

The digest keeps a saved delivery record so a temporary failure while recording a successful send does not require sending the email again. Retries reuse the same saved message rather than rebuilding it with different content.

Recovery is checked separately from your next scheduled digest day. Pausing or changing the schedule prevents new scheduled digests under the old schedule; it does not cancel a saved delivery already awaiting recovery.

When the email provider’s result remains uncertain, automatic retries are limited to 23 hours from the first attempt, within the provider’s 24-hour duplicate-protection window. After that, the Prokure team must reconcile the delivery before another digest is sent. This can delay a digest; it is not a guarantee that email can never be duplicated. Changes to recipients or opportunity availability can also require review of an unresolved attempt.

Finishing an older digest does not overwrite opportunities you archived or whose match results changed while that digest was being processed.

Amendment alerts

amendment_notification_policy decides when an amended opportunity earns an email:

• all — any opportunity that appeared in one of your digests and still meets your current minimum score.
• positive_only — only opportunities you responded to positively: agreed with in the portal, replied “interested” to, or requested a draft for.
• none — no amendment emails, including alerts that a draft in progress was invalidated.

Whatever the policy, amendments are still tracked and the opportunity is re-scored; the setting only governs email.