# valueverde Partner API

> Programmatic access to the valueverde platform for integration partners. Browse the published cooperative catalogue, provision the investors you act on behalf of, place share-purchase orders, and read the resulting portfolio. Authenticated via OAuth2 client_credentials; errors follow RFC 9457 Problem Details with stable `code` and `trace_id` fields.

Authentication is OAuth2 client_credentials; every error is an RFC 9457 problem detail with a stable `code` and a `trace_id`. Base URLs: `https://api.valueverde.de` (production) and `https://api.staging.valueverde.de` (staging — the same contract, no real money; build here first).

Each link below is the Markdown source of a page, not its rendered HTML.

## Start here

- [Introduction](https://docs.valueverde.de/docs/intro.md): What the valueverde Partner API does, how the pieces fit together, and where to start.
- [Quickstart](https://docs.valueverde.de/docs/quickstart.md): Credentials to a placed share-purchase order in eight calls, copy-pasteable end to end.
- [The investing flow](https://docs.valueverde.de/docs/investing-flow.md): The four phases of a partner integration, what each call requires, and every way an order can end.

## Concepts

- [Authentication](https://docs.valueverde.de/docs/authentication.md): OAuth2 client_credentials flow, scopes, token lifecycle, and JWT validation.
- [Webhooks](https://docs.valueverde.de/docs/webhooks.md): Signed outbound notifications for share-purchase transitions — event types, payload schemas, headers, signature verification and retry behaviour.
- [Pagination & sorting](https://docs.valueverde.de/docs/pagination-and-caching.md): One-based pagination, the page envelope, and how to sort the cooperative catalogue.
- [Security & data handling](https://docs.valueverde.de/docs/security.md): Transport, credential, and data-handling guarantees the Partner API operates under.
- [Versioning & deprecation](https://docs.valueverde.de/docs/versioning.md): What this contract promises, what counts as a breaking change, and how new versions are rolled out.
- [Rate limits](https://docs.valueverde.de/docs/rate-limits.md): What the limits are, the headers that tell you where you stand, and how to back off correctly.

## Reference

- [OpenAPI document](https://docs.valueverde.de/docs/openapi-spec.md): Download the machine-readable contract, generate a client from it, and pin the version you generated against.
- [Errors](https://docs.valueverde.de/docs/error-reference.md): RFC 9457 Problem Details envelope, every error code the Partner API returns, and when to retry.
- [Changelog](https://docs.valueverde.de/docs/changelog.md): Notable changes to the valueverde Partner API.

## Machine-readable contract

- [OpenAPI 1.6.0, YAML](https://docs.valueverde.de/spec/partner-api.yaml): the full contract — every path, schema, error body and webhook payload. Generate a client from this rather than from the prose.
- [OpenAPI 1.6.0, JSON](https://docs.valueverde.de/spec/partner-api.json): the same document.
- [Version manifest](https://docs.valueverde.de/spec/index.json): every published version and its permanent URL, newest first.
- [Postman collection](https://docs.valueverde.de/spec/valueverde-partner-api.postman_collection.json): generated from the spec; fetches and caches a token, then carries ids between requests.

## Optional

- [Everything above as one document](https://docs.valueverde.de/llms-full.txt): all guides concatenated, for a single fetch.