The accountability layer on top of your existing operations stack
Evalystar is designed to sit on top of the operations stack a facility team already runs, not to replace it: the CMMS, ticketing tool, or ERP keeps dispatching the work, and Evalystar holds the evaluation and the evidence. Scoped API keys, an inbound job-sync webhook, and bulk import are on the roadmap and will land on Enterprise first, so a completed job will be able to trigger its evaluation automatically. They are not available yet.
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.
Common questions
Does Evalystar integrate with my CMMS today?
Not yet. Scoped API keys, an inbound job-sync webhook, and bulk import are on the roadmap and will land on Enterprise first. Until then, jobs and evaluations are managed in Evalystar directly.
Will I have to replace my CMMS or ERP?
No, and that is not the intent. Evalystar is designed to sit on top of the operations stack you already run: the CMMS, ticketing tool, or ERP keeps dispatching the work, and Evalystar holds the evaluation and the evidence.
What will the job-sync webhook do?
As planned, a completed job in your existing system will be able to trigger its Evalystar evaluation automatically, so the request reaches the reviewer while the work is still fresh. It is not shipped, so treat this as a roadmap commitment rather than a current capability.
Can I import my existing sites and vendors?
Bulk import for sites, vendors, and users is on the same roadmap. Talk to us if the import shape matters to your decision, since the roadmap is still open to influence.