Postman Collection Setup
Get started quickly with the Docstron API using our ready-to-use Postman collection. All endpoints are pre-configured with examples and you can start testing immediately.
Download Collection
Section titled “Download Collection”Download the Postman collection and environment files:
- Download Postman Collection - All API endpoints
- Download Environment - Environment variables
What’s Included
Section titled “What’s Included”The Postman collection includes all Docstron API endpoints:
Applications
Section titled “Applications”- Get All Applications
- Get Single Application
Templates
Section titled “Templates”- Create Template
- Get Template
- Get All Templates
- Update Template
- Delete Template
Documents
Section titled “Documents”- Generate Document (with template)
- Get Document
- Get All Document
- Update Document
- Delete Document
- Download Document
Usages
Section titled “Usages”- Get Usage
Setting Up Postman
Section titled “Setting Up Postman”Step 1: Install Postman
Section titled “Step 1: Install Postman”If you don’t have Postman installed:
- Visit postman.com/downloads
- Download and install Postman for your operating system
- Create a free Postman account (optional but recommended)
Step 2: Import Collection
Section titled “Step 2: Import Collection”- Open Postman
- Click the “Import” button in the top-left corner
- Click “Choose Files” or drag and drop the
Docstron-API-Collection.jsonfile - Click “Import” to add the collection to your workspace

Alternative method:
- Click “Import” → “Link” tab
- Paste the collection URL (if provided)
- Click “Continue” → “Import”
Step 3: Import Environment
Section titled “Step 3: Import Environment”- Click the “Import” button again
- Select the
Docstron-Environment.jsonfile - Click “Import”
- The environment will appear in the top-right environment dropdown

Step 4: Configure Environment Variables
Section titled “Step 4: Configure Environment Variables”- Click the environment dropdown in the top-right corner
- Select “Docstron Environment”
- Click the eye icon (👁️) next to the environment name
- Click “Edit” to update variables
Required variables to update:
| Variable | Description | Example |
|---|---|---|
BASE_URL | API base URL | https://api.docstron.com/v1 |
API_KEY | Your API key | dstr_g9miFIPt67EGiW7tj... |
To get your API key:
- Log in to docstron.com
- Go to API Keys
- Generate a new API key if you don’t have one
- Copy the key and paste it into the
API_KEYvariable
Step 5: Save Environment
Section titled “Step 5: Save Environment”- After updating all variables, click “Save”
- Ensure the environment is selected in the top-right dropdown
Using the Collection
Section titled “Using the Collection”Making Your First Request
Section titled “Making Your First Request”- In the left sidebar, expand the “Docstron API” collection
- Navigate to “Applications” → “Get All Applications”
- Click on the request to open it
- Click the blue “Send” button
- View the response in the bottom panel

Understanding Requests
Section titled “Understanding Requests”Each request in the collection includes:
- Pre-configured URL - Uses
{{BASE_URL}}variable - Authentication - Automatically includes
{{API_KEY}} - Request Body - Example data for POST/PATCH requests
- Example Responses - Sample successful responses
Environment Variables Explained
Section titled “Environment Variables Explained”Base Variables
Section titled “Base Variables”These variables are used across all requests:
URL = https://api.docstron.com/v1API_KEY = YOUR_API_KEY_HEREPath Parameters
Section titled “Path Parameters”When you see a colon (:) in the URL path, Postman treats it as a path parameter:
{{URL}}/applications/:application_idPath parameters appear in the Params tab below the URL bar. You can set their values in two ways:
Option 1: Directly in Params tab
- The
:application_idwill appear as an editable field - Enter the value directly (e.g.,
app_123456)
Option 2: Using environment variables
- In the Params tab, use
{{application_id}}as the value - Set
application_idin your environment variables
Using Variables in Requests
Section titled “Using Variables in Requests”Variables are referenced using colon :application_id
In URL with path parameters:
{{BASE_URL}}/applications/:application_idThen in Params tab: application_id = app-58756d65..
In Headers:
Authorization: Bearer {{API_KEY}}Testing Workflow
Section titled “Testing Workflow”Follow this workflow to test the complete API:
1. Setup (One-time)
Section titled “1. Setup (One-time)”✓ Import collection✓ Import environment✓ Add your API key✓ Create an application (via dashboard)✓ Copy the application_id2. Template Creation
Section titled “2. Template Creation”1. Create Template → Save template_id2. Get Template → Verify template details3. Update Template (optional) → Test modifications3. Document Generation
Section titled “3. Document Generation”1. Generate Document → Save document_id2. Get Document → Verify document details3. Update Document (optional) → Modify attributes4. Delete Document (optional) → Clean up4. Cleanup (Optional)
Section titled “4. Cleanup (Optional)”1. Delete Template → Remove test templateTips and Tricks
Section titled “Tips and Tricks”Quick Testing
Section titled “Quick Testing”- Use Collection Runner - Run all requests sequentially
- Duplicate Requests - Test different scenarios
- Save Responses - Use examples for documentation
Debugging
Section titled “Debugging”- Console Tab - View variable values and logs
- Response Tab - Check status codes and response data
- Headers Tab - Verify authentication headers
Best Practices
Section titled “Best Practices”✅ Use environments - Separate dev, staging, production
✅ Name requests clearly - Easy to find specific endpoints
✅ Add descriptions - Document what each request does
✅ Save examples - Different success and error responses
✅ Use tests - Automate variable updates
Common Issues
Section titled “Common Issues”❌ “Unauthorized” error
- Check your API key in environment variables
- Ensure the environment is selected in the top-right
- Verify the API key is still valid at docstron.com/api-keys
❌ “Application not found” error
- Update the
application_idin environment variables - Ensure the application exists in your dashboard
- Check that the application is active
❌ Variables not working (showing {{variable_name}})
- Select the correct environment from the top-right dropdown
- Check variable names match exactly (case-sensitive)
- Save the environment after making changes
Need Help?
Section titled “Need Help?”If you encounter issues with the Postman collection:
- 📧 Email: support@docstron.com
- 💬 Live Chat: Available in your dashboard
- 📚 Postman Docs: learning.postman.com
- 🐛 Report Issues: Let us know if you find any errors in the collection