---
title: "Get a setup intent"
method: GET
path: "/setup_intents/{id}"
tags: ["Setup intents"]
---

# Get a setup intent

`GET /setup_intents/{id}`

Retrieves the setup intent with the given `id`. The setup intent must belong to your organization and match the `live` or `test` mode of the API key used.

## Path parameters

- `id` string, required

## Response `200`

The setup intent with the given `id`.

- SetupIntent
  - `id` string, required — Unique identifier of the setup intent.
  - `object` 'setup_intent', required — Type of the object. Always `setup_intent`.
  - `error_reason` 'null' | 'login_invalid_credentials' | 'login_credentials_locked' | 'authorization_timeout' | 'mfa_authorization_timeout' | 'mfa_unavailable' | 'bank_connection_error' | 'bank_not_available' | 'password_change_required' | 'request_timeout' | 'subscription_intent_expired' | 'account_type_not_permitted' | 'internal_error' | 'user_left' | 'card_declined' | 'invalid_card_credentials' | 'invalid_card' | 'authentication_failed' | 'insufficient_funds', nullable, required — Error code describing why the latest setup attempt failed. `null` until an attempt fails and when the setup succeeds.
  - `status` 'created' | 'started' | 'waiting_for_retry' | 'succeeded' | 'failed', required — Lifecycle status of the setup intent. One of `created`, `started`, `waiting_for_retry`, `succeeded`, or `failed`.

## Other responses

- `404` — The setup intent does not exist, belongs to another organization, or does not match the mode of the API key used.

---

[API](https://skmtc.net/fintoc/apis/fintoc-api.md) · [All operations](https://skmtc.net/fintoc/apis/fintoc-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fintoc/fintoc-api/revisions/9dafa63688a3/schema)