Skip to main content

Technical Changes

Information for developers and API users about what's changed, and what's planned.

Written by James Scholes

This article contains technical details on notable changes to underlying processes, automations, data structures and API calls for sheepCRM. It is also where we will announce upcoming changes which may affect any custom integrations or workflows.

If you need any further details on any of the changes please contact us via support.

Upcoming changes

Any planned changes which you may need to be aware of will appear here. Please check back regularly.

ETA Nov 2026: sheepApp registration (POST /api/v1/{flock}/user/register/): calls to this endpoint will need a valid security check token (Cloudflare Turnstile) in a captcha_token field. sheepApp and the sheepCRM sign-in and registration pages (auth.sheepcrm.com and oauth.sheepcrm.com) send one for you, so no change is needed there. Calls made with the credentials of a sheepCRM user of the same flock don’t need a token.

If you have a custom integration that registers sheepApp users without sheepCRM user credentials, please contact us via support before 14 November so we can help you keep it working.

NB: user/preregister/ endpoints may also need a captcha_token. Please also let us know if you are POSTing to this API endpoint.

  • ETA Nov 2026: Google Wallet membership cards: members using Android will be able to add their membership card to Google Wallet from sheepApp, alongside the existing Apple Wallet card. A saved Google card is marked as expired when the membership is no longer active or is deleted, and reactivated if the membership becomes valid again.

  • ETA Nov 2026: Membership cards for linked members: a new flock setting, membership_linked_member_cards (off by default), gives each person linked to a membership a card in their own name, showing “Member: ”. This applies to the Apple and Google Wallet cards, the PDF card and the QR verification page. Card links for a linked person carry person and person_signature parameters, and links that have been altered are refused.

  • ETA Nov 2026: Custom field yes/no values: yes/no (boolean) custom fields (extensions) will be stored as lowercase "yes" or "no" strings, and existing values such as "Yes" will be converted. If your integration reads or writes yes/no custom fields, compare without regard to case, or use the lowercase values.

  • ETA Dec 2026: Receipt PDFs: Close the same gap where "letterhead images" are not used for Receipt PDFs. This change will also affect links from sheepApp, and prevent unauthorised users from downloading another member's receipt.

November 2026

  • Invoice PDFs: Close a gap where Invoice PDFs use the "flock logo" image even if a "letterhead image" has been provided. Letterhead will now always be used for generating Invoice PDFs.

October 2026

  • sheepApp registration: provenance. When a registration or preregistration creates a new contact, the contact now gets a provenance record showing where the sign-up came from (for example “sheepApp registration via app.sheepcrm.com”). Existing contacts matched by email address are unchanged.

  • Registration pages on auth.sheepcrm.com and oauth.sheepcrm.com: to protect against an increase in spam sign-ups, both pages now run an invisible security check. Most users will not notice a difference; a few may be asked to tick a box before the Register / Create account button becomes available. Registrations submitted without completing the check are refused.

  • White-label sheepApp users: links from Alpine to Events and Forms will now use your white-label domain rather than defaulting to app.sheepcrm.com

  • Courses:

    • New endpoint: enrol a contact on a course. POST /api/v2/{flock}/person/{uid}/courses with a course (URI or uid) and an optional payment_ref. Returns 201 when the contact is enrolled and 200 if they were already enrolled. Needs a sheepCRM user with permission to create tickets.

    • Self-service course enrolment: no duplicate tickets. Enrolling on a course you’re already enrolled on now returns 200 with ticket: null instead of creating a second ticket.

    • Course tickets in event statistics. Course enrolment tickets no longer count towards a contact’s first, last or next event, or their past event count. They’re counted in a new course_count instead.

  • Bulk email status. A bulk email that runs out of time is now marked failed, rather than staying at rendering. Bulk emails whose template doesn’t use quotes no longer load each recipient’s quotes and invoices, so large sends are much faster.

  • Direct Debit renewals without a mandate. A self-service renewal that relies on an existing Direct Debit mandate is now refused with an error if the contact has no active mandate. Previously the renewal was created but could never be collected.

  • Segment-restricted users. Users whose access is limited to a segment no longer get “Unauthorized” when opening booking notes and tasks.

  • Ticketing API. Requests for a flock that doesn’t exist now return 404.

  • Custom field metadata endpoints. The schema fields endpoint (/internal/v2/{flock}/schema/{resource_type}/fields) now requires authentication. The custom field options lookup (/ext/v2/{flock}/extensions/fields/{extension}/{field}/lookup/) now returns 404 for a field that doesn’t exist on the extension.

September 2026

  • Events - Tighter definition of a ticketed third-party event when created by API calls/webhooks from another box office:

    • If a booking record has:

      • booking_type: 'third_party'

      • ticketed_event: True

      • controller: <any string>

    • the Event detail view will show a summary of ticket purchases over time

    • the Event detail view will provide access to Orders and Attendees

    • the Event will NOT allow tickets to be added from within the sheepCRM UI

    • sheepCRM will warn users when editing the configuration that this is a third party event, as changes made from within sheepCRM will likely not be reflected in the third party box office
      ​
      Please update your custom integrations to match the above behaviour for consistent access to Orders and Attendee information within sheepCRM Alpine

  • Segments - Extend available resources for segments to also include evidence - no front-end table view but this can be used to build segments for exports

August 2026

  • Available fields in segments/contact directory: extended to include support for more group fields including groups_accepted, groups_applied, groups_submitted, groups_rejected

  • Contact Mapreduce: A change has been made to the main contact mapreduce when processing form_responses.

    • Previously form_fields would be added as a simple key:label pair

    • Going forward form_fields contains a rich dictionary for each question:

      "form|1234|5678|910": {
      "label": "Form > Name > Section > Question",
      "type": "select-from-list",
      "choices": [
      "Red",
      "Green",
      "Blue"
      ]
      }

  • SchemaFields: A parallel change has been made to the SchemaFields GET call to correctly process form_fields after the change above

  • Membership selfservice call (/api/v1/{flock}/user/hosted/membership/{uid}/): Changed from using membership_type when fetching plan details (for renewal) to preferring next_membership_type if set. This fixes an issue where membership joining_fee could be incorrectly applied during a renewal with a plan change.

  • Fieldset exports: form fields in exports will now show their label rather than the raw field UID

July 2026

  • Events: booking.uncancel() action will now set status to "draft" rather than "pending", bringing states in line with expectations for events managed in sheepAlpine

  • Bulk SMS: SMS messages are now queued and sent asynchronously to avoid a timeout issue with larger segments.

Did this answer your question?