Send batch information
Submit agreed batch and device details through the customer API. Advance information is recorded separately from confirmation that the physical goods have arrived.
WJD OS & integrations
The system
behind
the bench.
WJD OS is our in-house repair operations platform. It connects the device, the work and the record, with a customer API for agreed integrations into your own operation.
Customer referencesRepair & approval recordsDispatch information
WJD OS / CONNECTED OPERATIONS
WJD OS
Your system.
Our repair workflow.
- 01Your references
- 02Customer API
- 03WJD OS
- 04Agreed updates
Workflow illustration, not an application screenshot or live customer data.
A record that follows the work
Your references stay
with your devices.
A batch sent for repair should not disappear into a different set of records. WJD OS keeps customer references linked to the repair workflow, so updates and decisions can be matched back to your operation.
Built into the WJD service.
WJD OS supports our repair operation. It is not advertised here as standalone software or a self-service subscription. Customer access and integrations are agreed during onboarding.
Retrieve repair information
Request customer-scoped repair records and updates, including references, status, findings and relevant quotation information in the agreed response.
Connect authorisation
Return repair approvals through the documented workflow. Keep customer decisions distinct from technical findings and the actual work carried out.
Reconcile completion & dispatch
Retrieve available completion, dispatch and tracking fields. A repaired device and a dispatched device are separate outcomes, not interchangeable labels.
Follow the information
One device.
A connected record.
Explore the information handovers. These are illustrative records, not a WJD OS screenshot or a live API response.
ILLUSTRATIVE RECORD / NO LIVE DATA
Information first. Physical receipt separately.
Advance device information can enter the workflow before the shipment arrives. The record should not say received until physical receipt is confirmed.
- Customer reference
- TEST-PARTNER-001
- Device reference
- TEST-DEVICE-001
- Batch information
- Pre-advice received
- Physical receipt
- Awaiting confirmation
ILLUSTRATIVE RECORD / NO LIVE DATA
Keep the finding separate from the next decision.
Customer-facing repair information can distinguish assessment, quotation and work awaiting authorisation. Field availability depends on the agreed workflow.
- Customer reference
- TEST-PARTNER-001
- Device reference
- TEST-DEVICE-001
- Illustrative finding
- Outer glass damage
- Next decision
- Repair authorisation
ILLUSTRATIVE RECORD / NO LIVE DATA
Make the authorised work explicit.
An approval belongs to the relevant repair record. The customer decision and technical findings remain separate parts of the workflow.
- Customer reference
- TEST-PARTNER-001
- Device reference
- TEST-DEVICE-001
- Illustrative instruction
- Proceed with quoted work
- Next operational step
- Approved repair
ILLUSTRATIVE RECORD / NO LIVE DATA
Repair complete is not the same as dispatched.
Completion, return readiness and confirmed dispatch are distinct. Tracking and dispatch information can be returned when available in the agreed workflow.
- Customer reference
- TEST-PARTNER-001
- Device reference
- TEST-DEVICE-001
- Illustrative repair outcome
- Final checks complete
- Dispatch evidence
- Not yet confirmed
A practical integration process
Start with the workflow.
Then connect the systems.
The integration should fit the operating agreement. We define the handovers with your team before enabling access.
- 01
Scope
Identify the devices, references, customer system, required fields and approval process.
- 02
Map
Agree how your records match WJD batches, repair records and customer-facing statuses.
- 03
Test
Use agreed test records to check submissions, updates, approvals and exception handling.
- 04
Enable
Activate the agreed customer-scoped access and confirm operational ownership.
- 05
Review
Check the information exchange and exception process as the programme develops.
For your technical team
An API conversation
with clear boundaries.
Bring your technical team into the conversation. We will define the supported fields, access and handovers together.
Customer-scoped access
Credentials are scoped to a customer. The documented access model separates one customer’s records from another’s.
Repeatable submissions
Documented write requests use idempotency keys, helping prevent an identical retry from creating a second submission.
Incremental updates
The customer API documents pagination and updated-since filtering so your system can retrieve relevant changes.
Polling in version one
Your system requests updates at an agreed frequency. Webhooks are not part of the current v1 offer. Access, limits and supported fields are confirmed at onboarding.
This page summarises documented capabilities. It is not an uptime commitment or a guarantee of compatibility with every third-party platform. Technical documentation is shared as part of the integration discussion.
Useful for a claim. Useful for a whole programme.
Apply the same reference-led approach to an agreed insurance repair workflow or the repair stages behind a trade-in operation. The service scope comes first.
Before we get started
A few useful
answers.
Have a specific process or technical requirement? Talk it through with the team.
Talk to WJDCan our own system receive repair updates?
Yes, through an agreed customer API integration. Version one uses polling: your system requests the available updates. Field mapping and the refresh frequency are agreed during onboarding.
Are instant webhooks available?
Webhooks are not included in the current v1 offering. We will discuss your requirements without presenting roadmap features as already available.
Does an API submission confirm the devices have arrived?
No. Advance batch information and physical receipt are different events. Receipt is confirmed in the operating workflow when goods arrive.
Can we start without an API integration?
Yes. Discuss the intake files, reporting and approval handovers your team needs. An integration is not a prerequisite for discussing a repair programme.
Can we buy WJD OS as standalone software?
This page presents WJD OS as part of WJD’s repair service. It does not offer a standalone licence or a self-service subscription.
Show us how
your systems work.
Tell us which system you use, the records you need to exchange and where the manual handovers are. We will scope the integration with you.