# Retrieve the service provider configuration Returns Zuora’s service provider configuration. Endpoint: GET /scim/v2/ServiceProviderConfig Version: 2026-02-20 Security: bearerAuth ## Response 200 fields (application/json): - `schemas` (array) List of schema URNs that define the structure of the response. Example: ["urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"] - `patch` (object) Details about support for the PATCH method. Example: {"supported":true} - `patch.supported` (boolean) Indicates whether the PATCH method is supported. Example: true - `bulk` (object) Details about support for bulk operations. Example: {"supported":true,"maxOperations":1000,"maxPayloadSize":10000} - `bulk.supported` (boolean) Indicates whether bulk operations are supported. Example: true - `bulk.maxOperations` (integer) The maximum number of operations that can be performed in a single bulk request. Example: 1000 - `bulk.maxPayloadSize` (integer) The maximum size of the payload for a single bulk request, in bytes. Example: 10000 - `filter` (object) Details about support for filtering resources. Example: {"supported":true,"maxResults":100} - `filter.supported` (boolean) Indicates whether filtering is supported. Example: true - `filter.maxResults` (integer) The maximum number of results that can be returned in a single request when using filters. Example: 100 - `changePassword` (object) Details about support for password change operations. Example: {"supported":false} - `changePassword.supported` (boolean) Indicates whether password change operations are supported. - `sort` (object) Details about support for sorting resources. Example: {"supported":false} - `sort.supported` (boolean) Indicates whether sorting is supported. - `etag` (object) Details about support for ETag headers. Example: {"supported":false} - `etag.supported` (boolean) Indicates whether ETag headers are supported. - `authenticationSchemes` (array) List of authentication schemes supported by the service provider. Example: [{"name":"Client Credentials","description":"The client credentials (or other forms of client authentication) can be used as an authorization grant when the authorization scope is limited to the protected resources under the control of the client, or to protected resources previously arranged with the authorization server. Client credentials are used as an authorization grant typically when the client is acting on its own behalf (the client is also the resource owner) or is requesting access to protected resources based on an authorization previously arranged with the authorization server.\n","specUri":"https://www.rfc-editor.org/rfc/rfc6749#section-4.4","type":"oauth2","primary":true},{"name":"Authorization Grant","description":"An authorization grant is a credential representing the resource owner's authorization (to access its protected resources) used by the client to obtain an access token. This specification defines four grant types -- authorization code, implicit, resource owner password credentials, and client credentials -- as well as an extensibility mechanism for defining additional types.\n","specUri":"https://www.rfc-editor.org/rfc/rfc6749#section-4.1","type":"oauth2","primary":false}] - `authenticationSchemes.name` (string) The name of the authentication scheme. - `authenticationSchemes.description` (string) A description of how the authentication scheme works. - `authenticationSchemes.specUri` (string) A URI to the specification of the authentication scheme. - `authenticationSchemes.type` (string) The type of the authentication scheme (e.g., OAuth2). - `authenticationSchemes.primary` (boolean) Indicates whether this is the primary authentication scheme. - `meta` (object) Metadata about the service provider configuration. Example: {"resourceType":"ServiceProviderConfig","location":"http://localhost:9900/scim/v2/ServiceProviderConfig"} - `meta.resourceType` (string) Type of the resource returned (e.g., ServiceProviderConfig). Example: "ServiceProviderConfig" - `meta.location` (string) URI of the resource. Example: "http://localhost:9900/scim/v2/ServiceProviderConfig" ## Response 401 fields (application/json): - `success` (boolean) Indicates whether the operation was successful or not. - `reasons` (array) A list of reasons explaining why the request was unauthorized. Example: [{"message":"Unauthorized","code":"90000011"}] - `reasons.message` (string) A message describing the reason for the unauthorized error. Example: "Unauthorized" - `reasons.code` (string) An error code associated with the unauthorized error. Example: "90000011" ## Response 403 fields (application/json): - `timestamp` (string) The timestamp when the error occurred. Example: "2023-07-28T10:47:07.931+00:00" - `status` (integer) HTTP status code representing the error. Example: 403 - `error` (string) A brief description of the error. Example: "Forbidden" - `message` (string) A message explaining why access was forbidden. Example: "Admin access denied" - `path` (string) The path of the request that caused the error. Example: "/scim/v2/Groups" ## Response 404 fields (application/json): - `schemas` (array) A list of schema URNs that describe the structure of the error response. Example: ["urn:ietf:params:scim:api:messages:2.0:Error"] - `status` (string) HTTP status code representing the error. Example: "404" - `detail` (string) A detailed message explaining the resource not found error. Example: "Resource not found"