Patternode API
Patternode keeps none of your series: no copies, no checkpoints, no results. A forming
series' state travels with you as a sealed edge; files are read from and written to
your own storage. Only account, usage and audit metadata are kept.
One API for every Patternode product, and one functional contract for every plan: a plan changes capacity, service levels and transports, never routes, fields or semantics. The service levels are the developer site's Service contract section.
Resources are product-neutral; the tag on each operation names the product it belongs to. Delve (formerly Mosaic) is the first.
Every operation carries x-status:
available: supported; changes follow the versioning policy.preview: works, may change with 30 days' notice; not for production alarms.planned: specified so you can design against it; returns 404 today.
Conventions that apply to every route are in the Concepts pages of the developer site: authentication, the body hash on writes, idempotency, errors, rate-limit headers and versioning.
Authentication
- HTTP: Bearer Auth
- API Key: apiKey
Authorization: Bearer pnk_live_..., one space after Bearer.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
The same key in x-api-key, for clients that cannot set Authorization.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | x-api-key |
Contact Patternode partner support: partners@patternode.com
License Apache 2.0