PLATFORM ACCESS · FOR DEVELOPERS & INTEGRATORS
Every specification and datasheet on SynC is addressable data behind a REST API. API keys carry exactly the permissions you grant, and reads can be pinned to a published revision. The reference is public, no login needed.
Scoped keys · JSON export · Revision-pinned reads
PART 1 · GENERAL
1.01
Construction requirements are published as documents for people, so anything downstream starts with a person extracting the data by hand.
1.02
Most integrations want an all-or-nothing credential. To read one project, a tool gets the keys to the whole account.
1.03
Send a PDF out for bid and you have no say over who has access to it or what tools read it.
1.04
On SynC you decide who has access and whether export is allowed. Software reads the record through the API with the permissions of the key you issued.
A specification is a database. SynC treats it like one.
PART 2 · PRODUCTS
2.01
Issue a key with exactly the permissions a tool needs. Read-only stays read-only. Revoke or rotate any key without touching the rest, and read its usage log.
2.02
Projects, standards, datasheets, revisions, comments: what you do to a project’s record in the browser, you can do over the API. The same model the application runs on, with a public reference. The API is still growing, and the reference is current.
Read the API reference2.03
Pull a project, or one datasheet, as JSON: field names, selected values, units, and the source revision’s fingerprint. Compact for machines, verbose for full provenance. Clause prose stays in the PDF, not the JSON.
2.04
Request data as of any published revision, not only the latest. A quote or a bid stays tied to the document set it was built against.
2.05
Your own tools read specs and pull scope through the API with the permissions of the key you gave them.
2.06
Rate limits are reported on X-RateLimit headers. A key whose owner belongs to a company gets a higher limit than a free account. Write the retry logic once.
PART 3 · EXECUTION
STEP 01
Create an API key from your account and grant only the scopes the tool needs.
STEP 02
Read projects, standards, and datasheets as JSON, pinned to the revision you name.
STEP 03
Post line-item responses back through the same API, on the exact requirement.
Sign up free and issue your first key, or read the reference first. No login needed.