Purolator · Authentication Profile

Purolator Authentication

Authentication

Purolator secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyShippingLogisticsCouriersFreight
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
basicAuth http
scheme: basic
AWSv4Auth apiKey
· in: header (Authorization)

Source

Authentication Profile

purolator-authentication.yml Raw ↑
generated: '2026-10-13'
method: derived
source: openapi/purolator-close-manifest-openapi.yml, openapi/purolator-create-void-shipment-openapi.yml,
  openapi/purolator-estimate-openapi.yml, openapi/purolator-get-documents-openapi.yml, openapi/purolator-get-summary-manifest-openapi.yml,
  openapi/purolator-locator-openapi.yml, openapi/purolator-pickup-openapi.yml, openapi/purolator-token-openapi.yml,
  openapi/purolator-tracking-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: 'For secure access, this API uses Bearer Authentication (also known as token
    authentication). You must send a Bearer token in the Authorization header when making requests
    to protected endpoints. The token should be prefixed with the word "Bearer" followed by
    a space. Example: "Authorization: Bearer <YourTokenHere>".'
  sources:
  - openapi/purolator-close-manifest-openapi.yml
  - openapi/purolator-create-void-shipment-openapi.yml
  - openapi/purolator-estimate-openapi.yml
  - openapi/purolator-get-documents-openapi.yml
  - openapi/purolator-get-summary-manifest-openapi.yml
  - openapi/purolator-locator-openapi.yml
  - openapi/purolator-pickup-openapi.yml
  - openapi/purolator-tracking-openapi.yml
- name: basicAuth
  type: http
  scheme: basic
  description: |-
    This API uses HTTP Basic Authentication to obtain a Bearer token. Provide your `client_id` as
    the username and `client_secret` as the password, Base64-encoded in the `Authorization` header.
    Example: "Authorization: Basic <base64(client_id:client_secret)>"
  sources:
  - openapi/purolator-token-openapi.yml
- name: AWSv4Auth
  type: apiKey
  in: header
  parameter: Authorization
  description: "For authenticating requests using AWS Signature Version 4. The value of this\
    \ header must be \nformed according to AWS Signature Version 4 specifications. This includes\
    \ the algorithm \nidentifier (AWS4-HMAC-SHA256), followed by credential scope, a list of\
    \ signed headers, and \nthe signature. Refer to AWS documentation for detailed instructions\
    \ on forming this header."
  sources:
  - openapi/purolator-token-openapi.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/purolator-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.