Your developer workspace.
Sign in, create scoped API keys, follow your usage, and manage a personal or shared workspace.
On this page
A home for your integrations
Open the developer console and sign in with Google or email. New accounts start with a personal workspace on the Free plan. The console brings your API keys, usage, billing, and account settings together.
Use the workspace switcher to create an organization or select one you belong to. Every workspace has its own keys, allowance, and subscription. Organization members can view the console; organization administrators can create or revoke keys and manage billing.
The public REST gateway is being connected. Creating a console account or key does not mean data requests are enabled. Check the connection notice in your console before integrating. Disabled deployments return HTTP 503. Stripe is initially configured for test payments where available.
Create and protect your API keys
In API keys, choose Create API key, give the integration a name, select its permissions, and choose an expiration of 30 days, 90 days, one year, or no expiration. Ninety days is the default. Create a separate key for each integration.
Copy the secret when it appears and save it in a server-side environment variable or secret manager. The complete secret is displayed once and cannot be retrieved later. The key list only shows a prefix. Never embed a key in frontend code, commit it to a repository, or place it in a URL.
To rotate a key, create and deploy a replacement, then revoke the old key. Revocation takes effect immediately and cannot be undone. Expired and revoked keys cannot authenticate.
markets:readScopeMarket and event data, discovery, and other market endpoints.
traders:readScopeLeaderboards, wallet and trader profiles, holders, and positions.
analytics:readScopeDeeper analytics including cohorts, funding, correlations, intelligence, and cross-platform analysis.
Make your first authenticated request
/api/v1/leaderboard/globalRESTOnce enabled, the production developer gateway base URL is https://implyra.com/api/v1. Use the exact base URL shown by your console for your environment. Append an endpoint path such as /leaderboard/global and send your key in the Authorization: Bearer header.
Set IMPLYRA_API_URL to the console’s gateway base URL and IMPLYRA_CUSTOMER_KEY to the secret you saved. Run requests from your server. This leaderboard example requires traders:read and consumes 5 credits on success.
curl --fail-with-body \
"$IMPLYRA_API_URL/leaderboard/global?limit=5&advanced=true" \
--header "Authorization: Bearer $IMPLYRA_CUSTOMER_KEY"Console keys authenticate only at the enabled developer gateway. Private enterprise origin URLs and streaming services use their own access configuration. A console sign-in session is not an API credential, and a console API key does not grant streaming access.
Credits, limits, and usage
An API request and a credit are different units. Each accepted operation has a fixed credit cost based on the endpoint. Your allowance and request rate are shared across all keys in a workspace.
Successful market GET requests cost 1 credit, market POST requests and trader endpoints cost 5 credits, and analytics endpoints cost 10 credits. For example, the trader leaderboard costs 5 credits and market discovery costs 5 credits. Failed upstream requests are not charged credits.
The console shows requests, errors, and credits for the current period, with a daily breakdown in UTC and a CSV export. Successful responses include X-Credits-Cost, X-Credits-Remaining, X-Credits-Limit, and X-Credits-Reset headers.
Usage is capped. There are no automatic overage charges: requests that would exceed the allowance are rejected. Free allowances reset by calendar month in UTC; paid allowances follow the active subscription period shown in your console.
Free$0 / month1,000 monthly credits, 30 requests per minute, 1 active API key. All three scopes are available for evaluation.
Builder$49 / month100,000 monthly credits, 300 requests per minute, 3 active API keys.
Pro$199 / month1,000,000 monthly credits, 600 requests per minute, 10 active API keys.
Prices are shown in USD before applicable taxes. These are the initial plan allowances; review the current console and Stripe checkout before subscribing. Enterprise arrangements are handled separately.
Billing through Stripe
Choose Builder or Pro in Billing to open Stripe checkout. Review the amount and terms before confirming. Opening checkout does not charge you. Where the console shows Test mode, checkout uses Stripe test payments and makes no real charges.
A workspace’s plan updates after Stripe confirms its subscription. If you have returned from checkout and the plan is still updating, use Refresh in the console. Canceling checkout leaves your existing plan unchanged.
Use Manage billing to open the Stripe customer portal for your workspace. Available options include payment details, invoices, and subscription management. Only workspace administrators can open checkout or manage the organization’s billing.
When a request needs attention
401 UnauthorizedAuthenticationSupply a valid Bearer key. Check whether the key has expired or been revoked. Console session errors require signing in again.
403 ForbiddenPermissionCheck that the API key has the required scope and the plan allows that operation. Managing organization keys or billing also requires administrator access.
429 Too Many RequestsUsage limitCheck the response error code and your console usage. A per-minute limit requires waiting; an exhausted monthly allowance requires a new period or an eligible plan change.
503 Service UnavailableConnectionThe developer gateway or a required service is not ready on this deployment. Check the console connection notice and contact support if it persists.