> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# SimplifyVMS

> SimplifyVMS (Vendor Management & Sourcing): the API posture, publish target and field mapping composerID publishes a decision reference through.

This page records how composerID publishes into SimplifyVMS: the vendor's API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it.

SimplifyVMS (Simplify Workforce Inc., Jersey City) is a cloud-native VMS that runs contingent staffing, statement-of-work services procurement, direct sourcing, and credentialing and compliance in one platform, built for multi-country deployment. composerID treats it as a destination system of record: Intent Records are published onto its native requisition and SOW objects and the audit spine is kept, with tenant mapping validated in a customer sandbox because no public endpoint reference was found and the API is treated as customer-scoped.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Documented. Vendor documentation: gated (customer or SKU documentation). No developer portal is evident.

  No Intent ID carrier is claimed: no vendor-published source shows an API-writable field for it yet. The carrier is identified with the vendor or the joint customer before this destination is marked Carrier mapped. [How carriers are proven](/concepts/carrier-evidence).
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Authentication       | Customer-provisioned credentials.                                                                              |
| composerID publishes | Requisition (Contingent): Requisition via customer API                                                         |
| Back-sync            | Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule. |

## Vendor documentation

<Columns cols={2}>
  <Card title="SimplifyVMS: product site" icon="external-link" href="https://www.simplifyvms.com/" horizontal />

  <Card title="SimplifyVMS: integration platform" icon="external-link" href="https://www.simplifyvms.com/solutions/integration-platform/" horizontal />

  <Card title="Simplify Bridge (integration hub)" icon="external-link" href="https://integrations.simplifyvms.com/" horizontal />

  <Card title="Simplify Bridge: connectors" icon="external-link" href="https://integrations.simplifyvms.com/integration/connectors/" horizontal />

  <Card title="SimplifyVMS: services procurement and SOW" icon="external-link" href="https://www.simplifyvms.com/solutions/services-procurement/" horizontal />

  <Card title="Simplify Bridge: data integration in the VMS space (80+ systems)" icon="external-link" href="https://integrations.simplifyvms.com/resources/revolutionizing-data-integration-in-the-vms-space/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                                                                                                                                                                                         |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Customer-provisioned credentials. The vendor describes a documented API for custom integrations and Simplify Bridge connectors for packaged ones; the auth flow (OAuth 2.0 vs API key) is confirmed per tenant at onboarding.                                                                                                                                                                  |
| Style          | Vendor-documented API for custom integrations plus Simplify Bridge, a no-code connector layer with data mapping, transformation, conditional logic and error handling, which the vendor says has integrated across 80+ back-office systems (Workday, Oracle, ADP, SAP, Ariba, Coupa among them). No public endpoint reference was found, so it is treated as customer-scoped until onboarding. |
| Base URL       | Provisioned per customer tenant. No public base URL.                                                                                                                                                                                                                                                                                                                                           |
| Webhooks       | Not publicly documented. Simplify Bridge advertises real-time synchronisation between connected systems, so event or webhook options are confirmed per tenant; composerID plans poll-based reconciliation until then.                                                                                                                                                                          |
| Events posture | Polling                                                                                                                                                                                                                                                                                                                                                                                        |
| Rate limits    | Not publicly documented; set by the tenant integration agreement.                                                                                                                                                                                                                                                                                                                              |
| Objects        | Requisition (job), Assignment (the vendor's work-order terminology is confirmed per tenant), Worker, Timesheet and expenses, Statement of Work (fixed fee, recurring, time and materials, unit-based or hybrid; milestones, deliverables, SLAs and acceptance criteria), Supplier (tiered), Invoice                                                                                            |

## Publish target and field mapping

Each object below pairs the canonical intent fields with the destination's own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

<AccordionGroup>
  <Accordion title="Requisition (Contingent)" icon="arrow-right-left" description="Create the job / worker request">
    | Mapping                  | Detail                                                                                |
    | ------------------------ | ------------------------------------------------------------------------------------- |
    | Canonical to destination | role\_title, location, start\_date, end\_date, cost\_center, worker\_type, rate\_card |
    | Target                   | Requisition via customer API                                                          |
    | Requirement              | Tenant required                                                                       |
    | Notes                    | Requisition and job-distribution flow; supplier tiering is tenant configuration       |
  </Accordion>

  <Accordion title="Statement of Work (Services)" icon="arrow-right-left" description="Create the SOW record">
    | Mapping                  | Detail                                                                                                                                 |
    | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
    | Canonical to destination | scope, sow\_type, milestones\[], deliverables\[], budget, start\_date, end\_date, supplier                                             |
    | Target                   | SOW module via customer API                                                                                                            |
    | Requirement              | Tenant required                                                                                                                        |
    | Notes                    | sow\_type maps to the module's fixed fee / recurring / T\&M / unit / hybrid types; clause and template choice stays inside SimplifyVMS |
  </Accordion>

  <Accordion title="Assignment / work order" icon="arrow-right-left" description="Assignment lifecycle read-back">
    | Mapping                  | Detail                                                                                                                       |
    | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
    | Canonical to destination | worker\_id, dates, rate, status                                                                                              |
    | Target                   | Customer API (read)                                                                                                          |
    | Requirement              | Read only                                                                                                                    |
    | Notes                    | Back-sync into the intent timeline; poll-first until tenant events are confirmed. Vendor object name confirmed at onboarding |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                                                                                                                 |
    | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
    | Canonical to destination | intent\_id, intent\_version                                                                                                                            |
    | Target                   | Not established: no vendor-published source shows an API-writable field for the Intent ID                                                              |
    | Requirement              | Tenant required                                                                                                                                        |
    | Notes                    | SimplifyVMS publishes no API reference: only marketing pages. The carrier is identified with the vendor or the joint customer before any claim is made |
  </Accordion>
</AccordionGroup>

<Note>
  SimplifyVMS API documentation is customer-scoped; the public material describes the integration platform, not endpoints. composerID starts with the minimum viable mapping above and relies on tenant discovery (required fields, custom fields, SOW types, supplier tiers) to generate a working MappingProfile. Where a customer already runs Simplify Bridge, composerID publishes to the VMS directly and leaves Bridge to its existing HRIS/ERP feeds.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>