Not clear error message

To assist you effectively with the error you're encountering while creating an organization, could you please provide more details about the steps you took leading up to the error and any specific details about the request you made? This information will help in diagnosing the issue more accurately. Additionally, if you have access to the request body you sent, sharing that (while omitting any sensitive information) could be very helpful.

Dear @onderay
This is a new issue with details. I'm sure if user is already registered, I think that you can return user id and information about the user is existing in organization.
POST https://rapp.kinde.com/api/v1/user
{ "profile": { "given_name": "Egemen", "family_name": "lastname", "provided_id": "3cca561e-92a5-4460-8154-84f9be12cfb1" }, "organization_code": "org_4ddccf440d0a", "identities": [ { "type": "email", "details": { "email": "email+order2@gmail.com" } } ] }

I'm getting following error.

Response{protocol=http/1.1, code=400, message=Bad Request, url=https://rapp.kinde.com/api/v1/user}

I've checked API document to get information of user with email, howeverI couldn't find.

Based on the information provided in the context, here are a few things to check and consider:

Correct Endpoint and Base URL: Ensure that the base URL (https://rapp.kinde.com) is correct for the Kinde API you are trying to access. Typically, API base URLs are provided in the documentation or the API settings within your Kinde account.

Request Body Format: The request body you've shared seems correctly structured according to the Kinde Management API documentation. However, ensure that there are no trailing characters or spaces, especially in the URL (https://rapp.kinde.com/api/v1/user%7D seems to have an encoded '}' character at the end, which might be causing the issue).

Required Fields: According to the documentation, fields such as given_name, family_name, organization_code, and identities (with type and details) are necessary for creating a user. Your request body includes these, so you should be good on this front.

Duplicate User or Email: If the user or the email address (email+order2@gmail.com) already exists in the specified organization (org_4ddccf440d0a), the API might return an error depending on how it's designed to handle duplicate entries. The documentation does not explicitly mention how duplicates are handled, so consider checking if the user or email already exists.

Provided ID: You've included a provided_id in the profile object. Ensure that this field is supported and correctly used as per the API documentation. If provided_id is not expected in the user creation endpoint or is formatted incorrectly, it could be the source of the error.
Authentication: Ensure that your request includes the correct authentication headers. According to the documentation, you must authenticate your request using the kindeBearerAuth scheme.