GraphQL API reference

Quick answer: Query exactly the fields you need, in one round trip.

Endpoint

POST https://api.cosmoquick.com/v1/graphql with same Bearer auth as REST.

Playground

api.cosmoquick.com/graphql/playground — schema introspection, query history, and saved snippets.

Step-by-step checklist

• Confirm you are in the correct CosmoQuick surface: Candidate Dashboard, Recruiter Dashboard, ATS, Tools, or Settings
• Search the command palette for the feature name before browsing menus manually
• Open the relevant object (job post, candidate, application, invoice, or workspace) and check its status
• Make one change at a time, save, refresh, and verify the expected result
• If the issue still appears, capture the page URL, screenshot, browser, account email, and last action before contacting support

Practical example

A common real-world case: a user signs up as a candidate, then realizes they need recruiter features such as posting jobs, Resume Rank, MIRA, or candidate pipelines. First check Settings → Account for account type or dual-mode controls. If switching is not available for your plan or workspace, export any candidate data you need, then either contact support to convert the account safely or create a fresh recruiter account with the correct work email.

Screenshot placeholder

[Screenshot placeholder: show the exact CosmoQuick screen, highlighted button, empty/error state, and the expected success state. Keep sensitive candidate, salary, invoice, and contact information blurred before sharing.]

Troubleshooting guidance

• If a button is missing, check your account type, plan, workspace role, and whether the page is available only on recruiter or candidate mode
• If data looks stale, refresh the page, clear filters, and check whether you are viewing the right workspace or role
• If search returns nothing, try broader terms, remove hard filters, and search by skill, role, company, email, or candidate name
• If a payment, activation, import, or integration fails, retry once and then send the error text plus screenshot to support
• For urgent hiring blockers, use WhatsApp support from the Help Center

Pro tips

• Map ATS stages 1:1 before turning on sync — mismatched stages create duplicates that are tedious to clean.
• Use scoped API tokens, not your master key, for third-party tools. You can rotate without breaking everything else.
• Webhook deliveries are retried 5 times with exponential backoff — log delivery IDs to make debugging trivial.

Common pitfalls

• Wide-scope OAuth: only grant 'write' to systems that actually need to push back data.
• Polling instead of using webhooks — you'll hit rate limits and miss real-time updates.
• Storing API tokens in client-side code. Always proxy through a server.

Frequently asked

Which ATS systems do you sync with?

Greenhouse, Lever, Ashby, Workable, JazzHR, Recruitee, and Personio out of the box. Others via Zapier/Make/Merge.dev.

Is there a rate limit on the API?

1000 requests/min/token for Pro, 5000/min for Team, custom for Enterprise. 429 responses include Retry-After headers.

Do you have a Zapier app?

Yes. Search 'CosmoQuick' on Zapier — 40+ triggers and actions are available.

Can I build my own integration?

Yes. REST + GraphQL APIs, OpenAPI spec at api.cosmoquick.com/docs, with sample SDKs in TypeScript, Python, and Go.

Key takeaways

• Most CosmoQuick issues come from account type, workspace context, plan limits, filters, or incomplete setup
• Recruiter tools and candidate tools intentionally live in different dashboards to protect privacy and reduce confusion
• The fastest fix is usually: verify mode → clear filters → inspect status → search docs → escalate with context
• Keep this article open while performing the steps so you can compare the expected and actual state

Next steps

• Browse all categories for related guides
• Open the Help Center home to keep exploring
• Still stuck? Contact our team — average reply under 4 hours on weekdays