There is no Isimio API to learn
Isimio is built natively on Salesforce, so the API you integrate with is Salesforce's own: REST, Composite, Bulk 2.0, SOQL, the streaming APIs, all of it, running over your Isimio data.
If your team has integrated with Salesforce before, there is nothing new here. Same auth, same query language, same libraries, same middleware connectors. If they haven't, the guide below takes them from an empty sandbox to a working integration.
What you get on day one, without us building anything:
Four ways to connect
Most projects end up using two or three of them together.
You call Isimio
REST & Composite
Read and write on demand, authenticated with OAuth 2.0 as a permission-scoped integration user. A query returns 2,000 records a page and hands you a cursor for the next. Composite lets you create a timesheet and its shifts in one atomic call to ensure data consistency.
You call Isimio, at volume
Bulk API 2.0
Asynchronous CSV jobs. Use it past a few thousand records: payroll runs, invoice exports, the nightly sync. Perfect for large, asynchronous jobs.
Isimio calls you
Callouts on real events
We build to your endpoint and fire on the events that matter to you: a timesheet approved, a shift filled, a candidate cleared for compliance. Your credentials sit in encrypted platform config, managed by your admin and rotated without a deployment.
Something in between
iPaaS & automation
Run a private n8n or Windmill server and wire Isimio to 1,500+ apps yourself. Available as a managed add-on, or bring your own instance.
What our API is used for
Everything in Isimio sits behind a standard API, so all data points are potentially accessible. The below are common use-cases that are generally available:
Timesheets and shifts
The one everybody asks for. Pull approved billable time out for payroll and invoicing, or push worked time in from wherever you capture it. Planned, submitted and approved times are held separately, so an export can only ever pick up hours a human has signed off.
Candidates and workers
Sync people and their details either way. Ask us for an external ID field and you can upsert on your own reference, which means you never store our record IDs and your retry logic gets much simpler.
Clients and projects
Keep accounts, sites and engagements lined up with whichever system is your book of record.
Bookings and requests
Take shift requests from a client-side system and push confirmed bookings back out as they fill.
Compliance and documents
Surface compliance state and document expiry to an external credentialing or audit platform.
Finance and invoicing
Feed generated invoices and charges into your accounting stack. Some of it is file-based rather than API-based, Sage 50 included, and that is usually the right answer for finance.
More apps? No problem!
Native ATS connectors
If you run one of the Salesforce-native or other supported ATS platforms, the connector exists and there is nothing to build. Candidate data lands in Isimio's scheduling and compliance engine without anyone retyping it. These are managed by our team internally.
Salesforce AppExchange
The Salesforce AppExchange offers a variety of pre-built addons that can already work with some Isimio data. If you're interested in marketing and messaging tools, electronic contracts, or anything else, as the saying goes: there's an app for that.
Building an ATS or application that should talk to Isimio? See the software partner programme.
APIs built around security
For those who don't want to end up on the news for all the wrong reasons.
One app per connected system
Each integration gets its own credentials, allowing you to flip the switch and cycle credentials any time.
Least privilege by default
Choose from one of our pre-built permission sets or create your own.
Hard enforcement of permissions
If an integration user cannot see a field, it cannot be queried - enforced at the platform level.
Secrets live in config
Outbound credentials sit in encrypted Named and External Credentials. An administrator rotates them. No deployment needed.
Locked to your IPs
IP allowlisting per app lets you control where requests come from and at what times of day.
Everything is attributable
Event monitoring, login history and field history all come from the platform. US, UK, and EU data residency as standard.
Ready for the technical specs?
Learn how to integrate with Isimio using real examples, covering topics such as:
- →Registering and securing an external app
- →OAuth 2.0 JWT bearer and client credentials
- →Scoping an integration user so it can reach only what it should
- →Pulling timesheets by person, date range, project or client
- →Fetching shift data
- →Creating timesheets and shifts atomically
- →Reading and updating candidates and clients
- →Bulk API usage
- →Timezones
Note about our data model
Isimio covers a lot of ground and customers switch on very different parts of it. Most deployments carry their own custom fields and record types. On top of that, permissions decide what the API returns at all, so two integration users can query the same object and see different results. The guide covers common usecases and can be applied in the case of model customisations. For a functional description of our data model, please inquire about our partner programme and the technical resources available.
See Isimio for yourself
Book a 30-minute demo with a real person and see exactly how Isimio would work for your team.
No commitment required. A real person will confirm your demo within 24 hours.