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

# GEP

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

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.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0.                                                                                                     |
| composerID publishes | Requisition: POST api/Requisition/...                                                                          |
| Intent ID lands on   | `document` `customAttributes.intentId`, written into the destination record                                    |
| 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="GEP Tech Documentation portal" icon="external-link" href="https://api.gep.com/" horizontal />

  <Card title="GEP SMART REST APIs index" icon="external-link" href="https://api.gep.com/gep-smart/gep-rest-apis" horizontal />

  <Card title="Order (PO) API" icon="external-link" href="https://api.gep.com/gep-smart/gep-rest-apis/transaction-data-apis/order" horizontal />

  <Card title="Invoice API" icon="external-link" href="https://api.gep.com/gep-smart/gep-rest-apis/transaction-data-apis/invoice" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                      |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | OAuth 2.0. Client credentials are provisioned by GEP: there is no public self-service signup. 401 on unauthorized.                          |
| 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)                                            |
| Webhooks       | None documented. Request/response REST + Bulk + file exchange; status-update endpoints (OrderStatus, InvoiceStatus) for poll / push-status. |
| Events posture | Polling                                                                                                                                     |
| Rate limits    | None published; defined per integration agreement. Bulk APIs handle high volume.                                                            |
| Objects        | Requisition, RFX (sourcing), Contract, Order (PO), Invoice, Catalog; master data Suppliers / Category / Users                               |

## 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" icon="arrow-right-left" description="Create the demand">
    | Mapping                  | Detail                                              |
    | ------------------------ | --------------------------------------------------- |
    | Canonical to destination | role\_title, service\_category, cost\_center, dates |
    | Target                   | POST api/Requisition/...                            |
    | Requirement              | Required                                            |
    | Notes                    | Convention: POST …Details / GET …All / PUT …Status  |
  </Accordion>

  <Accordion title="Sourcing event (RFX)" icon="arrow-right-left" description="Competitive services">
    | Mapping                  | Detail                                        |
    | ------------------------ | --------------------------------------------- |
    | Canonical to destination | service\_category, sow\.summary, suppliers\[] |
    | Target                   | RFX API                                       |
    | Requirement              | Tenant required                               |
    | Notes                    | For competitively sourced services            |
  </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                   | Custom attribute / external reference on the document              |
    | Requirement              | Required                                                           |
    | Notes                    | Provisioned with GEP at onboarding: no self-service field creation |
  </Accordion>

  <Accordion title="Order (PO)" icon="arrow-right-left" description="Transact + back-sync">
    | Mapping                  | Detail                                                       |
    | ------------------------ | ------------------------------------------------------------ |
    | Canonical to destination | po\_lines, supplier, amount                                  |
    | Target                   | POST api/Order/OrderDetails; GET api/Order/GetPurchaseOrders |
    | Requirement              | Required                                                     |
    | Notes                    | PUT api/Order/OrderStatus for back-sync                      |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</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>