---
title: "3DS execution enrollment status"
method: GET
path: "/merchants/:id/3ds-execution/{requestId}/status"
tags: ["Merchants"]
---

# 3DS execution enrollment status

`GET /merchants/:id/3ds-execution/{requestId}/status`

Check the status of a previous request to enroll a merchant in Forter's 3DS execution services.

## Path parameters

- `requestId` string, required

## Headers

- `api-version` string, required
- `x-forter-siteid` string, required
- `Authorization` string, required

## Response `200`

Example threeDsExecutionOnboardingStatusResponse

- ThreeDsExecutionOnboardingStatusResponse — Response structure for merchant onboarding requests
  - `status` string, required — Status of the onboarding request - IN_PROGRESS (request is pending processing) / COMPLETE (request completed) / REJECTED (invalid request is rejected) / FAILED (request is valid but failed for some reason)

## Other responses

- `400` — Bad Request (Often missing a required parameter)
- `401` — Unauthorized (No valid API key provided)
- `404` — Not Found (The requested item doesn't exist)
- `429` — Too Many Requests (The client exceeded a rate limit). Honor Retry-After before retrying.
- `500` — Server Error (Something went wrong on Forter's end)
- `default` — Typed error envelope for any undeclared 4xx / 5xx status.

---

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