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

# Zip

> Zip (Procurement Orchestration): the API posture, publish target and field mapping composerID publishes a decision reference through.

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

Zip is an intake-to-procure orchestration platform: one front door for any purchase request that routes through the right approvals and into the ERP. Its REST API and low-code App Studio let partners read and write Zip's procurement objects, so composerID can hand canonical intent to Zip's intake and let the orchestrated flow carry it through to purchase order: Zip as a complementary orchestration partner, not a destination-of-record.

<Info>
  Category: Procurement Orchestration. Coverage status: Documented. Vendor documentation: gated (customer or SKU documentation).

  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       | Credential-based: unique keys issued per partner for separate sandbox and production environments. |
| composerID publishes | Intake request: Intake / Purchase Request (App Studio action)                                      |
| Back-sync            | Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.           |

## Vendor documentation

<Columns cols={2}>
  <Card title="Zip: Intake-to-Procure" icon="external-link" href="https://zip.com/products/intake-to-procure" horizontal />

  <Card title="Zip App Studio (low-code integrations)" icon="external-link" href="https://zip.com/products/app-studio" horizontal />

  <Card title="Zip integration ecosystem" icon="external-link" href="https://zip.com/capabilities/integrations" horizontal />

  <Card title="Zip for Procurement" icon="external-link" href="https://zip.com/solutions/procurement" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                          |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Credential-based: unique keys issued per partner for separate sandbox and production environments. Build and certify against sandbox, then enable in production. No public self-service signup. |
| Style          | REST (JSON request/response, standard HTTP status codes). App Studio adds low-code REST/SOAP endpoint actions, triggers and branching.                                                          |
| Base URL       | Provisioned per customer (sandbox + production). No single public base URL.                                                                                                                     |
| Webhooks       | Event-driven via App Studio triggers + bi-directional sync; integration status and activity logs. Push or poll depending on the configured action.                                              |
| Events posture | Webhooks and polling                                                                                                                                                                            |
| Rate limits    | Not publicly documented; defined per partner integration agreement.                                                                                                                             |
| Objects        | Intake / purchase request, Requisition, Vendor (supplier), Contract, Purchase Order, 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="Intake request" icon="arrow-right-left" description="The single front door">
    | Mapping                  | Detail                                                      |
    | ------------------------ | ----------------------------------------------------------- |
    | Canonical to destination | role\_title, service\_category, cost\_center, dates, amount |
    | Target                   | Intake / Purchase Request (App Studio action)               |
    | Requirement              | Required                                                    |
    | Notes                    | Zip routes it through the right approvals                   |
  </Accordion>

  <Accordion title="Vendor" icon="arrow-right-left" description="Resolve / onboard supplier">
    | Mapping                  | Detail                           |
    | ------------------------ | -------------------------------- |
    | Canonical to destination | supplier\_name, tax\_id, contact |
    | Target                   | Vendor object                    |
    | Requirement              | Tenant required                  |
    | Notes                    | Vendor onboarding gates the PO   |
  </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                    | Zip's developer hub requires a login; public pages describe the API only in general terms. The carrier is identified with the vendor or the joint customer before any claim is made |
  </Accordion>

  <Accordion title="Purchase Order" icon="arrow-right-left" description="Transact + back-sync">
    | Mapping                  | Detail                              |
    | ------------------------ | ----------------------------------- |
    | Canonical to destination | po\_lines, supplier, amount, status |
    | Target                   | Purchase Order object               |
    | Requirement              | Read                                |
    | Notes                    | Read for reconciliation / liveness  |
  </Accordion>
</AccordionGroup>

<Note>
  Zip is configuration-heavy: intake forms, approval chains, custom fields and routing logic are tenant-defined in the workflow builder, and App Studio is the supported low-code path for custom triggers and actions. The API surface is partner-gated: endpoints, credentials and base URLs are provisioned by Zip during onboarding. Note: ziphq.com (now zip.com) is the procurement platform, which is unrelated to the Zip Co buy-now-pay-later product at zip.co.
</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>