Get Positions
Company positions from 3GPP contributions, each with a verbatim quote, and side-by-side comparison.
One company (org): its validated positions, optionally on a topic (matched by meaning), meeting, group, agenda item, or stance. Several companies (orgs=lekha-wireless,mavenir&topic=NTN timing advance): compare mode. groups puts each company's positions about the same technical object side by side (target_key), each group lists related meeting decisions, and organizations gives each company's coverage: an empty positions list with coverage means that company made no in-scope contribution on the topic.
Each position has stance (proposes, supports, opposes, prefers_alternative, raises_concern, requests_clarification, observes), claim, quote (exact text from the contribution), unit_label, page, target, and its TDoc (ID, title, doc_kind, status, meeting, agenda item, official_url). Only submitters and co-submitters hold positions; summary editors never do.
How to answer a comparison: compare within each group, quote both sides, cite the decisions, and state each company's coverage. A position is a proposal, not an agreement.
Errors: 400 invalid_parameter, 409 organization_ambiguous (candidates returned), 503 catalog_timeout.
Request
- Base URL: https://api.3gppscout.com (the document declares no server; this is the origin it was published from)
- URL: https://api.3gppscout.com/positions
- Auth: none declared
Query parameters
One company: name, alias, or org_id, e.g. 'Lekha Wireless'.
Several companies to compare, comma-separated, e.g. 'lekha-wireless,mavenir'.
Free-text topic matched by meaning, e.g. 'NTN timing advance'.
Comma-separated meeting IDs, e.g. R1-126.
Comma-separated working groups, e.g. R1,R2.
Agenda item, e.g. 10.7.1 (use with meeting).
Comma-separated stances: proposes, supports, opposes, prefers_alternative, raises_concern, requests_clarification, observes.
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.