How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Paradox Locations API

Manage locations including creating, retrieving, updating, deleting, and lookup by job location code

Paradox Locations API is one of 11 APIs that Paradox publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, an API reference, and 1 JSON Schema.

This API exposes 7 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 6 base URLs: https://api.paradox.ai/api/v1/public, https://api.eu1.paradox.ai/api/v1/public, https://stgapi.paradox.ai/api/v1/public, https://api.stg.eu1.paradox.ai/api/v1/public, https://testapi.paradox.ai/api/v1/public, https://dev2api.paradox.ai/api/v1/public.

7 operations 4 paths 4 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.paradox.ai
Authentication
OAuth 2.0, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Paradox Locations API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 client credentials authentication
  • bearerAuth — Bearer token obtained from the OAuth 2.0 token endpoint

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Locations 7

Manage locations including creating, retrieving, updating, deleting, and lookup by job location code

GET
/company/locations
Paradox Get locations
getLocations → 200401
POST
/location
Paradox Create location
createLocation body → 200400401
GET
/location/{id}
Paradox Get single location
getLocation 1 param → 200401404
PUT
/location/{id}
Paradox Update location
updateLocation 1 param body → 200400401404
DELETE
/location/{id}
Paradox Delete location
deleteLocation 1 param → 200401404
GET
/location/code/{job_loc_code}
Paradox Get location by job location code
getLocationByCode 1 param → 200401404
PUT
/location/code/{job_loc_code}
Paradox Update location by job location code
updateLocationByCode 1 param body → 200400401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Location (12 properties), LocationUpdate (9 properties), LocationCreate (8 properties), SuccessResponse (1 property). Each schema is shown below with its type and property counts.

SuccessResponse
object
1 property
Location
object
A physical location or job site in the Paradox platform
12 properties
LocationCreate
object
Request body for creating a new location
8 properties 1 required
LocationUpdate
object
Request body for updating an existing location
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paradox-locations-api-openapi.yml Raw ↑

Other APIs Paradox publishes across the network.

Paradox Authentication API
Paradox Candidate Attributes API
Paradox Candidates API
Paradox Company API
Paradox Location Areas API
Paradox Location Rooms API
Paradox Reporting API
Paradox Scheduling API
Paradox User Permissions API
Paradox Users API
Where this information came from

This is an independent, third-party profile of Paradox Locations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.