TrigCode AI
    TemplatesShowcasePricing
    Help center

    Getting started

    Welcome to TrigCodeBuild your first appChoose an app typeWrite effective promptsNavigate the TrigCode workspace

    Building and editing

    Understand the build lifecycleEdit an app with conversationPreview and test your appWork with code and filesUse checkpoints and rollbackOrganize work with projects and templatesUse reference images and app secrets

    Export and deploy

    Export source codeConnect GitHub, GitLab, or BitbucketDeploy on TrigCodeDeploy to external providersPreview mobile apps and build an APKConnect a custom domain

    Plans, credits, and account

    Plans and feature accessCredits and action costsBilling, renewals, and plan changesAccount and security settings

    Teams and enterprise

    Teams workspacesRoles, budgets, and governanceConfigure SSO and SCIMShared prompts, usage, and audit history

    API and automation

    API authentication and scopesAPI task referenceAPI organization resource referenceReceive signed webhooks

    Troubleshooting

    Troubleshoot builds and editsTroubleshoot previewsTroubleshoot deployments and domainsTroubleshoot billing and creditsGet support
    Help/API and automation/API organization resource reference

    API and automation

    API organization resource reference

    7 min readReviewed 9 September 2026

    Reference the organization, projects, usage, and members endpoints.

    On this pageResource endpointsUsage windowsData handling

    Resource endpoints

    MethodEndpointScopeReturns
    GET/api/v1/orgusage:readWorkspace identity, effective plan, balance, seats, member count.
    GET/api/v1/projectsprojects:readPaginated projects and task counts.
    GET/api/v1/usageusage:readCredit balance and spend grouped by member, day, and reason.
    GET/api/v1/membersmembers:readMembers, email, role, and joined time.

    Usage windows

    GET /usage defaults to the current billing cycle. Pass days=30 or days=90 for a rolling window. total_spent comes from positive debit entries in the organization credit ledger; balance is the current organization credit balance.

    Examplebash
    curl 'https://trigcode.com/api/v1/usage?days=30' \
+  -H 'Authorization: Bearer tck_live_REPLACE_WITH_YOUR_KEY'

    Data handling

    • Dates are JSON ISO timestamps.
    • Plan is the current expiry-aware effective plan.
    • Project and task list results include pagination metadata.
    • Member responses contain workspace-visible identity fields; protect API keys accordingly.
    • Unknown resources inside another organization return not found rather than crossing the tenant boundary.
    Still need help?Open a support ticket from your workspace or contact the TrigCode team.
    Contact support

    Related guides

    API authentication and scopesCreate an organization API key and understand authentication, scopes, limits, and envelopes.API task referenceCreate builds, list tasks, poll status, read files, and download exports through API v1.Shared prompts, usage, and audit historyStandardize briefs, understand credit activity, and inspect workspace changes.
    PreviousAPI task referenceNextReceive signed webhooks

    On this page

    Resource endpointsUsage windowsData handling
    TrigCode AI

    Bring your ideas to life with AI.
    Build, refine, and make them yours.

    Start building

    Product

    • AI app builder
    • Templates
    • Showcase
    • Pricing
    • Teams & enterprise

    Build

    • Websites
    • Web apps
    • Mobile apps
    • Games
    • Dashboards
    • CRM
    • SaaS
    • Scheduling
    • AI assistants

    Resources

    • Help center
    • Building guides
    • Compare builders
    • Vibe coding explained
    • What you can build

    Company

    • About TrigCode
    • Contact us
    • Trust & security
    • Get support

    © 2026 THS CyberSecure Private Limited.All rights reserved.

    Privacy policyTerms of service