Choose your task
Check the protected operation
Plan requirements apply to individual operations. A successful read does not grant permission to create, publish or start another workflow. Check the plan requirements and limits on the endpoint page before writing data. A plan denial and an unavailable decision are different results. Where documented,403 entitlement_denied means the plan does not permit the operation. 503 temporarily_unavailable means the service could not establish the required facts. Do not treat either result as permission to continue.
Previews and billing metadata
Use the Connect preview below for your company’s plan-access decisions. A preview is a snapshot. It does not reserve quota, charge an account or authorize a later command. Billing-profile metadata is not a payment operation. Use the supported portal or a separately approved billing integration for payment and subscription work. Do not infer a financial API from a profile field or dashboard request.Preview plan access on Connect
SendPOST https://data.grdd.net/api/entitlements/check with a Core-issued Bearer access token and Content-Type: application/json. The token selects your company. The request does not accept a company, plan, usage, trial or exemption selector. It does not need Idempotency-Key or If-Match.
capabilities, an array of 1 to 18 recognized capability IDs. Use the capability for the operation you intend to perform:
A capability name is a plan check, not a reference for an otherwise undocumented API.
Preview response
200 returns companyId, preview: true and decisions, in request order. Each decision has these fields:
The operation checks access again before protected work. An
allowed preview does not guarantee later capacity. An unavailable decision is not permission to proceed.
Request-level failures use the Connect problem format, including 400 invalid_request, 401 unauthenticated, 403 forbidden or 503 temporarily_unavailable. These are separate from decision outcomes inside a 200 response.