Skip to content

UX: raw 403 on tier-restricted endpoints reads as auth failure; document full typeId catalog #8

Description

@arcaputo3

Problem

Two paper cuts that cost agents repeated discovery time:

1. Tier-restricted endpoints surface as raw 403s. reports summary, events summary, and audio list all return bare 403 Forbidden on our tier (confirmed 2026-07-22 and again 2026-07-25). A raw 403 reads as "auth broken," so consumers waste cycles re-checking API keys before concluding it's an entitlement issue. Note reports download works fine on the same tier — so it really does look like a credentials bug the first time you hit it.

2. Document typeIds are partially undocumented. The document-types list omits at least typeId 25 = CEO shareholder letter (discovered by inspection on a PLTR pull, 2026-07-12). The IDs agents actually use constantly: 11=10-K, 7=10-Q, 10=8-K/earnings release, 5=slides, 46=DEFM14A, 26–29=earnings-call event types.

Proposed fixes

  1. When a summary/audio endpoint returns 403, print a distinct message: endpoint not available on this API tier (HTTP 403) — distinguishable from a 401 auth failure.
  2. Ship a quartr types (or extend the existing document-types listing) that includes the full known typeId catalog, and/or document the common IDs in the README.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions