Skip to main content

Atlas Company Service - Overview

Introduction​

The Atlas Company Service manages corporate identity, secure credential exchange, session token issuance, and sub-account governance across the Atlas banking infrastructure.

Platform operators and business clients utilize this service to:

  1. Authenticate master developer credentials (clientId and apiKey) to obtain scoped JWT access tokens.
  2. Delegate session access into managed downstream sub-accounts via Sub-Account Login.
  3. Trigger automated Terms & Conditions acceptance emails to controlling officers and directors of partner-referred sub-accounts during KYB onboarding.

Key Capabilities​

  • Primary Authentication: Exchange permanent developer credentials for a 60-minute scoped JWT Bearer token.
  • Sub-Account Context Switching: Platform partners can switch context into specific downstream sub-companies (subCompanyId) to perform actions on their behalf without requiring individual sub-account API keys.
  • Automated T&C Acceptance Dispatch: Trigger compliant electronic consent invitations to UBO-verified directors as the final milestone in the Atlas for Platform KYB onboarding workflow.
  • Strict Multi-Tenant Isolation: Enforces fine-grained permission configs (Client:Sub-Accounts:write, Admin:Onboarding:read) and prevents access to archived or compliance-rejected accounts.

Base URLs​

Production: https://api.ahrvo.network
Staging:    https://gateway.ahrvo.network

Available Endpoints​

MethodEndpointDescription
POST/users/loginExchange clientId and apiKey for a primary 60-minute JWT Bearer access token
POST/sub-accounts/{subCompanyId}/loginIssue a scoped Bearer token for a specific managed sub-account
POST/sub-accounts/{subCompanyId}/tnc/send-emailDispatch a Terms & Conditions acceptance email to a sub-account controlling director

Architecture & Sub-Account Lifecycle​

sequenceDiagram
    autonumber
    actor Partner as Platform Partner
    participant Atlas as Atlas Company API
    participant Onboarding as Onboarding / KYB Service
    actor Director as Sub-Account Director

    Partner->>Atlas: POST /users/login (clientId, apiKey)
    Atlas-->>Partner: 200 OK (Partner JWT Token)

    rect rgb(240, 248, 255)
    Note over Partner,Director: Partner-Referred Sub-Account Onboarding
    Partner->>Atlas: POST /sub-accounts/{subCompanyId}/tnc/send-email (email, shareholderId)
    Atlas->>Director: Delivers secure Terms & Conditions acceptance email
    Director-->>Onboarding: Reviews & accepts legal terms online
    end

    rect rgb(245, 255, 245)
    Note over Partner,Atlas: Sub-Account Operational Access
    Partner->>Atlas: POST /sub-accounts/{subCompanyId}/login (Authorization: Bearer <Partner JWT>)
    Atlas-->>Partner: 200 OK (Scoped Sub-Account JWT)
    end

Next Steps​