Reference Manual (API Version 2.0)

Account management

O*NET Web Services is designed for use by product developers and researchers, including those who work in large teams. This page explains how accounts, organizations, and projects are related in O*NET Web Services, and how to manage your Web Services access across multiple team members or clients.

Important concepts

Accounts are used to log in to the O*NET Web Services website.

• An account is associated with a single email address.
• Each person on your team who needs to manage API keys or other setup steps should have their own account.
• Each account may be connected to any number of organizations.

Organizations represent your employer, school, or client.

• Organizations may be company-wide, or specific to a single department or class.
• Each registered organization is managed by a team of one or more account holders.

Projects represent a specific app, website, or research project.

• Each project belongs to a single organization.
• An organization may have several projects.

API keys are credentials used to access the O*NET Web Services API.

• Each API key belongs to a single project.
• A project may have multiple API keys, but generally only one is used at a time.

Signing up for Web Services

If you’re new to O*NET Web Services, the Sign Up page will guide you through the following steps:

1. Create an account tied to your email address.
   1. Verify your email with a one-time code, and set a password.
   2. Provide required information including a phone number. We never sell, trade, or share your personal information; we only use it to contact you directly if there is a problem with your account or the projects you manage.
2. Register the organization with which you’re affiliated.
   1. Your registered “organization” will cover a single development team, so in a large company or institution, you may register on behalf of your department or group instead of the entire company. If so, include the department or group in the organization’s name.
   2. If you are a technical contractor building a product for a client, register on behalf of the client rather than your own company.
   Personal use of O*NET Web Services is not supported. If you are not working, conducting research, or affiliated with an organization in either a paid or unpaid role, please use our websites including O*NET OnLine and My Next Move, or our downloadable O*NET Database to explore our data.
3. Register a project for the organization.
   1. Summarize how you intend to use O*NET Web Services in a specific app, website, or other project.
   2. If you plan to use O*NET Web Services in several ways, focus on one here; you can add more projects later.
4. (optional) Add team members who will manage your organization or projects.
   1. Team members will be able to view your organization and project information and credentials through the O*NET Web Services website.
   2. Team members will be able to perform management tasks such as registering new projects or generating new API keys.
   3. You do not need to add every developer who works with the API.
   4. You can add or remove team members later.
5. Agree to the terms of service.
   1. O*NET Web Services are free for commercial and non-commercial use, but you must acknowledge their use in your projects.
   2. You must respect any licensing restrictions for the data you retrieve.

O*NET Web Services staff reviews and approves all organization registrations. Please make sure your information is complete and accurate, or your submission may be rejected. The approval process may take up to 3 business days.

Managing your projects

Once your organization is approved, you will be notified by email, and it will be available to view and manage at My Account. You will see your organization and project listed, along with an API key you can use to call the O*NET Web Services API. You now have everything you need to get started on your project!

You can also:

• Update your account information, including your email address and password.
• Update your organization’s name or URL.
• Add or remove team members to your organization. To manage projects, a team member will need to create their own personal account, but once they do, your organization will appear in their own “My Account” page.
• Add or remove API keys for your project. If you decide to rotate your key for security purposes, you can generate a new key, update your application to use the new key, and then revoke the old key.
• Add new projects to your organization. We recommend you use a separate project for each app or website using O*NET Web Services, so that any technical problems with one project or API key will not affect your other usage. Additional projects for an already-approved organization are activated immediately without a manual review.

Other use cases

If you were added to an organization’s team but do not have an account, visit the Sign Up page to create your account. You will not need to register an organization of your own.

If you’re a contractor implementing O*NET Web Services for multiple clients, or if you need separate developer teams for different projects, you can register a new organization from the Sign Up page. The process is identical to the initial signup, although you will not need to create a new personal account. You can view and manage each of your organizations in My Account, whether you submitted the registration or you were invited to the team by an administrator.

If you have a legacy username and password you used with Version 1.9 of O*NET Web Services, visit the Log In with Username page to connect that legacy organization to your personal account. If you do not have a personal account yet, that page will guide you through the process.

In this section

• Getting started
  • Overview
  • Migrating from version 1.9
  • Account management
  • Version information