What to send
Prepare the business and technical context.
Identify the business and the server-side work your integration needs to perform. Use a company email address and name a technical contact who can explain the commerce source, credential handling and expected request volume. The API reference helps you identify the documented operations without sharing customer payloads.
| Information | Why it matters |
|---|---|
| Legal company name and website | Identifies the organization requesting a tenant-scoped connection. |
| Integration use case | Explains the qualifying commerce activity and the operation your server needs to perform. |
| Commerce platform and source system | Establishes whether an existing connector or direct order API is appropriate. |
| Expected request volume | Provides operational context for staging validation and production readiness. |
| Technical contact | Names the person responsible for credentials, retries, monitoring and incident response. |
| Target launch date | Helps sequence access review, staging validation and the separate production decision. |
Do not include customer records, card numbers, bank details, passwords, API keys, webhook signing secrets or production payloads in the access request.
Contact form
Submit your developer access request.
Fields marked with an asterisk are required. This form starts a review; it does not create credentials automatically.
Review sequence
Understand the steps between a request and access.
- 01
Business and use-case review
We confirm the requesting organization, intended merchant program and integration owner.
- 02
Contract and data-flow review
We identify the operations, fields, scope, event subscriptions and prohibited-data boundary.
- 03
Staging provisioning
Approved integrations receive environment-specific access for controlled validation with non-production records.
- 04
Production readiness decision
Production access is provisioned separately after credential handling, idempotency, error handling and operational ownership are confirmed.
Possible outcomes
The review determines the appropriate next step.
A request may need clarification or a different integration approach. Staging access, where appropriate, is separate from the decision to provision production credentials.
- More information
- We may ask for clarification about ownership, data sources, traffic or the intended rebate workflow.
- Existing connector
- The use case may be better served by a supported commerce integration instead of a direct API credential.
- Staging access
- An approved technical scope can move to controlled staging validation.
- Not supported
- A request that conflicts with the published data boundary or current API contract will not be provisioned.