tenant_Google Enterprise
Creates a new Google Enterprise with the provided details
Creates a new Google Enterprise record with the provided enrollment details.
Creates the Google Enterprise binding record for the tenant, typically as part of completing or recording the outcome of the EMM enrollment flow.
About Google Enterprise Record This endpoint stores the Google-side enterprise binding details (tokens, state, callback/signup URLs) tying the tenant to its Google EMM enrollment. It's generally used internally by the enrollment flow rather than called directly once enrollment is already complete.
Key Fields / Query Parameters
- google_enterprise_id — Google's identifier for the enterprise
- state — Enrollment state to record
- callback_url / signup_url — URLs used during the enrollment flow
- completion_token / enterprise_token — Tokens exchanged during enrollment
Common Use Cases
- Recording the outcome of a Google EMM enrollment flow
- Re-establishing a Google Enterprise record after a data recovery scenario
- Advanced/custom EMM onboarding tooling that manages enrollment state directly
Best Practices
- Prefer driving enrollment through /v2/emm/enrollment/begin/ and /complete/ rather than constructing this record manually, unless building custom onboarding tooling
- Keep completion_token and enterprise_token secure — do not log them in plaintext
- Confirm no existing record already exists for the tenant before creating a new one
Workflow
- Complete the standard enrollment flow (begin → Google sign-up → complete) where possible
- Use this endpoint directly only for advanced scenarios needing manual record creation
- Verify the resulting state via GET /v2/emm/details/
post/v2/emm/details/
Request
- Base URLhttps://develop-api.esper.cloud/api
- URLhttps://develop-api.esper.cloud/api/v2/emm/details/
- Authnone declared. Required headers: Authorization
Headers
Authorizationstring required
Bearer token for authorization
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 6 revisions of this API.