atlas-status-req

Query Atlas account request status via GET with a JWT Bearer.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tombelial666/test --skill atlas-status-req
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atlas-status-req
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/atlas-status-req
Command: npx skills add https://github.com/tombelial666/test --skill atlas-status-req

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check Atlas account requests status (NEW, BACK_OFFICE, etc) directly via API, independent from Atlas UI, to confirm the true state of a submitted request.

Core Features & Use Cases

  • GET endpoint to retrieve the status of an Atlas account request using externalRequestId.
  • Manual substitution of externalRequestId in the path; uses a valid JWT at Authorization to access the API.
  • Useful for reconciling Atlas state with UI or debugging ProcessingByClearing vs Atlas state.

Quick Start

Substitute your externalRequestId in the endpoint path and perform a GET request with your JWT header.

Frequently Asked Questions about atlas-status-req

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Atlas account request status directly via the API?▼

You can check Atlas account request status by performing a GET request on the account_requests v2 endpoint, substituting your externalRequestId in the path and providing a valid JWT as a Bearer token in the Authorization header.

Why does my Atlas account request status differ between the UI and the API?▼

Atlas account request status discrepancies between the UI and the API occur due to processing states like ProcessingByClearing. Querying the account_requests v2 endpoint directly reveals the true state, such as NEW or BACK_OFFICE, independent from the Atlas UI.

Do I need a JWT to query the Atlas account_requests endpoint?▼

Yes, you need a valid JWT to query the Atlas account_requests endpoint. You must include this raw JWT in the Authorization header as a Bearer token to authenticate your GET request against the local Atlas endpoint base URL.

What is the process for debugging Atlas request states using externalRequestId?▼

Debugging Atlas request states involves executing a GET request on the account_requests v2 endpoint. You manually substitute the externalRequestId into the request path and authenticate with a valid JWT to retrieve the true status.

Can I retrieve Atlas account request status without using the Atlas UI?▼

Yes, you can retrieve Atlas account request status without the UI by calling the local Atlas account_requests v2 endpoint directly. This requires substituting your externalRequestId in the path and passing a valid JWT as a Bearer token in the Authorization header.