The Elevate API

Integrate Elevate with the systems
you already run.

A REST API over your entire contingent workforce, requisitions, submissions, engagements, time and expense. The same API Elevate itself is built on, documented to OpenAPI 3.1 and scoped to one tenant per credential.

Request API access → See how it works
Contract
OpenAPI 3.1Machine-readable, versioned
Transport
REST over JSONNo SOAP, no flat-file drops
Isolation
Tenant-scopedEnforced server-side, per request
Track record
Two decades in productionAcross active customer programs
No second path

Built on the API our own product runs on.

Most vendor management systems bolt an integration layer onto the side of the product: a second, thinner path to the data, built later, tested less, and quietly behind on every feature the real application already has.

Elevate does not have a second path. Every screen in the product is a client of the same versioned REST API we publish to you. When a hiring manager opens a requisition in the browser, that page is making the call you would make. There is no capability the interface has that the API does not.

The practical consequence: the endpoints you integrate against are exercised continuously by every user of the platform, not only by the customers who happen to have built an integration.

Integration patterns

What you can connect.

Four patterns cover most of what enterprise programs ask for. Each maps to a set of endpoints in the published reference.

Requisition sync

Open roles from your HRIS or ATS become requisitions in Elevate, and status flows back as the program works them. No re-keying, no nightly CSV.

  • →Create and update requisitions
  • →Read status and approval state
  • →Manage supplier distribution

Candidates and submissions

Move candidates through the pipeline programmatically (submitted, interviewed, offered, engaged) and keep your system of record in step.

  • →Read and advance submissions
  • →Interview scheduling and feedback
  • →Offer state transitions

Worker and engagement data

The population your HRIS cannot see. Active engagements, start and end dates, assignments and classification, on demand rather than on a report cycle.

  • →Active engagement roster
  • →Extensions and completions
  • →Worker classification status

Time, expense and spend

Push time from the systems that already capture it, and pull the invoice detail your AP team reconciles against.

  • →Submit and read timecards
  • →Expense submission and status
  • →Invoice and spend detail (read)
The contract

Predictable requests.
Predictable responses.

Every endpoint takes and returns JSON in the same envelope, so your error handling is written once.

Request
# List open requisitions for your program
curl https://api.elevatesaas.com/v1/requisitions \
  -H "Authorization: Bearer $ELEVATE_TOKEN" \
  -G --data-urlencode "status=open" \
     --data-urlencode "pageSize=20"
Response · 200
{
  "success": true,
  "data": [
    {
      "id": 48213,
      "title": "Senior Data Engineer",
      "status": "open",
      "jobType": "conthire",
      "openings": 2
    }
  ],
  "pagination": {
    "page": 1,
    "pageSize": 20,
    "totalPages": 7,
    "totalCount": 134
  }
}
Authentication
Bearer token over TLS. Credentials are issued to an organization, not a person, so an integration does not break when an employee leaves.
Tenant isolation
Every credential resolves to exactly one client program. Scope is applied server-side on every query. There is no parameter that addresses another organization's data.
Response envelope
success, data, and pagination on every list response. Errors return success: false with a stable machine-readable code alongside the human-readable message.
Pagination
Page and page-size on every collection, pageSize up to 100, with total counts returned so you can size a sync before you run it.
Validation
Request bodies are schema-validated at the edge. A malformed request is rejected with the offending field named, not accepted and half-applied.
Rate limits
100 requests per 15 minutes on standard endpoints, 20 on authentication. Limits are published in response headers and raised for volume integrations on request.
Versioning
The version is in the path. Breaking changes ship as a new version: the one you integrated against keeps behaving the way it did.
Availability

What's available today.

We would rather tell you where this actually stands than have you find out during an implementation.

Live in production

The API itself

Running continuously as the backbone of the Elevate platform, across every active program. This is not a preview build or a parallel service.

Limited release

Direct customer access

Scoped credentials and the published reference are rolling out to named customers first, so we can shape the surface around real integrations rather than guesses. Client-side program access is available now, request access and we will scope your use case.

On the roadmap

Client libraries, webhooks, supplier access

Generated SDKs, outbound event webhooks, and credentials for supplier organizations are planned and not yet available. If one of them is the difference for your program, tell us, customer demand sets the order.

Tell us what you need to connect.

Send us the system on the other end and what has to move between them. We will tell you plainly whether the API covers it today, and if it does not, when it will.

Request API access → See ELEVATE Connect