Login
Setup Documentation

Setting Up PestScan for PC40

A practical guide for configuring a PestScan account so it can receive and work with PC40 API events correctly.

API DocumentationPC40 Setup Guide
Jump to setup steps

Access

Admin required

Module

Permanent Monitoring

Key ID

PCO-ID header

Prerequisites

Before you begin, make sure the account and tenant are ready for permanent monitoring.

Active PestScan account with admin access
Permanent Monitoring module enabled
At least one customer and location configured

Step 1

Create a PC40 Profile
Create the permanent monitoring profile that will identify PC40 traffic.
  1. Navigate to General Settings using the cog wheel in the main navigation bar.
  2. Select Permanent Monitoring from the menu.
  3. Open the Profiles tab and click New.
  4. Set Description to something clear, such as PC40.
  5. Set Type to PC40.
  6. Click Save.
  7. Copy the resulting PCO-ID.
Note: The PCO-ID uniquely identifies your profile and must be included in the pco-id request header when sending new events.

Step 2

Configure the Customer
Enable permanent monitoring at the customer level before working with locations.
  1. Go to Equip Company -> Customers.
  2. Select the target customer.
  3. Make sure you are on the customer page, not a location page.
  4. If you see Back to customer in the top-right, click it first.
  5. Open the Settings tab.
  6. Enable Permanent Monitoring under Display on this customer's site.
  7. Click Save.

Step 3

Configure the Location
Attach the PC40 profile to the location that should receive the events.
  1. Navigate to the location that will use PC40.
  2. Open the Inspections tab.
  3. Select the Permanent Monitoring sub-tab.
  4. Set Type to the PC40 profile created in Step 1.
  5. Optionally set Provider ID to a unique identifier for this location.
  6. Click Save.
Note: The Provider ID is used as LocationId in API calls. If provided, it links traps directly to the correct location in PestScan. A GUID is a good choice, for example 550e8400-e29b-41d4-a716-446655440000.
Tip: If the Provider ID is left empty, traps that send events without a LocationId can still be assigned later through Trap Assignment.

Step 4

Assign Unlinked Traps
Use this only when events arrive without a location identifier.
  1. Navigate to General Settings.
  2. Select Permanent Monitoring.
  3. Open the Trap Assignment tab.
  4. Review the list of traps that sent events without an associated location.
  5. Choose the target Location for each trap.
  6. Click Assign.
Tip: You can also use Trap Assignment later to reassign traps to a different location if the deployment changes.

Verification

After setup, verify the configuration before starting a larger rollout.

  1. Confirm the PCO-ID is visible in the profile settings.
  2. Confirm the location has a Provider ID, or plan to use Trap Assignment.
  3. Test the API connection using the authentication endpoint and event ingestion flow.
Documentation navigation
Use this guide for PestScan-side configuration and the API documentation for authentication, headers, payloads, and endpoint behavior.
API documentationOpen /api-docs

Troubleshooting

Common setup issues and the fastest corrective action.

Issue
Solution
Cannot see Permanent Monitoring option
Make sure your account has the Permanent Monitoring module enabled.
Events not being received
Verify the Provider ID is set, or assign traps manually through Trap Assignment.
Traps not appearing in Trap Assignment
Make sure the trap has sent at least one event to the API.

Next Steps

Once the account is configured, move into API validation and trap integration work.

Review the API docs

Check endpoint details, request schemas, and required headers.

Open API documentation

Set up authentication

Use the Login endpoint first to obtain an access token and refresh token.

Configure trap event delivery

Point your traps or integration service at the PC40 event ingestion endpoint.