# Wonolo

> Wonolo is an on-demand staffing marketplace (founded 2013, San Francisco) that connects
> businesses needing flexible frontline labor with a pool of vetted independent workers
> ("Wonoloers") across warehousing, manufacturing, food production, retail, hospitality and
> general labor. Wonolo operates a REST integration API (V2) at api.wonolo.com for creating and
> managing job requests, jobs, workers and users, plus webhook callbacks for resource state
> changes.

This file was generated by API Evangelist from the public Wonolo surface on 2026-08-05.
Wonolo does not publish its own /llms.txt (https://www.wonolo.com/llms.txt returned 404).

## Read this first

- Wonolo publishes **no OpenAPI, AsyncAPI, GraphQL SDL or JSON Schema** at any probed location.
- Wonolo's public API documentation is **retired**: https://wonolo.readme.io/ returns HTTP 404,
  and https://developer.wonolo.com/ is a dangling Netlify custom domain (TLS SAN mismatch, 404).
- The API is **live but credentialed**: api_key and secret_key are issued by Wonolo to customers.
  There is no public self-service signup for API access.

## APIs

- [Wonolo API V2](https://www.wonolo.com/businesses): RESTful, JSON-only. Base URL
  `https://api.wonolo.com/api_v2/`. Resources: Users (Workers/Wonoloers and Employers/
  Requesters), Job Requests, Jobs. Webhook callbacks for resource state changes.
- [GET /api_v2/info](https://api.wonolo.com/api_v2/info): the one anonymous endpoint —
  returns environment and server time.
- Authentication: POST an issued `api_key` + `secret_key` to `/api_v2/authenticate` for a token.
  Keys carry either Public Pool or Private Pool access; writes are restricted at Public Pool.

## Machine-readable artifacts published by Wonolo

- [OAuth authorization server metadata](https://api.wonolo.com/.well-known/oauth-authorization-server):
  RFC 8414, served by the Pomerium identity-aware proxy in front of api.wonolo.com.
- [OAuth protected resource metadata](https://api.wonolo.com/.well-known/oauth-protected-resource):
  RFC 9728.
- [robots.txt](https://www.wonolo.com/robots.txt) and [sitemap.xml](https://www.wonolo.com/sitemap.xml).

## API Evangelist artifacts in this repo

- well-known/wonolo-well-known.yml — every /.well-known/ path probed, with status.
- authentication/wonolo-authentication.yml — auth profile, verified vs unverified claims split.
- conformance/wonolo-conformance.yml — standards asserted, each with fetched evidence.
- lifecycle/wonolo-lifecycle.yml — versioning, and the retired-documentation record.
- security/wonolo-domain-security.yml — TLS, HSTS, DNSSEC, CAA, SPF, DMARC probe.

## Company

- [Wonolo](https://www.wonolo.com/)
- [For businesses](https://www.wonolo.com/businesses)
- [About](https://www.wonolo.com/company/about)
- [Blog](https://www.wonolo.com/blog)
- [Engineering blog](https://engineeringblog.wonolo.com/)
- [GitHub](https://github.com/Wonolo)
- [Business support](https://support-business.wonolo.com/)
- [Worker support](https://support-worker.wonolo.com/)
- [Terms of service](https://info.wonolo.com/terms/)
- [Privacy policy](https://info.wonolo.com/privacy/)
- [Requester sign in](https://api.wonolo.com/users/sign_in)

## Not published

No status page (status.wonolo.com does not resolve), no changelog, no deprecation or sunset
policy, no SLA, no security.txt, no first-party SDK on npm/PyPI/RubyGems/Packagist, no CLI,
no MCP server (tools/list returned 404 on every probed path), no A2A agent card, no Postman
workspace published by Wonolo.