Skip to main content
This page records how composerID publishes into GEP: 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. 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. composerID maps intent onto Requisition / RFX / Contract / Order / Invoice resources.
Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

GEP Tech Documentation portal

GEP SMART REST APIs index

Order (PO) API

Invoice API

​
API posture

​
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.
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.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.