Submiting an Application

The Applications endpoints power Credit Key’s underwriting and onboarding flow. An application represents a business attempting to qualify for Credit Key financing. The application contains business details, ownership information, identity verification steps, and the decisioning result (approved, declined, pending).

These endpoints allow you to:

• Create a new application
• Update business or owner details during the application process
• Retrieve application state
• Submit verification information
• Complete the final decisioning steps

All endpoints require authentication and are intended for backend use.

---

Create an Application

POST /application

Start a new Credit Key application.

Common uses:

• Beginning the underwriting process for a new buyer
• Pre-qualifying a customer before checkout
• Creating an application during an account setup flow

The request includes business information (name, type, revenue, industry), owner details, and other identity fields required for underwriting.

---

Retrieve an Application

GET /application/{id}

Fetch the full state of an existing application.

Common uses:

• Showing users their current application status
• Reviewing submitted business and owner information
• Determining whether the application is approved and ready for ordering

The response includes decision status, required next steps, and any missing fields.

---

Update an Application

PATCH /application/{id}

Update business or owner information for an in-progress application.

Common uses:

• Fixing typos or updating information after validation
• Collecting missing business fields required to complete underwriting
• Updating ownership information before decisioning

You generally use this in multi-step onboarding flows where additional details are submitted over time.

---

Submit Owner Information

POST /application/{id}/owner

Submit or update personal information for the applying business owner.

Common uses:

• Adding the primary beneficial owner
• Updating owner identity information prior to KYC checks
• Supporting multi-owner application flows

This endpoint is key for identity verification and soft credit-pull requirements.

---

Submit Two-Factor Verification

POST /application/{id}/verify-2fa

Confirm the application via two-factor authentication code (SMS or email).

Common uses:

• Verifying user identity before issuing approval
• Completing the final requirement in the underwriting flow

Most applications require 2FA before Credit Key will provide a final decision.

---

Complete the Application

POST /application/{id}/complete

Finalize the application and trigger the underwriting decision process.

Common uses:

• Ending a multi-step onboarding flow
• Triggering a fresh decision after all required info has been provided

The response typically includes an approved, declined, or additional info needed result.

---

Where Applications Fit in the Overall Model

• Applications → Collect business, owner, and identity details and perform underwriting
• Companies → Created after approval; represent the ongoing business account
• Orders → Can be created only after the application is approved and a company.id exists

Typical lifecycle:

1. Create an application
2. Gather missing business/owner info
3. Submit 2FA
4. Complete the application → receive final decision
5. On approval, transition the applicant into a Company and begin creating Orders