Retrieve Organization Connections

Learn how to retrieve Organization connections using the Auth0 Management API.

Manage Organization Connections via new endpoints and attributes is in Early Access as part of the My Organization API and Embeddable UI Components. By using this feature, you agree to the applicable Free Trial terms in Okta’s Master Subscription Agreement. To learn more about Auth0’s product release cycle, read Product Release Stages.

When working with Auth0 Organizations programmatically, you may need to retrieve a list of connections for an Organization.

You can view the connections associated with an Organization using either the Auth0 Dashboard or the Management API.

Auth0 Dashboard

1. Navigate to Auth0 Dashboard > Organizations, and select the organization.
2. Select the Connections view.

Management API

Make a GET call to the Get Organization Connections endpoint. Be sure to replace the ORG_ID and MGMT_API_ACCESS_TOKEN placeholder values with your organization ID and Management API Access Token, respectively.

Find Your Auth0 Domain

If your Auth0 domain is your tenant name, your regional subdomain (unless your tenant is in the US region and was created before June 2020), plus .auth0.com. For example, if your tenant name were travel0, your Auth0 domain name would be travel0.us.auth0.com. (If your tenant were in the US and created before June 2020, then your domain name would be https://travel0.auth0.com.)

If you are using custom domains, this should be your custom domain name.

Value	Description
ORG_ID	ID of the Organization for which you want to retrieve connections.
MGMT_API_ACCESS_TOKEN	Access Token for the Management API with the scope read:organization_connections.

Response status codes

Possible response status codes are as follows:

Status code	Error code	Message	Cause
200		Connections successfully retrieved.
400	invalid_body	Invalid request body. The message will vary depending on the cause.	The request payload is not valid.
401		Invalid token.
401		Invalid signature received for JSON Web Token validation.
401		Client is not global.
403	insufficient_scope	Insufficient scope; expected any of: read:organization_connections.	Tried to read/write a field that is not allowed with provided bearer token scopes.
429		Too many requests. Check the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers.