Developers access your APIs through apps. When the developer registers an app, they receive a single API key that allows them to access all of the API products associated with the app. However, developers must be registered before they can register an app.

By a back-end administrator using the Edge management UI, described below.

In the Edge management UI, select Publish > Developers to open the Developers page. You can see the apps they've created and the keys assigned to the developer. From this page, you can also manage the developer's information or delete them from your org.

If you use the Developer Services portal, Apigee recommends that you log in to the portal as a portal administrator to manually create, edit, and delete developers on the portal, not in the Edge UI. When you add a developer through the administrator interface on the portal, you can set the developer's password for the portal and trigger an automated email message sent to the developer. Also, any changes made to the developer's account on the portal are automatically sent to Edge. When adding or modifying a developer through Edge, no email is sent to the developer and you cannot set the password for the developer on the portal. Therefore, the developer must reset their password on the portal before they can log in to the portal. For more information, see Add and manage user accounts.

Adding a developer manually using the Edge management UI

If you use the Developer Services portal, Apigee recommends that you create, edit, and delete developers on the portal itself, not in the Edge management UI. For more information, see Add and manage user accounts.

Enter the developer's email. This the email address you use when sending keys and notifications to this developer.

Add any custom attributes for the developer. For each custom attribute:

Click (+) Add Custom Attribute.

Enter the attribute name and value.

Select Save.

If you are using the Developer Services portal, synchronize the portal with the changes to Edge as described below. When the new developer first logs in to the portal, they must use the password recovery process on the portal to set their portal password.

Editing a developer using the Edge management UI

If you use the Developer Services portal, Apigee recommends that you create, edit, and delete developers on the portal itself, not in the Edge management UI. For more information, see Add and manage user accounts.

Deleting a developer using the Edge management UI

If you use the Developer Services portal, Apigee recommends that you create, edit, and delete developers on the portal itself, not in the Edge management UI. For more information, see Add and manage user accounts.

Synchronizing the portal with developers modified using the Edge UI

If you are using a Developer Services portal to publish your APIs, changes made to developers through the Edge UI are not pushed down to the portal. Therefore, you must log in to the portal as a portal administrator and synchronize the portal with Edge for those changes to appear on the portal.

If you use the Developer Services portal, Apigee recommends that you create, edit, and delete developers on the portal itself, not in the Edge UI. For more information, see Add and manage user accounts.

To synchronize the portal with a developer added on Edge:

Log in to your portal as a user with admin or content creation privileges.

Select People in the Drupal administration menu.

Select the Dev Portal Developer Sync button at the top of the page to pull down any developers added on Edge.

Grouping developers into companies

A company is a collection of developers managed as a single entity. A company can be any grouping that is appropriate to your organization such as business unit, product line, or division. Grouping developers into companies is useful when your need to have multiple developers associated under a single corporate entity. For example, you may need to set up different companies for billing purpose. However, developers in your organization don't need to be associated with a company. Note that a developer is always a single entity, uniquely identified by the email element. If a developer is part of a company you'll see the Company name on the Developers page.