# Noosh

> Noosh is marketing execution and print/procurement management software for enterprise marketing teams
> running campaigns across direct mail, print and point-of-sale materials. It coordinates collaborative
> marketing workflows, agency and supplier performance, vendor diversity, and cost/quality/time/
> sustainability data, and integrates with procurement and other enterprise systems.

Generated by API Evangelist on 2026-08-13 from the Noosh apis.yml and the artifacts in this repository.
Noosh does not publish its own llms.txt — https://support.noosh.com/llms.txt returns 404.

## What Noosh publishes

Noosh ships a real, public, machine-readable API contract: a Swagger 2.0 document with 86 paths,
107 operations and 214 schema definitions, served at https://api.noosh.com/api/swagger.json with a
Swagger UI at https://api.noosh.com/api/developer/index.html. Noosh's own site describes it as "the
industry-leading Noosh API" behind "over 60 integrations to enterprise software systems", but publishes
no developer portal, no getting-started guide, no SDK, no changelog for the API, no pricing and no
rate limits. The Swagger document is the entire developer surface.

## API

- [Noosh API (Swagger 2.0)](https://api.noosh.com/api/swagger.json): The complete published contract. 107 operations across Project, Spec, Estimate, RFE, RFQ, Quote, Order, Shipment, Invoice, File, Task, Time Card, Team Member, Contact and Workgroup.
- [Swagger UI](https://api.noosh.com/api/developer/index.html): The only interactive documentation Noosh publishes.

## Shape of the API

- Base host: `https://api.noosh.com`. The published document declares the build-time placeholder host `example.com:80`; the real host is the one serving the document.
- Auth: HTTP Basic, one scheme (`HTTP_BASIC`). No OAuth, no API keys, no scopes.
- Addressing: hierarchical and workgroup-scoped — `/{version}/workgroups/{workgroup_id}/projects/{project_id}/{resource}`. `workgroup_id` is a path parameter on 105 of 107 operations.
- Versioning: four generations served at once in the URI path — `/v1`, `/1.1`, `/1.2`, `/3` — with no operation marked deprecated and no policy published.
- Errors: vendor envelope `HTTPStatusVO` (`status_code`, `status_reason`) on 404/422/500. Not RFC 9457. The same field pair also appears on 200 responses.
- No pagination, no idempotency key, no request-id header, no webhooks, no events, no 429 and no rate-limit headers.
- Unauthenticated calls return `403 {"message":"Forbidden"}` from AWS API Gateway.

## Specs

- [openapi/noosh-openapi.yml](openapi/noosh-openapi.yml): The harvested contract with the placeholder host repaired to api.noosh.com.
- [openapi/_original/noosh-openapi.json](openapi/_original/noosh-openapi.json): The unmodified document as Noosh publishes it.
- [overlays/noosh-openapi-overlay.yaml](overlays/noosh-openapi-overlay.yaml): Every change API Evangelist applied, as an OpenAPI Overlay.

## Artifacts

- [authentication/noosh-authentication.yml](authentication/noosh-authentication.yml): HTTP Basic profile.
- [conventions/noosh-conventions.yml](conventions/noosh-conventions.yml): Cross-cutting semantics, including the absences.
- [errors/noosh-problem-types.yml](errors/noosh-problem-types.yml): The HTTPStatusVO error envelope and the three documented statuses.
- [data-model/noosh-data-model.yml](data-model/noosh-data-model.yml): Entity graph derived from the 214 definitions.
- [lifecycle/noosh-lifecycle.yml](lifecycle/noosh-lifecycle.yml): Versioning, the missing deprecation policy, and the Pingdom status page.
- [changelog/noosh-changelog.yml](changelog/noosh-changelog.yml): The customer help-centre release notes — Noosh has no API changelog.
- [conformance/noosh-conformance.yml](conformance/noosh-conformance.yml): Standards conformance, mostly negative.
- [packages/noosh-packages.yml](packages/noosh-packages.yml): No first-party SDK exists in any registry.
- [mcp/noosh-mcp.yml](mcp/noosh-mcp.yml): No MCP server exists; a candidate tool surface derived from the operations.
- [plans/noosh-plans-pricing.yml](plans/noosh-plans-pricing.yml): No published pricing.
- [rate-limits/noosh-rate-limits.yml](rate-limits/noosh-rate-limits.yml): No published limits.
- [security/noosh-domain-security.yml](security/noosh-domain-security.yml): TLS/HSTS/SPF/DMARC probe.
- [well-known/noosh-well-known.yml](well-known/noosh-well-known.yml): Nothing served at any /.well-known/ path.

## Agent skills

- [skills/noosh-source-a-print-job.md](skills/noosh-source-a-print-job.md): Project → spec → RFQ → quote → buy order.
- [skills/noosh-manage-project-files.md](skills/noosh-manage-project-files.md): Files and folders, and which of the four upload routes to use.
- [skills/noosh-track-order-fulfillment.md](skills/noosh-track-order-fulfillment.md): Order → shipment → locations → invoice.

## Company

- [Noosh](https://www.noosh.com/): Marketing execution software.
- [Product](https://www.noosh.com/our-product/)
- [Partners and integrations](https://www.noosh.com/partners/)
- [Support](https://www.noosh.com/support/) and [help centre](https://support.noosh.com/hc/en-us)
- [Resources / blog](https://www.noosh.com/resources/)
- [Status](https://stats.pingdom.com/qcecd0tzzhpr/667653)
- [Login](https://nooshauth.noosh.com/login)
- [Terms of Service](https://www.noosh.com/terms-of-service/) · [Privacy Policy](https://www.noosh.com/privacy-policy/)