clerk-http-client 0.0.1

data/spec/api/organization_domain_api_spec.rb

@@ -0,0 +1,49 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::OrganizationDomainApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationDomainApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::OrganizationDomainApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationDomainApi' do
+    it 'should create an instance of OrganizationDomainApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::OrganizationDomainApi)
+    end
+  end
+
+  # unit tests for update_organization_domain
+  # Update an organization domain.
+  # Updates the properties of an existing organization domain.
+  # @param organization_id The ID of the organization the domain belongs to
+  # @param domain_id The ID of the domain
+  # @param update_organization_domain_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationDomain]
+  describe 'update_organization_domain test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/organization_domains_api_spec.rb

@@ -0,0 +1,77 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::OrganizationDomainsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationDomainsApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::OrganizationDomainsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationDomainsApi' do
+    it 'should create an instance of OrganizationDomainsApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::OrganizationDomainsApi)
+    end
+  end
+
+  # unit tests for create_organization_domain
+  # Create a new organization domain.
+  # Creates a new organization domain. By default the domain is verified, but can be optionally set to unverified.
+  # @param organization_id The ID of the organization where the new domain will be created.
+  # @param create_organization_domain_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationDomain]
+  describe 'create_organization_domain test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_organization_domain
+  # Remove a domain from an organization.
+  # Removes the given domain from the organization.
+  # @param organization_id The ID of the organization the domain belongs to
+  # @param domain_id The ID of the domain
+  # @param [Hash] opts the optional parameters
+  # @return [DeletedObject]
+  describe 'delete_organization_domain test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_organization_domains
+  # Get a list of all domains of an organization.
+  # Get a list of all domains of an organization.
+  # @param organization_id The organization ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [String] :verified Filter domains by their verification status. `true` or `false`
+  # @option opts [String] :enrollment_mode Filter domains by their enrollment mode
+  # @return [OrganizationDomains]
+  describe 'list_organization_domains test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/organization_invitations_api_spec.rb

