GEP (platform)
GEP SMART is a unified source-to-pay procurement platform. Reference docs are public, but working credentials and base URLs are provisioned per customer at onboarding. VMS Agent maps intent onto Requisition / RFX / Contract / Order / Invoice resources.
The public API facts VMS Agent's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.
| Authentication | OAuth 2.0. Client credentials are provisioned by GEP — there is no public self-service signup. 401 on unauthorized. |
|---|---|
| API style | REST (JSON) + SOAP + Bulk APIs + FTP/SFTP. GEP QUANTUM adds cXML / EDI-X12 / PIDX. |
| Base URL | api/{Resource}/{Action} e.g. api/Order/OrderDetails (fully-qualified host issued per tenant) |
| Objects | Requisition, RFX (sourcing), Contract, Order (PO), Invoice, Catalog; master data Suppliers / Category / Users |
| Events / webhooks | None documented. Request/response REST + Bulk + file exchange; status-update endpoints (OrderStatus, InvoiceStatus) for poll / push-status. |
| Rate limits | None published; defined per integration agreement. Bulk APIs handle high volume. |
“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary — especially around custom fields, approval flows and object extensions.
Deterministic mapping
Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).
Tenant discovery
VMS Agent can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.
Enrichment loop
If the target platform requires a field the Intent record doesn't yet have, VMS Agent emits an enrichment_request back to the intake layer.
An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.
| Object | Canonical fields | Platform target | Required status | Notes |
|---|---|---|---|---|
| Requisition Create the demand |
role_title, service_category, cost_center, dates | POST api/Requisition/... | Required | Convention: POST …Details / GET …All / PUT …Status |
| Sourcing event (RFX) Competitive services |
service_category, sow.summary, suppliers[] | RFX API | Tenant required | For competitively sourced services |
| Order (PO) Transact + back-sync |
po_lines, supplier, amount | POST api/Order/OrderDetails; GET api/Order/GetPurchaseOrders | Required | PUT api/Order/OrderStatus for back-sync |
Idempotency & drift — publish + reconcileExpand
Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, VMS Agent supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.
Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). VMS Agent is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.
How scanning works
High-level flow
What gets produced
Portable artefacts
Important — where this platform is tenant-definedExpand
No open self-service portal — base URL, tenant ID, sandbox and full auth specs are provisioned by GEP during onboarding. Two products: GEP SMART (source-to-pay) and NEXXE (supply chain); GEP QUANTUM is the platform layer.
Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.