<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>E1 External API changelog</title><description>Reverse-chronological record of observable changes to the External API.</description><link>https://developer.api.estimateone.com/</link><language>en-au</language><item><title>2026-10-21 — Added</title><link>https://developer.api.estimateone.com/reference/changelog.html#2026-10-21</link><guid isPermaLink="true">https://developer.api.estimateone.com/reference/changelog.html#2026-10-21</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;All additive and non-breaking. &lt;strong&gt;No action is required&lt;/strong&gt;; existing integrations keep working unchanged.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Added&lt;/code&gt; — Speci-finder results take a &lt;code&gt;createdSince&lt;/code&gt; query parameter (RFC 3339, inclusive) that returns only projects added on or after that instant, ordered by &lt;code&gt;createdAt&lt;/code&gt;, 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 &lt;a href=&quot;https://developer.api.estimateone.com/guides/incremental-crm-sync.html&quot;&gt;Incremental CRM sync&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Added&lt;/code&gt; — Each project carries &lt;code&gt;createdAt&lt;/code&gt;, when it was added to E1 (RFC 3339, UTC).&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Added&lt;/code&gt; — Each tender carries the builder’s &lt;code&gt;description&lt;/code&gt; (plain text) and the estimated construction dates, &lt;code&gt;estimatedStartDate&lt;/code&gt; and &lt;code&gt;estimatedEndDate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Added&lt;/code&gt; — Each consultant carries &lt;code&gt;types&lt;/code&gt;, its disciplines on the project (e.g. &lt;code&gt;ARCHITECT&lt;/code&gt;, &lt;code&gt;ENGINEER_STRUCTURAL&lt;/code&gt;), so you can tell architects from engineers.&lt;/li&gt;
&lt;/ul&gt;</content:encoded><category>Added</category></item><item><title>2026-09-30 — Added, Deprecated</title><link>https://developer.api.estimateone.com/reference/changelog.html#2026-09-30</link><guid isPermaLink="true">https://developer.api.estimateone.com/reference/changelog.html#2026-09-30</guid><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Added&lt;/code&gt; — Speci-finder results are now served from &lt;code&gt;GET /api/tender/supplier/v1/companies/{companyId}/speci-finder/results&lt;/code&gt;. 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.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Deprecated&lt;/code&gt; — The previous path, &lt;code&gt;GET /api/supplier/v1/companies/{companyId}/speci-finder/results&lt;/code&gt;, is superseded. &lt;strong&gt;No action is required&lt;/strong&gt;: it keeps working indefinitely and returns identical responses. Its responses now carry &lt;code&gt;Deprecation&lt;/code&gt; and &lt;code&gt;Link: &amp;#x3C;...&gt;; rel=&quot;successor-version&quot;&lt;/code&gt; headers, and it is marked &lt;code&gt;deprecated&lt;/code&gt; in the OpenAPI spec. Move to the new path when convenient. See &lt;a href=&quot;https://developer.api.estimateone.com/reference/versioning.html#superseded-paths&quot;&gt;Superseded paths&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</content:encoded><category>Added</category><category>Deprecated</category></item></channel></rss>