@@ -0,0 +1,133 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::OrganizationInvitationsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationInvitationsApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::OrganizationInvitationsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationInvitationsApi' do
+    it 'should create an instance of OrganizationInvitationsApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::OrganizationInvitationsApi)
+    end
+  end
+
+  # unit tests for create_organization_invitation
+  # Create and send an organization invitation
+  # Creates a new organization invitation and sends an email to the provided `email_address` with a link to accept the invitation and join the organization. You can specify the `role` for the invited organization member.  New organization invitations get a \"pending\" status until they are revoked by an organization administrator or accepted by the invitee.  The request body supports passing an optional `redirect_url` parameter. When the invited user clicks the link to accept the invitation, they will be redirected to the URL provided. Use this parameter to implement a custom invitation acceptance flow.  You can specify the ID of the user that will send the invitation with the `inviter_user_id` parameter. That user must be a member with administrator privileges in the organization. Only \"admin\" members can create organization invitations.  You can optionally provide public and private metadata for the organization invitation. The public metadata are visible by both the Frontend and the Backend whereas the private ones only by the Backend. When the organization invitation is accepted, the metadata will be transferred to the newly created organization membership.
+  # @param organization_id The ID of the organization for which to send the invitation
+  # @param create_organization_invitation_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationInvitation]
+  describe 'create_organization_invitation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_organization_invitation_bulk
+  # Bulk create and send organization invitations
+  # Creates new organization invitations in bulk and sends out emails to the provided email addresses with a link to accept the invitation and join the organization. You can specify a different `role` for each invited organization member. New organization invitations get a \"pending\" status until they are revoked by an organization administrator or accepted by the invitee. The request body supports passing an optional `redirect_url` parameter for each invitation. When the invited user clicks the link to accept the invitation, they will be redirected to the provided URL. Use this parameter to implement a custom invitation acceptance flow. You can specify the ID of the user that will send the invitation with the `inviter_user_id` parameter. Each invitation can have a different inviter user. Inviter users must be members with administrator privileges in the organization. Only \"admin\" members can create organization invitations. You can optionally provide public and private metadata for each organization invitation. The public metadata are visible by both the Frontend and the Backend, whereas the private metadata are only visible by the Backend. When the organization invitation is accepted, the metadata will be transferred to the newly created organization membership.
+  # @param organization_id The organization ID.
+  # @param create_organization_invitation_bulk_request_inner 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationInvitations]
+  describe 'create_organization_invitation_bulk test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_organization_invitation
+  # Retrieve an organization invitation by ID
+  # Use this request to get an existing organization invitation by ID.
+  # @param organization_id The organization ID.
+  # @param invitation_id The organization invitation ID.
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationInvitation]
+  describe 'get_organization_invitation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_instance_organization_invitations
+  # Get a list of organization invitations for the current instance
+  # This request returns the list of organization invitations for the instance. Results can be paginated using the optional `limit` and `offset` query parameters. You can filter them by providing the 'status' query parameter, that accepts multiple values. You can change the order by providing the 'order' query parameter, that accepts multiple values. You can filter by the invited user email address providing the `query` query parameter. The organization invitations are ordered by descending creation date by default.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [String] :order_by Allows to return organization invitations in a particular order. At the moment, you can order the returned organization invitations either by their `created_at` or `email_address`. In order to specify the direction, you can use the `+/-` symbols prepended in the property to order by. For example, if you want organization invitations to be returned in descending order according to their `created_at` property, you can use `-created_at`. If you don't use `+` or `-`, then `+` is implied. Defaults to `-created_at`.
+  # @option opts [String] :status Filter organization invitations based on their status
+  # @option opts [String] :query Filter organization invitations based on their `email_address`
+  # @return [OrganizationInvitationsWithPublicOrganizationData]
+  describe 'list_instance_organization_invitations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_organization_invitations
+  # Get a list of organization invitations
+  # This request returns the list of organization invitations. Results can be paginated using the optional `limit` and `offset` query parameters. You can filter them by providing the 'status' query parameter, that accepts multiple values. The organization invitations are ordered by descending creation date. Most recent invitations will be returned first. Any invitations created as a result of an Organization Domain are not included in the results.
+  # @param organization_id The organization ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [String] :status Filter organization invitations based on their status
+  # @return [OrganizationInvitations]
+  describe 'list_organization_invitations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_pending_organization_invitations
+  # Get a list of pending organization invitations
+  # This request returns the list of organization invitations with \"pending\" status. These are the organization invitations that can still be used to join the organization, but have not been accepted by the invited user yet. Results can be paginated using the optional `limit` and `offset` query parameters. The organization invitations are ordered by descending creation date. Most recent invitations will be returned first. Any invitations created as a result of an Organization Domain are not included in the results.
+  # @param organization_id The organization ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @return [OrganizationInvitations]
+  describe 'list_pending_organization_invitations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for revoke_organization_invitation
+  # Revoke a pending organization invitation
+  # Use this request to revoke a previously issued organization invitation. Revoking an organization invitation makes it invalid; the invited user will no longer be able to join the organization with the revoked invitation. Only organization invitations with \"pending\" status can be revoked. The request accepts the `requesting_user_id` parameter to specify the user which revokes the invitation. Only users with \"admin\" role can revoke invitations.
+  # @param organization_id The organization ID.
+  # @param invitation_id The organization invitation ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [RevokeOrganizationInvitationRequest] :revoke_organization_invitation_request 
+  # @return [OrganizationInvitation]
+  describe 'revoke_organization_invitation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/organization_memberships_api_spec.rb

