# Developer access Most Handy APIs require credentials issued through the user portal. Start by creating an account and obtaining credentials for the API your integration will use. Hosting API uploads and downloads are available without an account. ## Create your developer account 1. Open the [user portal](https://user.handyfeeling.com). 2. Sign up for an account, then sign in. 3. Issue an Application ID (`application_id`) or Authentication Key (`authentication_key`) for the API you want to use. The API's guide explains which credential each operation accepts. The same portal manages developer access across the APIs. Credentials remain API-specific: an Application ID issued for one API does not automatically authorize another. If your account cannot issue credentials for an API, contact platform support about access to that API. ## Choose the right credential | Credential | Where it belongs | Purpose | | --- | --- | --- | | Application ID (`application_id`) | Browser, mobile app, or server, where the API accepts it | Identifies your integration. It may be visible in client code; requests still belong to your account. | | Authentication Key (`authentication_key`) | Your server | Authorizes the operations that accept this secret, such as client-token issuance or account administration. Keep it out of browser and mobile client code. | | Client token | Client application, where supported | Provides temporary API access with an expiry and any configured restrictions. Your server obtains it using its Authentication Key. | Currently, Handy REST API v3 supports client-token issuance. Channel API v1 and Stream API v0 use their documented creation credentials and resource keys; do not substitute a Handy REST token for them. The account access token used to manage your portal account is separate from an API client token. Always use the credential, header or query parameter specified by the selected endpoint. ## Continue with your API | API | How to begin | | --- | --- | | [Handy REST API v3](https://links.handyfeeling.com/docs-handy-rest-api-v3-auth) | Use an Application ID for initial device requests, or have your server issue a client token. Supply a device connection key to address the device. | | [Channel API v1](https://links.handyfeeling.com/docs-channel-api-v1#keep-the-identifiers-and-credentials-distinct) | Use a creation credential to create a channel. Use the returned channel and subscriber keys for their respective operations. | | [Stream API v0](https://links.handyfeeling.com/docs-stream-api-v0#credentials-and-references) | Create a stream using an Application ID issued for Stream. Use its returned data and editor keys for resource operations. | | [Hosting API v2](https://links.handyfeeling.com/docs-hosting-api-v2) | Upload or download a script without an Application ID, Authentication Key, or client token. | A device connection key identifies the device. Channel and Stream resource keys authorize specific resources. Keep these values separate from your portal-issued credentials, and follow the relevant API guide when an integration uses several APIs.