Accounts/Developers

You can view and manage registered user and developer accounts on the Portal. You can create new users, update existing user information, change account statuses to Active or Disabled, or completely delete accounts. You can search and filter by email, full name, organization, and status.

You can search and filter on this page based on the following information:

• Email
• Full Name
• Organization
• Status (Enabled / Disabled)

Click the ”+ New” button to create a new user.

To update an existing user’s information, go to the Edit option from the menu (three dots) on the relevant row.

Since the necessary permissions for both operations are found in the System Administrator (System Admin) role; users with this permission can create new users, update existing user information, and delete user accounts. Detailed explanations of these settings are given below.

Field Name	Description	Detailed Information
Enable	User’s account status can be set as active/passive.	If set to passive, the user receives the warning “Your account has been disabled. You can contact the Portal Manager.” when trying to log in. When left active, the user can log into the system.
Organization Manager	Grants the user administrative authority for the organization they belong to.	When enabled, the user gains the authority to manage other users, applications, and settings in the organization.
Email	Email address the user will use to log into the system.	Must be unique. This is the address where notification, approval, and password reset emails are sent. Example: [e-mail]
Full Name	User’s first and last name.	Displayed in profile and contact information. Example: Test User
Phone	User’s contact phone number.	Optional field. Left empty in the image.
Password	Password the user will use for portal login.	System can automatically generate a strong password or user can enter it manually. Can be reset via email using the “Forgot my password” option.
Organization	Organization the user belongs to is selected.	This selection determines which products the user can access. Example: Organization-3
Description	Role or task information can be added for the user.	Example: (Team Lead). This field is used to specify roles such as “Team Lead”, “DevOps Engineer”.

All applications and their details belonging to that person are listed. Fields are explained in the table below:

Field Name	Description	Detailed Information
App (Application Name)	Name of the application the user accesses or creates.	Application represents API connections registered to the Product on the portal. Example: Application 1
Description	Short description of the application.	Example: Test Application
Created Date	Date and time the application was created in the system.	Example: 07/11/2025 14:09:38
Reference Id	Unique identification number that identifies the application within the system.	Example: 87377cc7-e8aa-4820-875d-2aaabb5622b8

Appearance in Portal Interface

After users become members of the Apinizer portal and their accounts are approved, they can manage their profile information. However, they can update all information except the email address. Profile updates allow users to ensure the accuracy and currency of their personal information.

Users Can View and Edit Their Information

On the Portal, users can easily view and edit their own account information when needed. You can follow these steps to perform this operation:

Viewing Account Information:

• Email Address: User’s email address is specified at the top of the profile page. Also, if you are an organization manager, an “Organization Manager” label appears next to the email address.
• Full Name: User’s first and last name are displayed on the profile screen and can be edited.
• Phone Number: Phone number can also be viewed and updated in the same way.
• Description: User can add personal information or organization-related descriptions to the profile description section.

Changing Password:

• User clicks the “Change Password” button for password change, enters their current password, and creates a new password. They need to enter it again to verify the new password.

You need to click the “Apply Changes” button to save the changes you made.

It is explained visually below.

API Portal and Apinizer Manager user management:

Operation	Portal User	Manager Admin
Edit profile information	Name, phone, description	All fields
Email change	Mostly restricted	Free
Password reset	From profile screen	Reset / lock
Account approval	Only views	Approve / Reject
Organization management	If authorized	Full control
API access token generation	If authorized	Viewing, revocation
Account deletion	Authorized organization manager	Full authority

Creating and Managing API Access Tokens

On the Apinizer portal, creating and managing API access tokens is quite simple. API tokens allow your application to access Apinizer APIs.

• Allows you to generate bearer tokens for machine-to-machine calls on behalf of the API Portal account (CLI, automation, third-party integration).
• Each token is saved with name and duration information; you can cancel it whenever you want.

Step	Description
1. Open My Profile → Account Page	Click on the “My Profile” tab located in the top right corner of the Portal and then go to the “Account” page.
2. Go to API Access Tokens Section	On the “Account” page, find the API Access Tokens section. Token creation is done in this section.
3. Click Create API Access Token Button	In the API Access Tokens section, click the “Create API Access Token” button to create a new token.
4. Fill Out the Form	- Token Name: Enter a name for the token (e.g., claude-writer, ci-build). - Expiration Type: Set token duration (No expiration, 1 Week, 1 Month, Custom Date, etc.). - If you select the Custom option, you need to select a date from the calendar.
5. Create Token	When you click the “Create” button, the token is created and shown once. Copy this token immediately and store it in a secure place.
6. View List	Tokens you created are listed. - Show/Hide Button: You can temporarily show and hide the token value (stored as asterisks on screen). - Copy Button: You can copy the token to clipboard. - Revoke Button: You can cancel the token and remove its authorization.

When a token is revoked, integrations start receiving 401 errors; generate a new token and update the configuration.

Where Are Tokens Used?

API Access Token is an authentication tool used to securely access the Apinizer API.

The “API Access Tokens” tab on the profile page allows developers to generate personal access keys to authorize machine-to-machine integrations connected to their own account. These keys are specifically designed for AI assistants working via MCP (Model Context Protocol) or external automations to access Portal/Manager APIs; tokens generated on the service side come in mcp_<uuid> format and are only shown as plain text at the moment of creation.

This token allows your application or integrations to send or receive data to/from the Apinizer API over different platforms.

By integrating the token you created with platforms such as API Portal and AI tools using MCP, you can securely manage data flow between systems.

• For MCP integration, you can visit the API Portal MCP Usage documentation.

Creating Account from API Portal Interface

Anyone who wants to access the Apinizer API Portal, including Apinizer administrators, must register with the relevant API Portal and request access. Administrators will have separate credentials for Apinizer and the API Developer Portal.

Developer registrations can be manually approved by Apinizer administrators or automatically approved by configuring automatic approval settings.

Register as a Developer

All developers must register through the Apinizer API Portal. An Apinizer administrator can provide you with the correct registration URL.

For the Sign Up button to be active, the “Activate developers to create their own accounts” option must be enabled in the table from the API Developer Portal settings section. If this button is closed, the Sign Up button will not be active.

To register as a developer, go to the Apinizer API Portal and follow these steps:

Step 1

If you are not yet a member of the Apinizer API Portal, you can become a member by clicking the Sign Up button located in the top right corner.

Step 2

The relevant fields are filled in as shown in the image below and the Sign Up button is clicked.

If the “Auto Approve Account/Developers” button is not enabled, an administrator must manually review and approve the request from the API Manager section. All developers who are manually approved are notified via email when they access the API Portal. You can read the Approval Requests documentation to learn more about the manual approval process.

Step 3

To complete the registration process successfully, you will need to activate your account by clicking the confirmation link sent to your email address. When you click the link, if the confirmation process is completed successfully, the following screen will greet you.

Step 4

To complete the registration process successfully, you will need to activate your account by clicking the confirmation link sent to your email address. When you click the link, if the confirmation process is completed successfully, the following screen will greet you.

Step 5

You can log into the API Portal with your activated account information.

You can review the general settings to be used on the API Developer Portal side in detail.

Forgot My Password

If you forgot your password: Click the “Forgot your password?” option from the Developer Portal. and enter the email address associated with your API Portal account. If an account exists with the specified email address, you will receive an email asking you to change your password.