Skip to main content
The pages in this section document the Workspace API operations that scripts and integrations call. Each page shows the operation’s parameters, its request and response shapes, a code sample for each SDK, the kind of token that can call it, the permissions that allow it, and its known errors.

Basics

These operations need no token and no X-Tenant. They read the global Provider catalog:
  • GET /api/vendors/parable-vendors
  • GET /api/vendors/parable-vendors/{slug}
  • GET /api/vendors/parable-vendor-groupings/{vendorSlug}
  • GET /api/vendors/parable-vendor-groupings/{vendorSlug}/{groupingPath}
  • GET /api/vendors/provider-directory
  • GET /api/vendors/product-logos
GET /api/security/encryption-key also needs no token, but it needs X-Tenant. See Encrypted request bodies.

Errors

Error responses use the Problem Details format (RFC 9457), with the content type application/problem+json. The body has type, title, status, and detail. It often has a code, such as WA-VL-001, and a requestId. A validation error also has an errors member that lists each field that failed and why. Some refusals have a details member. See Errors for an example. Each operation page lists the statuses that the operation can answer. Two answers have a plain-text body, not a Problem Details body:
  • 429 from an operation that limits the requests from one address.
  • 504 from an operation that has a time limit.
Every response has an X-Request-ID header. Include its value when you contact support.

Operation groups