Harborline LogisticsRollout deal room with RelayWorks
More
Theme
Ask a question
Evan BrooksService Operations Manager, Harborline
Mutual plan 3 of 9Executive decision Oct 9

Security and IT

How Harborline IT connects identity and the dispatch reference, from sandbox to production.

Integration guide, updated Sep 24, 2026
Engineers integrating an API at their desks

Environments

How Harborline's IT team connects the dispatch system to RelayWorks for the rollout, from sandbox keys to production. Prepared by Omar Lewis, who supports the integration through Wave 1.

Sandbox base URL
https://sandbox.relayworks.example/v1
Production base URL
https://api.relayworks.example/v1
Auth method
OAuth 2.0 client credentials, 1 hour tokens
Rate limit
300 requests per minute
Integration support
Omar Lewis, through Wave 1 go-live
Target
Production keys before Wave 1, Nov 16

Get connected

  1. Sandbox app createdClient ID issued Sep 22
  2. SSO and SCIM confirmedHarborline IT, due Sep 30
  3. Dispatch reference lookupRead only, in sandbox
  4. Webhooks and go-live checkBefore Nov 16

Step 1: Authenticate

Exchange the client ID and secret for an access token at POST /oauth/token. Cache the token and refresh it before it expires rather than requesting one per call.

Step 2: Attach a dispatch reference to a handoff

Call POST /handoffs with the account, region, owner and the dispatch job reference. RelayWorks stores the reference only. It never writes back to dispatch.

Live from the Dashboards app: pilot scenario tests by roundOpen the full report

Core endpoints

MethodEndpointPurposeScope
POST/oauth/tokenExchange credentials for an access tokennone
GET/handoffsList handoffs, filter by region, owner or statushandoffs:read
POST/handoffsCreate a handoff with a dispatch job referencehandoffs:write
PATCH/handoffs/{id}Change owner or waiting reasonhandoffs:write
POST/webhooksRegister a webhook endpointwebhooks:write
GET/teamsRead teams synced from SCIMteams:read

Webhook flow for handoff updates

  • handoff.created when the service desk hands work to a region.
  • handoff.acknowledged when the receiving owner accepts it.
  • handoff.owner_changed on region transfers and the after hours duty manager fallback.

Webhooks retry for 24 hours with backoff. Verify the signature header on every call.

Live from the Dashboards app: acknowledgment times in the pilotOpen the full report

Common error codes

CodeMeaningWhat to do
401Token expired or invalidRefresh the token, then retry once
403Scope missing for this callAsk Omar to add the scope to your client
409Handoff already has an ownerUse PATCH to transfer ownership
429Rate limit reachedBack off and retry after the stated delay

Go-live checklist

  • Sandbox client createddone
  • Token refresh testeddone
  • SCIM groups mapped to regional teamsopen
  • Webhook signature verifiedopen
  • Dispatch reference lookup tested on 20 real jobsopen
  • Production keys issued after technical reviewopen
Live from the Dashboards appOpen the full report

Next steps

  • Harborline IT confirms the identity provider and SCIM groups by Sep 30.
  • Omar schedules a 45 minute sandbox session for the week of Oct 5.
  • Production keys are issued after signature, before Nov 16.

The live page in FuseBase

This document as a FuseBase page, read-only from the RelayWorks workspace. Changes made there appear here.
Open the page