PLATFORM ACCESS · FOR DEVELOPERS & INTEGRATORS
Every specification and datasheet on SynC is addressable data behind a REST API. Integration 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
INTEGRATION KEY
quote-tool-prod
SCOPE
READ-ONLY
GET /api/projects/2841/datasheets?format=compact
Authorization: Bearer sync_k9…
HTTP/1.1 200 OK
X-RateLimit-Remaining: 119
{
"project": "Building 400",
"revision": 7,
"fingerprint": "f0d7ef311a02",
"datasheets": [ … ]
}PART 1 — GENERAL
Construction requirements are published as documents for people, so anything downstream starts with a person extracting the data by hand.
Most integrations want an all-or-nothing credential. To read one project, a tool gets the keys to the whole account.
AI agents are in every workflow now, and the documents they need are pages they can only guess at.
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: every entity by ID, every requirement by its clause address. The same model the application runs on, with a public reference. Paths are unversioned today (/api/, not /api/v1/), and we say so up front.
Read the API reference→2.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
Point your agent at SynC and it reads specs, answers questions, and pulls scope with the permissions of the key you gave it. No screen-scraping, no PDF parsing.
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 integration 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.
PART 4 — ON THE ROADMAP
PLANNED
Standards will carry decision-support notes (why one configuration over another) so an AI can help make a selection, not only read it back.
ON ROADMAP
The keys, API, and structured export are live, and teams can build on them today. Pre-built connectors for common configurators and ERPs come later.
Sign up free and issue your first key, or read the reference first. No login needed.