Pagination, filtering, and caching

How public endpoints handle lists.

SectionAPI reference

AudienceDevelopers

Public safeNo private credentials

Purpose

How public endpoints handle lists.

Public and auth behavior

Foundry discovery endpoints are public and return cached public-safe payloads. Marketplace product APIs may require a configured marketplace access path such as bearer token, RapidAPI proxy secret, GitHub entitlement, or Zapier automation key.

Caching and freshness

Responses are backed by generated or cached artifacts. They are meant for stable public discovery and integration, not direct access to internal systems or live provider dashboards.

Errors

Expect standard JSON error responses for missing products, invalid input, rejected access, or throttled requests. Public Foundry API traffic is rate limited to the configured public limiter.

Security notes

Examples use sanitized slugs and do not expose internal database IDs, private run IDs, owner-only endpoints, provider credentials, or bucket names.