@@ -0,0 +1,118 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::OrganizationMembershipsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationMembershipsApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::OrganizationMembershipsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationMembershipsApi' do
+    it 'should create an instance of OrganizationMembershipsApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::OrganizationMembershipsApi)
+    end
+  end
+
+  # unit tests for create_organization_membership
+  # Create a new organization membership
+  # Adds a user as a member to the given organization. Only users in the same instance as the organization can be added as members.  This organization will be the user's [active organization] (https://clerk.com/docs/organizations/overview#active-organization) the next time they create a session, presuming they don't explicitly set a different organization as active before then.
+  # @param organization_id The ID of the organization where the new membership will be created
+  # @param create_organization_membership_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationMembership]
+  describe 'create_organization_membership test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_organization_membership
+  # Remove a member from an organization
+  # Removes the given membership from the organization
+  # @param organization_id The ID of the organization the membership belongs to
+  # @param user_id The ID of the user that this membership belongs to
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationMembership]
+  describe 'delete_organization_membership test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for instance_get_organization_memberships
+  # Get a list of all organization memberships within an instance.
+  # Retrieves all organization user memberships for the given instance.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [String] :order_by Sorts organizations memberships by phone_number, email_address, created_at, first_name, last_name or username. By prepending one of those values with + or -, we can choose to sort in ascending (ASC) or descending (DESC) order.
+  # @return [OrganizationMemberships]
+  describe 'instance_get_organization_memberships test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_organization_memberships
+  # Get a list of all members of an organization
+  # Retrieves all user memberships for the given organization
+  # @param organization_id The organization ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [String] :order_by Sorts organizations memberships by phone_number, email_address, created_at, first_name, last_name or username. By prepending one of those values with + or -, we can choose to sort in ascending (ASC) or descending (DESC) order.\"
+  # @return [OrganizationMemberships]
+  describe 'list_organization_memberships test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_organization_membership
+  # Update an organization membership
+  # Updates the properties of an existing organization membership
+  # @param organization_id The ID of the organization the membership belongs to
+  # @param user_id The ID of the user that this membership belongs to
+  # @param update_organization_membership_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationMembership]
+  describe 'update_organization_membership test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_organization_membership_metadata
+  # Merge and update organization membership metadata
+  # Update an organization membership's metadata attributes by merging existing values with the provided parameters. Metadata values will be updated via a deep merge. Deep means that any nested JSON objects will be merged as well. You can remove metadata keys at any level by setting their value to `null`.
+  # @param organization_id The ID of the organization the membership belongs to
+  # @param user_id The ID of the user that this membership belongs to
+  # @param update_organization_membership_metadata_request 
+  # @param [Hash] opts the optional parameters
+  # @return [OrganizationMembership]
+  describe 'update_organization_membership_metadata test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/organizations_api_spec.rb

@@ -0,0 +1,139 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::OrganizationsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationsApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::OrganizationsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationsApi' do
+    it 'should create an instance of OrganizationsApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::OrganizationsApi)
+    end
+  end
+
+  # unit tests for create_organization
+  # Create an organization
+  # Creates a new organization with the given name for an instance. In order to successfully create an organization you need to provide the ID of the User who will become the organization administrator. You can specify an optional slug for the new organization. If provided, the organization slug can contain only lowercase alphanumeric characters (letters and digits) and the dash \"-\". Organization slugs must be unique for the instance. You can provide additional metadata for the organization and set any custom attribute you want. Organizations support private and public metadata. Private metadata can only be accessed from the Backend API. Public metadata can be accessed from the Backend API, and are read-only from the Frontend API. The `created_by` user will see this as their [active organization] (https://clerk.com/docs/organizations/overview#active-organization) the next time they create a session, presuming they don't explicitly set a different organization as active before then.
+  # @param create_organization_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Organization]
+  describe 'create_organization test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_organization
+  # Delete an organization
+  # Deletes the given organization. Please note that deleting an organization will also delete all memberships and invitations. This is not reversible.
+  # @param organization_id The ID of the organization to delete
+  # @param [Hash] opts the optional parameters
+  # @return [DeletedObject]
+  describe 'delete_organization test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_organization_logo
+  # Delete the organization's logo.
+  # @param organization_id The ID of the organization for which the logo will be deleted.
+  # @param [Hash] opts the optional parameters
+  # @return [Organization]
+  describe 'delete_organization_logo test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_organization
+  # Retrieve an organization by ID or slug
+  # Fetches the organization whose ID or slug matches the provided `id_or_slug` URL query parameter.
+  # @param organization_id The ID or slug of the organization
+  # @param [Hash] opts the optional parameters
+  # @option opts [Boolean] :include_members_count Flag to denote whether or not the organization's members count should be included in the response.
+  # @return [Organization]
+  describe 'get_organization test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_organizations
+  # Get a list of organizations for an instance
+  # This request returns the list of organizations for an instance. Results can be paginated using the optional `limit` and `offset` query parameters. The organizations are ordered by descending creation date. Most recent organizations will be returned first.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Float] :limit Applies a limit to the number of results returned. Can be used for paginating the results together with `offset`.
+  # @option opts [Float] :offset Skip the first `offset` results when paginating. Needs to be an integer greater or equal to zero. To be used in conjunction with `limit`.
+  # @option opts [Boolean] :include_members_count Flag to denote whether the member counts of each organization should be included in the response or not.
+  # @option opts [String] :query Returns organizations with ID, name, or slug that match the given query. Uses exact match for organization ID and partial match for name and slug.
+  # @option opts [String] :order_by Allows to return organizations in a particular order. At the moment, you can order the returned organizations either by their `name`, `created_at` or `members_count`. In order to specify the direction, you can use the `+/-` symbols prepended in the property to order by. For example, if you want organizations to be returned in descending order according to their `created_at` property, you can use `-created_at`. If you don't use `+` or `-`, then `+` is implied. Defaults to `-created_at`.
+  # @return [Organizations]
+  describe 'list_organizations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for merge_organization_metadata
+  # Merge and update metadata for an organization
+  # Update organization metadata attributes by merging existing values with the provided parameters. Metadata values will be updated via a deep merge. Deep meaning that any nested JSON objects will be merged as well. You can remove metadata keys at any level by setting their value to `null`.
+  # @param organization_id The ID of the organization for which metadata will be merged or updated
+  # @param merge_organization_metadata_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Organization]
+  describe 'merge_organization_metadata test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_organization
+  # Update an organization
+  # Updates an existing organization
+  # @param organization_id The ID of the organization to update
+  # @param update_organization_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Organization]
+  describe 'update_organization test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for upload_organization_logo
+  # Upload a logo for the organization
+  # Set or replace an organization's logo, by uploading an image file. This endpoint uses the `multipart/form-data` request content type and accepts a file of image type. The file size cannot exceed 10MB. Only the following file content types are supported: `image/jpeg`, `image/png`, `image/gif`, `image/webp`, `image/x-icon`, `image/vnd.microsoft.icon`.
+  # @param organization_id The ID of the organization for which to upload a logo
+  # @param file 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :uploader_user_id The ID of the user that will be credited with the image upload.
+  # @return [OrganizationWithLogo]
+  describe 'upload_organization_logo test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/phone_numbers_api_spec.rb

