The accountability layer on top of your existing operations stack
Jobs can start anywhere; evidence lives here. Keep your CMMS, ticketing tool, or ERP for running the work. API access and a job-sync webhook are on our roadmap, landing on Enterprise first, so completed jobs will flow into Evalystar and trigger the evaluation the moment the work is done.
From closed work order to scored evaluation, automatically
Your external system will post jobs to Evalystar's inbound webhook as they are created, updated, and completed. When a job arrives marked completed, Evalystar will treat it exactly like a job closed internally: the right reviewer receives an evaluation request by email and rates the work in seconds, without logging in. The operational system stays your source of truth for the work; Evalystar becomes the source of truth for how well the work was done.
Designed for admins who do not want surprises
Everything will be managed in-app by your admins: keys, scopes, revocation, and imports. No implementation project, no vendor involvement. Here is what the API is being built to do.
Admins create and revoke API keys in Security Settings, no support ticket required. Each key is scoped to the operations it needs, so a job-sync key cannot read your analytics or touch your users. Keys can carry an optional expiry date.
Push jobs from any external system into Evalystar over a single endpoint. Create a job when a work order opens, update it as it progresses, and mark it completed when the work is done. The job lands against the right vendor and site in your account.
A job marked completed through the API triggers the exact same flow as a job completed inside Evalystar: an evaluation request is sent the moment the job closes, and the reviewer rates the work from an email link with no account and no app install.
Moving off spreadsheets or another system? Import your sites, vendors, and users in bulk, through the API or directly in the app. Onboarding a 30-site portfolio does not have to mean 30 rounds of manual data entry.
Every key gets 200 requests per minute. Enough headroom to sync a busy portfolio in real time, with a hard ceiling that keeps one misbehaving script from affecting your account.
API keys are hashed before storage and never kept or displayed in plaintext after creation. If a key is exposed, revoke it in Security Settings and issue a new one; the old key stops working immediately.