Adobe Acrobat Sign Developer Edition: Account Setup for Testing on OttoKit

Overview

The Acrobat Sign Developer Edition is a free account provided by Adobe specifically for developers who want to test and build integrations with the Acrobat Sign REST APIs without needing a paid Business or Enterprise plan. It provides access to the full set of API features in a sandboxed environment.

Who needs this

You need a Developer Edition account if you fall into any of these situations:

• You do not have an existing Acrobat Sign Business or Enterprise plan
• You want a separate sandbox account for testing, isolated from your production data
• You want to test API functionality without affecting live agreements

If you already have a Business or Enterprise plan and just want to use the API on that account, you do not need a Developer Edition. You can generate Client ID and Secret directly inside your existing account. Refer to this second guide for that flow.

Step 1: Sign up for the Developer Edition

1. Open the developer account signup form: https://www.adobe.com/go/acrobatsigndevaccount
2. Fill in the required details
3. Submit the form.

Adobe will send a confirmation email. The account is typically activated within a few minutes to a few hours, though it can occasionally take up to one business day.

Step 2: Verify your email and complete account creation

1. Open the confirmation email from Adobe.
2. Click the activation link.
3. If prompted, create an Adobe ID or sign in with an existing one. Adobe IDs are separate from Acrobat Sign accounts, and the same Adobe ID can be linked to multiple Sign accounts.
4. Set a password and complete your profile.

Step 3: First login

1. Go to the login page: https://secure.adobesign.com/public/login
2. Sign in with your Adobe ID credentials.
3. After login, check the URL in your browser. It will redirect you to a regional shard, for example:
   • secure.na1.adobesign.com for North America
   • secure.na2.adobesign.com, secure.na3.adobesign.com, secure.na4.adobesign.com are alternate North America shards
   • secure.eu1.adobesign.com or secure.eu2.adobesign.com for Europe
   • secure.in1.adobesign.com for India
   • secure.jp1.adobesign.com for Japan
   • secure.au1.adobesign.com for Australia

Note your shard. You will need it for every API call later, since each Acrobat Sign account is tied to a specific regional shard and the API base URL changes accordingly.

Step 4: Verify API access is enabled

1. After logging in, look at the top navigation menu.
2. You should see an “API” link in the top menu, or under Account in the sidebar you should see “Acrobat Sign API”.
3. Click into it and confirm you can see “API Applications” and “API Information” sections.

If you do not see these sections, the Developer Edition may still be provisioning. Wait a few hours and check again, or contact Adobe support through the Help link.

Step 5: Create your first test application

1. Navigate to: Account > Acrobat Sign API > API Applications
2. Click the “+” icon in the top right.
3. Fill in:
   • Name: Test-App (or any internal identifier)
   • Display Name: Test Application (this appears on the OAuth consent screen)
   • Domain: select CUSTOMER. This restricts the app to your own developer account, which is what you want for testing.
4. Click Save.

Step 6: Get the Client ID and Client Secret

1. Single-click your newly created application in the list. An action menu appears at the top.
2. Click “View/Edit”.
3. A dialog will display:
   • Application ID (this is your Client ID)
   • Client Secret
4. Copy both values and store them securely.

Step 7: Configure OAuth settings

1. With the app still selected, click “Configure OAuth for Application”.
2. Enter your Redirect URI in the field provided. For testing, you can use:
   • https://api.ottokit.com/adobe_acrobat_sign/connection
   • Multiple URIs can be added as a comma-separated list
3. Select all the scopes
4. For each scope, set the modifier to account (since you are an admin of your own developer account).
5. Click Save.

Now your OAuth app has been configured for OttoKit using your Developer Account