Skip to content

Changelog

This page records observable changes to the External API. Entries are added at release time only — no in-flight or unreleased work is published here. If you’re tracking an integration against a specific behaviour and need an early heads-up, contact support@estimateone.com.

See Versioning for what counts as a breaking change.

To be notified of new entries, subscribe to the RSS feed.

When adding an entry:

  • Group by date (ISO YYYY-MM-DD), reverse-chronological.
  • Tag each item as Added, Changed, Deprecated, Removed, Fixed, or Security.
  • Describe the change from the partner’s perspective — not the internal implementation.
  • Call out any required action on the partner’s part.

All additive and non-breaking. No action is required; existing integrations keep working unchanged.

  • Added — Speci-finder results take a createdSince query parameter (RFC 3339, inclusive) that returns only projects added on or after that instant, ordered by createdAt, oldest first. Use it to pick up new projects between full syncs. It matches on the project’s creation, so new tenders on existing projects still need a full sync. See Incremental CRM sync.
  • Added — Each project carries createdAt, when it was added to E1 (RFC 3339, UTC).
  • Added — Each tender carries the builder’s description (plain text) and the estimated construction dates, estimatedStartDate and estimatedEndDate.
  • Added — Each consultant carries types, its disciplines on the project (e.g. ARCHITECT, ENGINEER_STRUCTURAL), so you can tell architects from engineers.
  • Added — Speci-finder results are now served from GET /api/tender/supplier/v1/companies/{companyId}/speci-finder/results. API paths are now namespaced by the E1 platform serving them, so that each platform’s surface is distinct as more are added. The response shape is unchanged.
  • Deprecated — The previous path, GET /api/supplier/v1/companies/{companyId}/speci-finder/results, is superseded. No action is required: it keeps working indefinitely and returns identical responses. Its responses now carry Deprecation and Link: <...>; rel="successor-version" headers, and it is marked deprecated in the OpenAPI spec. Move to the new path when convenient. See Superseded paths.