ENTITY developer reference
Application credentials
Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.
Browser testing and application access
The signed-in tester uses the current human session and permitted workspace context. It does not require a machine credential pasted into the browser. Application code uses an integration with the appropriate environment and scope, a recognisable name and a clear owner or steward.
Integration creation, secret delivery, rotation and revocation are not connected on these pages. No token endpoint, audience, scope value or credential flow is supplied until its release is qualified.
Keep the credential types separate
The data API requires a validated OAuth access token. An identity-provider ID token, a browser session cookie or a client secret is not a substitute. Follow the released integration instructions for the selected environment and audience.
A technical credential does not grant purchasing authority, workspace membership or permission to broaden a delegation. Confirm the intended environment, workspace, scope and usable allowance before deliberate work.
Save a newly delivered secret
Use the protected one-time delivery flow and your approved secret store. Do not place secrets in a public repository, browser local storage, screenshots, exported API-client environments or support messages. If delivery is lost, use the supported reissue or rotation flow; an old secret is not displayed again.
Rotate or revoke a suspected compromised integration and review the stated effect. Do not assume that revocation cancels or refunds an earlier admitted operation. A later authentication refusal does not establish that an earlier uncertain request had no effect.
Preserve the original operation during recovery
Keep the original intent, key, creation time and compatible recovery contract. Restore current authority and use the separately permitted original-operation status path. A successful sign-in or a newly issued token is not permission to replay a mutation under a fresh key.
Next: inspect an API collection safely, prepare an MCP client, or check release compatibility.