RESTful API returns 404 on every endpoint despite active, enabled key
Posted: Mon Aug 03, 2026 2:03 am
Build: pwfp.simprosuite.com
API endpoint(s) tested:
GET /api/1.1/companies/
GET /api/1.1/info/
GET /api/1.1/companies/0/customers/
Request details:
Base URL: https://pwfp.simprosuite.com/api/1.1
Auth: Authorization: Bearer {access_token} header
Grant Type: API Key (application shown as Enabled in System Setup → API → Applications)
Tested with two separate keys, including one freshly issued by Simpro Support (Nartarsha) on 3/08/2026, who confirmed the API is active on our build
Expected response: JSON data (list of companies / info / customers)
Actual response: HTTP 404 with Simpro's own branded "The page you are trying to access does not exist" HTML page — identical response for every endpoint tried, including the most basic ones
Steps to reproduce:
Generate an API Key application in System Setup → API → Applications, status Enabled
Send a GET request to any /api/1.1/... path on our build using Authorization: Bearer {token}
Response is always the branded 404 page, never JSON
What we've already ruled out: wrong domain (confirmed correct — response includes genuine Simpro branding/version assets), token mismatch (confirmed token matches what's shown in System Setup), domain case sensitivity (tested both cases, no change), stale/placeholder key (tested with brand new key issued directly by Simpro Support)
API endpoint(s) tested:
GET /api/1.1/companies/
GET /api/1.1/info/
GET /api/1.1/companies/0/customers/
Request details:
Base URL: https://pwfp.simprosuite.com/api/1.1
Auth: Authorization: Bearer {access_token} header
Grant Type: API Key (application shown as Enabled in System Setup → API → Applications)
Tested with two separate keys, including one freshly issued by Simpro Support (Nartarsha) on 3/08/2026, who confirmed the API is active on our build
Expected response: JSON data (list of companies / info / customers)
Actual response: HTTP 404 with Simpro's own branded "The page you are trying to access does not exist" HTML page — identical response for every endpoint tried, including the most basic ones
Steps to reproduce:
Generate an API Key application in System Setup → API → Applications, status Enabled
Send a GET request to any /api/1.1/... path on our build using Authorization: Bearer {token}
Response is always the branded 404 page, never JSON
What we've already ruled out: wrong domain (confirmed correct — response includes genuine Simpro branding/version assets), token mismatch (confirmed token matches what's shown in System Setup), domain case sensitivity (tested both cases, no change), stale/placeholder key (tested with brand new key issued directly by Simpro Support)