# Sense (Sense Talent Labs, Inc.)

> AI-powered talent engagement and recruiting automation for staffing firms and enterprise talent-acquisition teams. Sense publishes one public API: a partner REST API that synchronizes applicant-tracking-system data into the Sense platform to drive workflow automation, plus a Write-back specification defining the events Sense pushes back to a customer endpoint.

Generated by API Evangelist from the provider's published surface on 2026-08-26. Sense does not serve an llms.txt of its own (probed https://www.sensehq.com/llms.txt -> 404 and https://developer.sensehq.com/llms.txt -> 403).

## Access model

Partner/customer only. Credentials are OAuth 2.0 client_id/client_secret pairs issued manually by the Sense team and bound to a single agency tenant. There is no self-serve signup, no sandbox, no trial, and no way to obtain a key without a commercial relationship. There is no scope model — a credential carries full read and write access to every entity type in its tenant.

## API

- [Sense API](https://developer.sensehq.com/): Partner REST API, OpenAPI 3.0.2, 52 operations across 10 entity types. Production base https://partner-api.sensehq.com/v1
- [OpenAPI definition](https://developer.sensehq.com/): published inline in the developer portal (a Redoc page); no standalone spec URL is served
- Token endpoint (production): https://partner-auth.sensehq.com/oauth2/token — OAuth 2.0 client_credentials, 300-second bearer JWT, caching mandatory

## Entities

Candidate, Placement, InternalUser, JobOrder, Company, ClientContact, Appointment, Submission, Certification, Lead. Each supports batch upsert (POST, max 500 items / 256 KB compressed), single fetch (GET /{entity}/{id}), partial update (PATCH /{entity}/{id}), and dropdown value management (GET/PUT /{entity}/possible-values/{fieldName}). Candidates additionally support resume upload (POST /candidates/{id}/resume, max 4 MB).

## Semantics an agent must know before writing

- POST is UPSERT and is a WHOLE-ENTITY REPLACE keyed on the caller-supplied `id`. Fields omitted from the body are CLEARED, not preserved. Use PATCH for partial updates.
- `id` is the primary key from the CALLER's system and is not managed by Sense.
- Writes are accept-then-enqueue. A 201 means the batch was queued, not persisted; expect roughly 30 minutes before data is visible. Do not treat a 404 on immediate read-back as a failed write.
- There is no DELETE method. Deletion is soft, expressed by sending the entity with `is_deleted = true`. No restore operation and no retention window are documented.
- There are no list/collection endpoints, so ids cannot be discovered through the API — they must already be known from the source system.
- Sync order matters: internal-users, candidates, client-contacts, companies, job-orders, submissions, placements, leads, certifications, appointments.
- Datetimes are ISO 8601 and strictly validated; an unparseable value rejects the whole update with 400.

## Errors

Custom JSON envelope `{ errors[], warnings[] }`, each item carrying entity_id, message and path. Not RFC 9457. Declared statuses: 400 (validation), 404 (entity not found, reads only), 413 (payload too large). 401, 403, 429 and 5xx are NOT declared anywhere in the contract.

## Events (Write-back API)

Outbound only, and inverted from the usual pattern: the CUSTOMER operates the receiving endpoint and Sense POSTs to it. Ten event types — ENGAGE_SENT_EVENT, ENGAGE_EVENT_RESPONSE, MESSAGING_INCOMING_MESSAGE, MESSAGING_OUTGOING_MESSAGE, MESSAGING_DIGEST, CHATBOT_RESPONSE_SUMMARY, ENTITY_CREATE, ENTITY_UPDATE, ENTITY_DELETE, GENERIC_EVENT. Receiver must return HTTP 200 with an `id` in the body or the delivery is treated as failed and retried. Payloads are not signed. No AsyncAPI is published.

## Operations

- Status page: https://status.sensehq.com/ (Atlassian Statuspage; JSON API at /api/v2/summary.json)
- Changelog: published inline in the developer portal, dated, split by surface, 15 entries from 2021-07-16 to 2026-04-02
- No published SLA, no deprecation policy, no Sunset/Deprecation headers, no rate-limit response headers

## Not available

- No SDKs or client libraries in any language. The docs direct integrators to generate one with openapi-generator.
- No CLI, no Postman collection, no GraphQL, no gRPC, no SOAP/WSDL.
- No MCP server and no A2A agent card.
- No /.well-known documents on any host, including no OAuth 2.0 authorization-server metadata (RFC 8414) and no OpenID Connect discovery.

## Company

- [Website](https://www.sensehq.com/)
- [Pricing](https://www.sensehq.com/sense-pricing): published floor pricing from $500/month to $7,000/month, quote-based above that
- [Security](https://www.sensehq.com/security): TLS in transit, AES-256 at rest, annual penetration assessments, MFA. Security contact security@sensehq.com. Note the PCI DSS / SOC 1-2-3 / ITAR / NIST certifications named on that page are AWS's, not Sense's.
- [AI assurance dashboard](https://trust.warden-ai.com/sense/candidate-matching): third-party bias auditing of Candidate Matching by Warden AI, covering NYC Local Law 144, EU AI Act, Colorado SB 205 and California FEHA
- [Support](https://www.sensehq.com/support)
- [Blog](https://www.sensehq.com/blog)
- [Terms](https://www.sensehq.com/terms-and-conditions) | [Privacy](https://www.sensehq.com/privacy-policy) | [Subprocessors](https://www.sensehq.com/legal/subprocessors)