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

# Globality

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

This page records how composerID publishes into Globality: 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.

Globality is an AI-guided services-sourcing platform. Its public REST API exposes a fixed domain model (Project to Brief to Provider to Proposal to Award) that composerID reads to track services and SOW sourcing intent end to end.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                                                                                                |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0 client-credentials to a Bearer JWT via Auth0 (POST [https://globality-prod.auth0.com/oauth/token](https://globality-prod.auth0.com/oauth/token), audience per environment). |
| composerID publishes | Project (create): POST /v2/projects                                                                                                                                                   |
| Intent ID lands on   | `project` `external_reference`, held by composerID against the destination record                                                                                                     |
| Back-sync            | Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent's timeline.                                                                     |

## Vendor documentation

<Columns cols={2}>
  <Card title="Globality Developer API" icon="external-link" href="https://www.globality.com/developer-api" horizontal />

  <Card title="Integration overview" icon="external-link" href="https://www.globality.com/integration" horizontal />

  <Card title="OpenAPI spec (spec.json)" icon="external-link" href="https://www.globality.com/wp-content/uploads/2026/06/spec.json" horizontal />

  <Card title="Webhooks overview" icon="external-link" href="https://www.globality.com/product-innovation-journey/webhooks" horizontal />

  <Card title="Webhooks documentation (PDF, v5)" icon="external-link" href="https://www.globality.com/hubfs/Integration%20and%20API%20pages/Globality%20Webhooks%20Documentation%20v5.pdf" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | OAuth 2.0 client-credentials to a Bearer JWT via Auth0 (POST [https://globality-prod.auth0.com/oauth/token](https://globality-prod.auth0.com/oauth/token), audience per environment). Token TTL 24h. Scopes read:project / write:project.                                                                                                                                                                                                                |
| Style          | REST (JSON), versioned /v2, OpenAPI / Swagger                                                                                                                                                                                                                                                                                                                                                                                                            |
| Base URL       | US [https://apis.prod.globality.com](https://apis.prod.globality.com)  \|  EU [https://apis.eu.globality.com](https://apis.eu.globality.com)                                                                                                                                                                                                                                                                                                             |
| Webhooks       | Yes: push webhooks, registered in-app per event type. Documented events: Brief Completed, Brief Updated, Proposal Submitted, Proposal Approved, Award Completed (Globality adds event types over time; an earlier v8 of the PDF also listed Project Status Change). Thin payload (event, projectId, providerId where relevant, timestamp): call back to /v2 for detail. Retries at 1/3/6/12/24h, then the endpoint is auto-disabled and you are emailed. |
| Events posture | Webhooks                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| Rate limits    | Not publicly documented; confirm per tenant.                                                                                                                                                                                                                                                                                                                                                                                                             |
| Objects        | Project, Brief, Provider (supplier), Proposal, Award, Files                                                                                                                                                                                                                                                                                                                                                                                              |

## 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="Project (create)" icon="arrow-right-left" description="Container for sourcing intent">
    | Mapping                  | Detail                                         |
    | ------------------------ | ---------------------------------------------- |
    | Canonical to destination | service\_category, sow\.summary, budget, dates |
    | Target                   | POST /v2/projects                              |
    | Requirement              | Required                                       |
    | Notes                    | Project is the sourcing-intent container       |
  </Accordion>

  <Accordion title="Brief (read)" icon="arrow-right-left" description="Scoped requirement">
    | Mapping                  | Detail                                  |
    | ------------------------ | --------------------------------------- |
    | Canonical to destination | requirement, budget, timeline, services |
    | Target                   | GET /v2/projects/\{id}                  |
    | Requirement              | Read                                    |
    | Notes                    | Auto-created from the intake form       |
  </Accordion>

  <Accordion title="Award (read)" icon="arrow-right-left" description="Outcome / receipt">
    | Mapping                  | Detail                              |
    | ------------------------ | ----------------------------------- |
    | Canonical to destination | completion, dates, po\_ref          |
    | Target                   | webhook AwardCompleted then GET /v2 |
    | Requirement              | Read                                |
    | Notes                    | Feeds the publish receipt           |
  </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                   | Project external reference (link-only until write support confirmed)                  |
    | Requirement              | Required                                                                              |
    | Notes                    | Read-centric API: composerID records the intent\_id ↔ project linkage on its own side |
  </Accordion>
</AccordionGroup>

<Note>
  Public docs + OpenAPI, but credentials are customer-gated (an admin assigns the in-app Developer role). Region-specific base URLs and Auth0 audience per environment. The API is read-centric: Project create + status update only; there is no public endpoint to push your own supplier lists. Pre-built connectors exist for Ariba, Fieldglass and Coupa.
</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>