Jump to Content
Identity Cloud Custom Provider API
RecipesAPI
Identity Cloud Custom Provider API
API
RecipesAPI

API

  • Identity Cloud Custom Provider API
  • API summary
  • Get started
  • API concepts
  • Other Identity Cloud APIs
  • Errors
    • 400
    • 403
    • 404
    • 415
    • 422

Custom Providers

  • /{customerId}/v2/config/low/services/engage-v2/apps
    • List your social login applicationsget
  • /{customerId}/v2/config/low/services/engage-v2/apps/{appId}
    • View a social login applicationget
  • /{customerId}/v2/config/low/services/engage-v2/apps/{appId}/custom-providers
    • List your custom providersget
    • Create a custom providerpost
  • /{customerId}/v2/config/low/services/engage-v2/apps/{appId}/custom-providers/{providerId}
    • View a custom providerget
    • Modify a custom providerput

422

Update failed. Typically occurs if your request body specifies a field that can’t be found in the provider being updated. This might occur because:

  • You misspelled a field name (protcol) or used incorrect letter casing in a field name (auth_URL).
  • You referenced a SAML-only field (e.g., idp_certificate) for an OpenID Connect or OAuth provider (or vice-versa).
Akamai TechDocs
Akamai.com
Linode.com
Contact us
Akamai support Linode support Share feedback
Try Akamai
Log in
Log out
Try Akamai

Akamai.com

Linode.com

Contact us Akamai support Linode support Share feedback

Log in
Log out