@@ -0,0 +1,84 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::PhoneNumbersApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'PhoneNumbersApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::PhoneNumbersApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of PhoneNumbersApi' do
+    it 'should create an instance of PhoneNumbersApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::PhoneNumbersApi)
+    end
+  end
+
+  # unit tests for create_phone_number
+  # Create a phone number
+  # Create a new phone number
+  # @param create_phone_number_request 
+  # @param [Hash] opts the optional parameters
+  # @return [PhoneNumber]
+  describe 'create_phone_number test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_phone_number
+  # Delete a phone number
+  # Delete the phone number with the given ID
+  # @param phone_number_id The ID of the phone number to delete
+  # @param [Hash] opts the optional parameters
+  # @return [DeletedObject]
+  describe 'delete_phone_number test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_phone_number
+  # Retrieve a phone number
+  # Returns the details of a phone number
+  # @param phone_number_id The ID of the phone number to retrieve
+  # @param [Hash] opts the optional parameters
+  # @return [PhoneNumber]
+  describe 'get_phone_number test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_phone_number
+  # Update a phone number
+  # Updates a phone number
+  # @param phone_number_id The ID of the phone number to update
+  # @param update_phone_number_request 
+  # @param [Hash] opts the optional parameters
+  # @return [PhoneNumber]
+  describe 'update_phone_number test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/proxy_checks_api_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#Clerk Backend API
+
+#The Clerk REST Backend API, meant to be accessed by backend servers.  ### Versions  When the API changes in a way that isn't compatible with older versions, a new version is released. Each version is identified by its release date, e.g. `2021-02-05`. For more information, please see [Clerk API Versions](https://clerk.com/docs/backend-requests/versioning/overview).   Please see https://clerk.com/docs for more information.
+
+The version of the OpenAPI document: v1
+Contact: support@clerk.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.9.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ClerkHttpClient::ProxyChecksApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ProxyChecksApi' do
+  before do
+    # run before each test
+    @api_instance = ClerkHttpClient::ProxyChecksApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ProxyChecksApi' do
+    it 'should create an instance of ProxyChecksApi' do
+      expect(@api_instance).to be_instance_of(ClerkHttpClient::ProxyChecksApi)
+    end
+  end
+
+  # unit tests for verify_domain_proxy
+  # Verify the proxy configuration for your domain
+  # This endpoint can be used to validate that a proxy-enabled domain is operational. It tries to verify that the proxy URL provided in the parameters maps to a functional proxy that can reach the Clerk Frontend API.  You can use this endpoint before you set a proxy URL for a domain. This way you can ensure that switching to proxy-based configuration will not lead to downtime for your instance.  The `proxy_url` parameter allows for testing proxy configurations for domains that don't have a proxy URL yet, or operate on a different proxy URL than the one provided. It can also be used to re-validate a domain that is already configured to work with a proxy.
+  # @param verify_domain_proxy_request 
+  # @param [Hash] opts the optional parameters
+  # @return [ProxyCheck]
+  describe 'verify_domain_proxy test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end