How do I request product or integration access?
3 min readAccess is specific to the requested product and operations. Describe the workflow, intended environment, and the read or write capabilities you need. A public product page or API example is not an access grant.
Describe the work you want to do
Tell the team which product interests you, the intended business outcome, and whether you need to read information, evaluate a proposal, or perform an action. Include the relevant environment and network where applicable. A request such as “show wallet readiness in our application” is easier to scope than “enable everything.” You do not need a complete technical design, but a concrete use case helps identify the right prerequisites and responsible people.
Ask for an explicit evaluation boundary
Confirm which operations are available, what credentials and scopes are needed, and whether the test uses non-production data. Ask which supporting services or resource relationships must already exist. Record any operation that remains outside the evaluation, especially signing, deployment, or funds movement. An API example is a guide to a request shape, not permission to use it. Access to one module should not be assumed to grant access to another.
Keep the access request free of secrets
Use the established contact route and share a sanitized workflow description. If an existing public record is relevant, include its URL and network. Do not send passwords, private signing material, or recovery information to speed up onboarding. Once access is agreed, begin with a bounded test and verify both the permitted result and the expected refusal outside that scope. This gives your team a documented starting point for integration rather than a vague assumption about what the account can do.
What to do next
Contact the team with your evaluation scope so the prerequisites and enabled operations can be confirmed.