Summary and recommendation
Around never released a public API, SDK, or developer tooling during its operational lifetime. The product was fully shut down on March 31, 2025. No endpoints, authentication methods, SCIM provisioning, SSO integrations, webhooks, or rate-limit contracts exist - there is nothing to integrate against.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A - Product discontinued |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: Around did not offer a public webhook system. The product was discontinued on March 31, 2025.
Alternative event strategy: Miro Video Calls (features integrated from Around); Miro does offer its own API at https://developers.miro.com
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A - Product discontinued
- Endpoint: Not documented
Limitations:
- Around was shut down on March 31, 2025.
- No SCIM provisioning was ever offered.
- No SSO or IdP integrations (Okta, Entra, Google Workspace, OneLogin) were supported.
Common scenarios
There are no viable API automation scenarios for Around. The product is gone.
If your automation requirements relate to the features Miro absorbed from Around, those fall under Miro's own API surface at https://developers.miro.com. For teams evaluating automated user lifecycle management across active video-call or collaboration tools, an MCP server with ~100 deep IT/identity integrations provides a more durable foundation than building point-to-point against any single vendor.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary trap here is legacy tooling or runbooks that still reference Around as an integration target. Any connector, IdP rule, or SCIM configuration pointed at Around is inert and should be removed to avoid false confidence in provisioning coverage.
Around never supported Okta, Entra ID, Google Workspace, or OneLogin integrations, so no deprovisioning automation was ever in place - meaning offboarding cleanup must be handled manually against whatever IdP records remain.
Automate Around workflows without one-off scripts
Stitchflow builds and maintains identity workflows for your exact setup. We cover every app, including the ones without APIs, and run deterministic trigger-to-report workflows with human approvals where they matter.
