GET /partner/v1/applications/{id}

2 min read

GETHTTP method

OAuthAuth

partnerRing

Endpoint

Method	`GET`
Path	`/partner/v1/applications/{id}`
Ring	partner (OAuth)
Auth	OAuth

Request

Path parameter id — the application ID returned when you created it. Requires applications:read.

Response

A JSON application object: its id, status, the submitted details and a reference to the associated decision where one exists. Use it to reconcile state after a missed webhook or on a support lookup.

Errors & notes

A 404 if the ID is unknown or not owned by your project. A 403 without applications:read. Reads are cheap but still count against your bucket.

When to use it

Reach for this read in three situations: to reconcile after a missed webhook, to power an on-demand support lookup, or to confirm the current state before taking an action that depends on it. It is not a substitute for webhooks in a real-time flow — polling it in a tight loop wastes your rate budget — but as a reconciliation and lookup tool it is exactly right. To walk the whole collection, use the list endpoint with cursor pagination.

Frequently asked questions

Can I list all my applications?

Yes — GET /partner/v1/applications returns a paginated list; this endpoint reads one by ID. See the pagination reference for cursoring through the collection.

Should I poll this for the decision?

Prefer a webhook for the decision event. Use this read to reconcile after a missed webhook or for an on-demand support lookup, not as a tight polling loop.

Is this read cached?

Application state changes over its lifecycle, so treat this as a live read rather than a long-lived cache. Cache briefly if you must, but rely on webhooks for the authoritative, timely state transitions.