# JENNi Partner API

The JENNi Partner API is one HTTP API, read by four kinds of partner, for registering stores, pushing catalog and live stock into JENNi in runs, and reading back what landed. This portal (developer.jennipro.com) is a single page that routes by URL fragment, so read the raw sources linked below rather than the rendered page: the OpenAPI document is the contract, and the Markdown files are the prose the build folds into it. Every request needs a partner key issued through the portal; when a call fails, quote the `x-jenni-request-id` response header, which equals the `request_id` in the problem body.

## Specification

- [OpenAPI 3 document, provider-v1](/specs/provider-v1.json): every operation, schema, scope and RFC 7807 problem type, generated by the service that serves it.
- [OpenAPI 3 document, provider-v1, raw](/specs/provider-v1.source.json): the same document exactly as the service generated it, without the portal's landing page and guide tags. Generate clients from this one, and compare digests against it.

## Docs

- [Quickstart](/content/quickstart.md): get a credential, find the base URL, register a store, open a run, push inventory levels, close the run, read it back; dry-run before committing anything.
- [Errors](/content/errors.md): the problem+json envelope, the full catalogue of problem types, per-item errors versus HTTP errors, and the whole error contract as client logic.
- [Rate limits](/content/rate-limits.md): what is enforced today and what is not, the response headers to read, and how to handle a 429.
- [Webhooks](/content/webhooks.md): the event catalogue, delivery format, signature verification, retry policy, URL rules and endpoint management.