Check a requested date
Ask for Morning, Midday, Afternoon, and After hours windows with an available or unavailable result.
Website scheduling API
Connect a service website to 850 Work scheduling.
The 850 Work Scheduling API lets a connected business website check broad appointment-window availability and submit a customer request into the business's review queue. A website request stays pending until the business approves it; the API does not silently create a confirmed job or expose private customer and workspace records.
What is an API?Plain-language explanation
An API is a secure bridge that lets two systems exchange only approved information. Here, it lets a business website check broad availability and send a pending appointment request into 850 Work for the business to review. It does not open the private schedule or customer records to the public.
Website connection
What a service website can do
Submit customer details
Send the customer's name, requested date, email or phone, and optional service, time, address, notes, and source.
Create a pending request
Successful submissions return a request ID and pending status instead of promising an appointment the business has not approved.
Keep the schedule controlled
The business reviews the request in 850 Work before turning it into a customer, job, final time, duration, and crew assignment.
Integration flow
From website form to reviewed appointment request
- Enable the website connection. The signed-in owner opens Scheduling and uses the organization identifier and connection details shown by 850 Work.
- Check a date when useful. The website requests broad availability for the selected day. Availability remains advisory until approval.
- Submit only approved form fields. The request includes the organization identifier, customer name, date, and at least an email or phone number.
- Review inside 850 Work. The business can approve, decline, archive, or convert the pending request into normal customer and job records.
Public endpoints
A narrow API for availability and appointment intake
- GET /api/v1/public/scheduling/availability checks broad windows for an organization and date.
- POST /api/v1/public/scheduling/request creates a pending website appointment request.
- OpenAPI document: review the current request and response definitions at 850work.com/openapi.json.
- Implementation guide: use the field list and owner setup notes in the 850 Work API guide.
Security boundaries
Keep connection keys and account access out of public browser code
When 850 Work enables a scheduling connection key, the business must keep it on its server or protected form backend. Do not place account passwords, session tokens, payment credentials, customer exports, or admin credentials in a website request. Owner-approved OAuth access for agents is separately limited to organization identity and scheduling scopes.
Direct answers
Frequently asked questions
Does a website request automatically become a confirmed job?
No. The API creates a pending request. The business reviews it before confirming the customer, job, time, duration, or crew.
What customer information is required?
The request needs the organization identifier, customer name, requested date, and at least one contact method: email or phone.
Can a website read all customers or the private schedule?
No. The public scheduling API is limited to broad availability and new pending requests. It does not expose customer lists, documents, payments, staff records, billing, or full workspace state.
Where does the business find its setup details?
The signed-in business owner opens Scheduling in 850 Work and uses the organization identifier, endpoint, and connection example shown there.
Keep exploring
Related 850 Work pages
Try 850 Work with sample data first.
The demo does not require a credit card. Full access is managed from inside the app.