CarSoft API · 1.0.0
API version 1.0.0. Explore 46 endpoints, authentication, app permissions and integration guidance. Apply for partner approval, then activate your developer account.

Developer guidance for CarSoft’s marketplace and partner platform.
API version 1.0.0. Explore 46 endpoints, authentication, app permissions and integration guidance. Apply for partner approval, then activate your developer account.
The consolidated local contract follows the approved simplified marketplace scope: existing Stripe payment integration, required partner administration and billing, manual overdue decisions and bounded jobs.
Ordinary external software partners remain in scope; arbitrary payment-provider onboarding is excluded. This draft does not establish production availability. Website provider-hostname and environment acceptance remain pending.
Local embedding documentation covers five placements, a server-revalidated minimal context bridge, current resource/native permissions, keyboard controls and removal when access changes.
The fee invoice provider contract separates optional preCreditMinor, postCreditMinor and appliedBalanceMinor fields from cash and excludes private financial receipts. No new partner billing adjustment API is advertised. The full goal remains unfinished; public application intake stays disconnected and disabled.
Customer setup documentation now reflects locally accepted native root method and version controls, immutable processor configuration receipts and private paginated history.
Hosted bank acceptance remains pending. Local verification does not establish full launch readiness; the complete Software goal remains unfinished and public application intake stays disconnected and disabled.
Local immutable processor configuration receipts, versioned native root method review and private paginated history constrain processor changes.
Software reports owned SQL/browser checks and isolated local Supabase Auth, Storage, PostgREST and CarSoft API acceptance with temporary resources removed. This is not hosted or real bank acceptance. Software remains local and unreleased, the complete goal remains unfinished, and public application intake stays disconnected and disabled.
Local material-revision and invitation receipts bind the exact action.
Native sign-out exposes failure and retry states. Software reports owned admin/security fixtures, logout races and six fresh real sandbox merchant SDK checks. These checks do not establish hosted customer or bank acceptance, physically isolated sandbox acceptance or full launch readiness; those remain unfinished. Public application intake stays disconnected and disabled.
Local native root billing, recovery, domain and invitation actions require transaction admission, with bounded local acceptance checks.
These contracts do not establish production availability or full launch readiness. The overall Software goal remains unfinished; public application intake stays disconnected and disabled.
Local native root records provide full paginated applications, apps, teams, invitations, domains, submissions, revisions, journals, audits, deletion and governance inventories beyond dashboard previews.
Software reports owned pagination, private authorization, screening refresh and responsive fixture checks. Broader legacy root billing and recovery mutations, hosted provider acceptance and physically isolated sandbox acceptance remain pending. The overall goal is unfinished; public application intake stays disconnected and disabled.
Local native root credential creation requires admitted proof and issues credentials once.
Rotation and revocation bind the expected version; deletion attestation is evidenced and versioned. Software reports owned native browser/customer/tracking checks and a rotation/logout race check. These results do not establish full launch readiness. The overall Software goal remains unfinished; public application intake stays disconnected and disabled.
Local versioned native screening and private review journals require transaction-current root proof for revision, submission, ownership and credential-sharing reviews.
Software reports owned fixture and logout-race verification, including denial of later replay. These checks do not establish full production readiness. Broader legacy root mutations and full launch remain unfinished; Software and public application intake stay gated and unreleased.
Local native cookie logout retires exact hashed sessions and prevents replay.
Approved registry method selection, exact charge customer/method/type binding and requested provider receipt IDs constrain payment readback. Reported SQL, unit and owned HTTP fixture checks do not establish updated real hosted Stripe or bank acceptance. Root configuration method controls, physically isolated sandbox acceptance and broader launch work remain pending. Software and public application intake remain gated and unreleased.
Local customer receipt recovery requires current root review, original merchant identity and current source checks.
Bounded automatic provider readback, exact signed setup callbacks and expiry preserve the original setup evidence. These local contracts do not establish real hosted Stripe or bank acceptance, physically isolated sandbox acceptance or full launch readiness; those remain pending. Software and public application intake remain gated and unreleased.
Local payment authorization listing exposes only opaque CarSoft references filtered to the exact installation and consent version.
Native owner password/MFA invitations freeze the customer, app, limit and expiration. Browser fragment capability, explicit terms acceptance, one-use provider setup, exact readback and encrypted app-bound methods support local setup and revocation; setup does not charge. Owned protocol fixtures do not prove real hosted card/bank acceptance, approved bank selection, automatic pending verification or reviewed uncertain-setup recovery. These remain unfinished. Software and public intake remain gated and unreleased.
Explicitly activated submitted financial tracking can privately read confirmed provider state during public shutdown, processor suspension or merchant revocation.
It cannot mutate providers or reopen APIs. Native root receipt review binds password/session MFA, intent version and exact original merchant/customer/amount/invoice evidence before recording the native ledger once. Unresolved effects are investigated, never replaced. Charge/refund readback retains original customer/method binding. Pending setup expiry holds uncertain effects for review and does not expire active connections. Owned fixtures do not prove hosted Stripe or physically isolated sandbox delivery; hosted customer setup, external processors and full financial acceptance remain unfinished. Software and intake stay gated and unreleased.
Local native merchant verification uses single-use separate webhook registration and a private uncharged delivery probe.
Signed callbacks plus exact provider readback do not activate access; fresh dealership admin/password/MFA approval is required. Lost registration/probe responses require review, never blind recreation. SDK transport permits one HTTP attempt, including closed connections. Owned protocol fixtures are not real hosted Stripe delivery acceptance. Physically isolated HTTPS sandbox delivery, hosted customer setup, external processors and full financial acceptance remain pending; Software and intake remain gated and unreleased.
Local versioned platform processor review preserves immutable historical configurations and binds the action to the current root session and MFA transaction.
Native factor/proof writers coordinate with review. Review alone grants no merchant access; endpoint registration, delivery, activation and external merchant/customer acceptance remain unfinished. Public intake stays disabled and Software remains unreleased.
Local native payment controls include connection/method inventory and revocation, immutable expiring customer authorization and bounded processor callbacks.
Staged read-only Stripe merchant verification is visible for platform review. Pending setup grants no payment access. Separate endpoint registration/delivery, activation, hosted customer setup and full launch remain unfinished; public intake stays disabled.
Payment environment and merchant identity binding and exact-session native marketplace MFA sign-out are locally documented.
These controls do not provision an isolated sandbox or complete merchant onboarding. Full launch and production activation remain unfinished; public Website intake stays disabled.
Local native dealership-admin session-bound MFA now protects payment-scope consent and refund approval.
Disconnect and refund rejection retain password-only protection. This scoped local verification does not complete merchant/customer onboarding or the full Software launch. Partner access and Website intake remain gated and unreleased.
Reviewed lost-authenticator recovery has scoped local acceptance with real disposable Auth and the portal browser.
Native-admin forms and owned provider protocol fixtures have separate local verification. Hosted Auth configuration, email/CAPTCHA and complete marketplace launch remain pending; portal and public intake remain gated and unreleased.
Local organization domain controls offer exact-host one-hour TXT challenges, versioned verification/revocation and 30-day proofs under current owner/admin recent TOTP authority.
Domain proof approves no app or dealership access. The gated local portal now includes team invitation, ownership and credential-sharing controls; incoming acceptance still requires separate platform review. Hosted email/CAPTCHA, reviewed lost-factor recovery, merchant onboarding/full API-to-ledger, finance adjustments/contact replacement, usable isolated sandbox and full launch remain unfinished. Authenticator replacement is still under implementation and has no accepted-readiness claim.
Voluntary cancellation requires the current organization owner, exact agreement fingerprint and recent TOTP MFA.
Agreed period-end or immediate-prorated cutoff governs access and final fees; existing payments reconcile and owed invoices remain payable. Active owner/admin/billing members retain billing history access. Cleanup preserves the original cutoff plus 30-day deletion deadline. Four actual Stripe sandbox partner-fee scenarios passed with synthetic customers; email delivery and production activation remain separate unfinished acceptance requirements. Installed merchant-adapter SDK tests also passed wrong-account/mode/customer refusal, a saved-method charge fully refunded with a bound refund, and a stable hosted link subsequently expired. Full hosted merchant/customer onboarding, API-to-native-ledger acceptance, completed hosted checkout, external processors and production acceptance remain unfinished. Overdue billing never automatically suspends or cancels a partner. Local platform-admin sensitive reviews require the current password and a verified authenticator session. Reviewed versioned tax replacements preserve prior rates on queued invoices and accepted pricing. Email retry uses the same immutable message/key within 23 hours; older uncertain outcomes require a verified read-only provider receipt, never invented delivery. Software release and live notification acceptance remain outstanding.
Automatic completed-month scheduling, reviewed admin pause/resume and tax mappings are locally verified.
Signed native Stripe events use bounded raw signature input and persisted provider invoice ownership, then fetch current payment state. Duplicate/out-of-order events and lease recovery cannot create or send invoices through reconciliation. Cancellation/termination/credits/refunds/disputes, admin MFA, hosted developer portal and actual Stripe sandbox acceptance remain unfinished. Hosted scheduling activation, deployment capacity and release approval are outstanding; no production activation is claimed.
Local invoice history exposes exact monetary strings and safe last-confirmed provider status, excluding provider identifiers and private evidence.
Review-required amounts may be stale and are not fresh payment evidence. Invoice workers, manual overdue decisions and a durable existing-admin-address email queue are locally verified; email provider acceptance does not prove inbox delivery. Monthly scheduling, signed Stripe billing events, credits/cancellation/disputes, actual provider sandbox acceptance and Software activation remain unfinished. No automatic suspension, Connect or fund distribution.
Local billing-account reads provide safe owner/admin/billing status and consent history.
Only a current owner with recent TOTP MFA can consent to invoices at their provider-verified email; the server captures email and reviewed organization name. Exact UUID receipts, seven-day expiry and current owner/email/epoch checks bind manual platform review. Customer setup is separate and requires activation, a dedicated CarSoft partner customer and stable idempotency. It creates no invoice, payment method, charge or API access and never reuses dealership subscription customers. Actual Stripe sandbox acceptance, monthly invoice orchestration, payment reconciliation integration, credits/cancellation and overdue notifications remain unfinished; no automated billing readiness is claimed.
Local billing periods provide read-only owner/admin/billing access with provider/TOTP identity.
Immutable completed UTC-month records bind exact terms, usage and calculations; monetary totals are exact strings. Only successful production app API requests count; OAuth/developer calls, failures and sandbox requests are excluded. Installation-day evidence begins with the ledger, without invented history. Revenue statements require the exact commercial window and currency; versioned corrections precede freezing and separately reviewed adjustments follow. Local Stripe issuance/reconciliation core has isolated protocol tests; customer provisioning, orchestration, signed webhooks, cancellation/credits, overdue notifications and actual Stripe sandbox acceptance remain incomplete. Production billing is not activated.
Local billing agreements contain individually reviewed immutable monthly terms.
Only current organization owners with recent TOTP MFA can accept or decline exact fingerprints. Offers expire after 14 days; one accepted agreement per UTC calendar month, with subsequent prices effective on a future month’s first day. Accepted terms cannot be rewritten. Acceptance creates no invoice, charge or API access. CarSoft fees will use its current Stripe account; partners collect their own fees. Overdue invoices require William’s manual decision. Automated metering, invoices, collection, reconciliation and notifications remain under implementation; production billing is not activated.
Local credential sharing requires a current owner/admin secret holder, separate recent-MFA recipient acceptance and manual platform review of live identities, custody purpose and private evidence.
Seven-day requests bind current client version, member epochs and exact fingerprints; one pending per client/recipient and 50 per organization. No raw secret is accepted, recovered or delivered. Share through a secure external channel only after approval. Offboarding any current holder retires the shared client. Approval creates no OAuth or dealership grant. Hosted portal, sandbox, full financial/billing and provider lifecycle acceptance remain incomplete. Not deployed.
Local organization invitations let owners invite admins/developers/billing/support and admins invite developers/billing/support.
They cannot create owners or claim platform review; platform bootstrap invitations remain separate. Tokens are shown once and only hashes stored. Exact retries return original metadata without exposing or replacing tokens. Acceptance checks live issuer identity, role and epoch; offboarding retires pending invitations. No email is sent automatically. Hosted team portal, provider enrollment/recovery/lifecycle, sandboxes, payments, billing and full launch acceptance remain unfinished. Not deployed.
Local owner-role transfers require a current owner, independent incoming-member MFA consent and manual platform review with live provider identity/email/MFA checks and private evidence.
Seven-day expiry, member epochs and immutable fingerprints bind the decision. Approval revokes outgoing membership and retires affected credentials while preserving other known holders and dealership consent. No credentials, installations or funds are created. Hosted provider lifecycle/recovery, sandboxes, payments, billing and full launch acceptance remain unfinished. Not deployed.
Local app registration requires an active owner/admin/developer and recent TOTP MFA.
A UUID request receipt recovers the original unpublished app; changed reuse conflicts and organizations are limited to 100 apps. Initial submissions require explicit baseRevisionId: null, manual exact-candidate review, domain proof and evidence. Atomic first revision approval creates no credentials or installations. Hosted signup/login/recovery, MFA/team self-service, isolated sandboxes and renewal alerts remain incomplete. Not deployed.
Local MFA-protected credential listing, issuance, rotation and revocation with reviewed redirects, version checks and one-time secrets.
UUID request receipts return original-client metadata on retries, never another secret. Current-secret custody governs offboarding; reissuance needs fresh dealership OAuth and cannot expand consent. Hosted identity/recovery, owner/team self-service, sandbox and provider acceptance remain unfinished. Not deployed.
Five local developer API paths use separate provider JWT authentication, verified email/TOTP MFA and current organization roles.
Immutable app updates and platform-reviewed one-use invitations do not establish hosted signup/login/recovery, MFA/team self-service, initial app registration, automatic credential offboarding rotation or sandbox readiness. Not deployed.
Local platform-admin exact-host DNS TXT ownership review before app approval, credential issuance and installation.
One-hour challenges, 30-day proofs and expiry/withdrawal gates require fresh dealer authorization after reproof. Enrollment/MFA/team recovery, isolated sandboxes and renewal alerts remain incomplete. Not deployed.
Local inventory marketing-gallery reads with separate media:read and inventory:read permissions.
Private authenticated JPEG downloads recheck access and strip metadata. Uploads, other attachments, protected real-storage acceptance and full launch readiness remain incomplete. Not deployed.
Local bounded synchronous exports and bulk jobs, with authenticated private JSONL downloads, cancellation and separate resource bulk permissions.
Large queued jobs, attachments, complete developer onboarding, billing and provider acceptance remain incomplete. Not deployed.
Latest local contract and Software integration guide.
Includes customer invoices, payment cancellation and subscription management. Admin revision consent and credential rotation are locally implemented; developer self-service and production readiness remain incomplete.
Local, unverified resource, intake, token, payment-intent and event-subscription contracts.
Not deployed; financial adapters and invoice/developer/export/billing interfaces remain incomplete.
Software-provided resource, intake and token contracts. Local and under verification; not deployed. Financial, event and developer interfaces are not included.
Read the draft API referenceRead the agreed boundaries and proposed integration model. Planned capabilities are explicitly labeled; no supported endpoint names are invented.
Read the planning guideDownload the planning guide. Versioned API schemas and examples will be published from reviewed Software releases when available.
View documentation downloads