Skip to content

Builder API

The Builder API covers the work a builder does on E1: the projects they run, the packages they break that work into, and the drawings and specifications they issue to the market.

Where the Supplier API answers “what work is out there for me?”, the Builder API answers “what am I putting to market, and what have I issued?”. They are separate surfaces with separate scopes — an integration usually needs one or the other, not both.

Open the live API reference

https://api.dev.ascension.estimateone.com/api/tender/builder/v1/companies/{companyId}

Every endpoint is scoped to a company you are registered against. companyId is the E1 company account number, the same identifier the Supplier API uses. See Environments for the host in each environment and Versioning for what tender means in that path.

The examples throughout these pages refer to that host as $E1_API_BASE, alongside the E1_* variables from Make your first call. For this environment:

Terminal window
export E1_API_BASE="https://api.dev.ascension.estimateone.com"

Every request needs the external-api/access scope, a bearer token, and the x-e1-client-id header. Beyond that, each endpoint requires one capability scope:

ScopeGrants
companies/readList the companies your application is registered against.
projects/readRead projects.
projects/writeUpdate project details.
packages/readRead the packages on a project.
packages/writeCreate, update and delete packages.
documents/readRead project documents and addenda.
documents/writeAdd, replace and remove documents, run upload jobs, and start, rename and cancel addenda.
trade-disciplines/readRead the trade discipline list used to classify packages.
invitations/readRead the invitations sent for a package and the responses to them.
invitations/writeSend and manage the invitations for a package.
quotes/readRead the quotes received for a package.
quotes/writeCreate and update quotes.
address-book/readRead the companies and contacts in your address book.
address-book/writeAdd and update the companies and contacts in your address book.

Scopes imply the ones they depend on — packages/read also grants projects/read and trade-disciplines/read, for instance — so you only need to request the most specific scope for what you do. See Authorization for how scopes are granted.

Projects

List, read and update the projects a builder runs. Projects →

Documents

The drawings and specifications issued on a project. Documents →

Addenda

Group document changes into one issue. Addenda →

Invitations

Who you invited to quote, and how they responded. Invitations →

Quotes

The quotes you received, with their files, notes and revisions. Quotes →