Skip to main content
The Request Tester lets you execute HTTP requests against any linked account directly from the dashboard. Use it to verify connections, test specific endpoints, and troubleshoot integration issues.
Unified API Testing: The Request Tester is the recommended way to test Documents API endpoints against specific accounts. It provides direct access to the API without requiring code or external tools.

​
Accessing the Request Tester

1

Navigate to Accounts

Go to Accounts in the StackOne dashboard.
2

Find your account

Locate the linked account you want to test.
3

Open Request Tester

Click the ellipsis menu (⋯) on the account row and select Request Tester.
You can also access the Request Tester from the account detail page by clicking the Test Request button.

​
Using the Request Tester

​
Select an Endpoint

Choose from available Documents endpoints:
CategoryExample Endpoints
DocumentsList Files, Get File, List Folders, Get Folder, List Drives, Get Drive

​
Configure Parameters

Depending on the endpoint, you can configure:
  • Path parameters – Required IDs like file_id or folder_id
  • Query parameters – Pagination, filtering, and expansion options
  • Request body – For POST/PUT/PATCH requests
ParameterDescription
page_sizeNumber of results per page (default varies by endpoint)
nextPagination cursor for fetching next page
updated_afterFilter by modification date
expandInclude related resources in response
Some endpoints support expanding related data. For example, when listing files you might expand related folder or drive information to include those details inline.See Using Expand and Include Parameters for details.

​
Execute and Inspect

Click Send Request to execute. The response panel shows:
  • Status code – HTTP status (200, 400, 404, etc.)
  • Response body – JSON data returned by the API
  • Response headers – Including rate limit information
  • Timing – Request duration

​
Troubleshooting with Request Tester

The Request Tester is particularly useful for debugging:
If an account shows an error status, use the Request Tester to execute a simple request (like listing files). The response will reveal:
  • Authentication failures (401/403)
  • Token expiration
  • Permission issues
  • Provider API errors
When expected data isn’t appearing:
  1. Test the specific endpoint directly
  2. Check if the data exists in the source system
  3. Review field mappings in the response
  4. Verify scopes/permissions in the integration configuration
To debug pagination:
  1. Make an initial request with a small page_size
  2. Copy the next cursor from the response
  3. Make a follow-up request with that cursor
  4. Verify data continuity between pages
If requests are slow:
  • Check the response timing in the panel
  • Try smaller page_size values
  • Review Request Logs for detailed timing breakdown

​
Request Tester vs AI Playground

FeatureRequest TesterAI Playground
PurposeDirect API testingNatural language exploration
Best forDebugging, verificationDiscovery, prototyping
InputStructured parametersNatural language prompts
OutputRaw API responseAI-interpreted results
Unified APIsRecommendedSupported
Provider actionsSupportedSupported
Use the Request Tester when you need precise control over parameters and want to see exact API responses. Use the AI Playground when exploring capabilities or testing complex multi-step workflows.

Accounts

Manage linked accounts

Request Logs

View detailed request history

Error Codes

Understand error responses

AI Playground

Test with natural language