Reference · built on requestConnectorFleet & telematics

Tookan

Pickup, delivery, appointment, and field workforce tasks, agents, teams, and customers from Tookan by Jungleworks.

Request accessPricing ↗

About

Tookan is a delivery management product from Jungleworks. Dispatchers create tasks, group agents into teams, and track each task through a numbered job_status from Unassigned to Successful, Failed, or Cancelled. Every call is a JSON POST to https://api.tookanapp.com/v2 with an api_key in the body, and Tookan can POST each status change to a webhook URL you set in the dashboard. Tasks carry the customer's phone and address, the agent's signature and photos, custom fields from your templates, and a task_history of every state change with the agent's coordinates.

An operator on Fibric reads those webhooks and task lists, spots the task nobody accepted or the agent running late, and proposes the reassignment, the new time, or the customer message for your approval.

This is a reference listing. It documents what Fibric would read from Tookan and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Tasks by job_type (0 pickup, 1 delivery, 2 appointment, 3 FOS) through POST /get_all_tasks, filtered by status, agent, team, customer, or order_id
  • job_status values: Assigned 0, Started 1, Successful 2, Failed 3, Arrived 4, Unassigned 6, Accepted 7, Decline 8, Cancel 9, Deleted 10
  • Task details through POST /get_job_details with task_history, job report, and custom_fields, up to 100 job ids per call
  • Webhook POSTs on every status update carrying job_id, job_status, fleet_id, customer_phone, sign_image, custom_fields, and optional task_history
  • Agents through POST /get_all_fleets with status 0 available, 1 offline, or 2 busy, plus duty logs, activity timeline, and last location
  • Routes after optimization for a date through POST /get_route_details_for_date, and geofence regions through POST /view_regions
  • Teams, managers, merchants, and customers looked up by phone or name through POST /find_customer_with_phone and POST /view_customer_profile

Proposed actions

  • Target capability: propose a pickup, delivery, or appointment task through POST /create_task with order_id, address, datetime, team_id, and custom fields
  • Target capability: propose assigning or reassigning a task to an agent through POST /assign_fleet_to_task or POST /assign_task
  • Target capability: propose moving one or more tasks to a new start_time and end_time through POST /change_job_date
  • Target capability: propose cancelling a task through POST /cancel_task with job_status 9, or forcing a status through POST /update_task_status
  • Target capability: propose a push message to agents through POST /send_notification or a dispatch push through POST /ready_to_dispatch

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reassign the task nobody accepted

    Watch webhooks for job_status 6 or 8 past the pickup time. Pull available agents from POST /get_all_fleets and propose the assignment through POST /assign_fleet_to_task for the dispatcher to approve.

    With Field Dispatch, Route Overflow

  • Warn the customer before the agent is late

    Compare the agent's last location and job_pickup_datetime for tasks still in Started. Propose the customer message and, if needed, a new time through POST /change_job_date.

    With ETA Notice, Missed Stop

  • Settle a delivery claim from the task record

    Fetch the task with task_history and the job report, attach sign_image and the arrival coordinates, and draft the reply for approval.

    With Delivery Proof, Delivery Dispute

Requirements

  • A Tookan account with an API key from Settings > API Keys; the key is mandatory on every request
  • team_id and fleet_id values from the dashboard for assignment and auto_assignment calls
  • A timezone value in minutes from UTC on task creation and timeline calls
  • Webhook URLs configured under the notifications section of the dashboard, with ?task_history=1 if you want history in the payload
  • Custom field templates defined under Templates before sending meta_data or pickup_meta_data
Authentication
An api_key generated under Settings > API Keys in the Tookan account and sent in the body of every request; webhooks are checked against a tookan_shared_secret you set through POST /set_tookan_shared_secret_key.

Limits

  • POST /get_all_tasks accepts a start_date and end_date at most 31 days apart, so history loads are paged by month
  • POST /send_notification caps pushes per agent at 50 a day, 150 a week, and 300 a month; the same message cannot repeat in a day
  • Every endpoint is a POST with the api_key in the body; the published API blueprint does not state request rate limits
  • Webhook requests are checked by comparing the tookan_shared_secret field, not by a signature header

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Tookan ↗

Questions and answers

How does Tookan tell my system that a task changed status?
Tookan POSTs the task to a webhook URL you set in the dashboard's notifications section on each status update. The payload carries job_id, job_status, job_state, fleet_id, customer fields, custom_fields, and task_history when you append ?task_history=1. Compare tookan_shared_secret to confirm the sender.
Which task statuses does Tookan use?
job_status is numeric: Assigned 0, Started 1, Successful 2, Failed 3, InProgress/Arrived 4, Unassigned 6, Accepted/Acknowledged 7, Decline 8, Cancel 9, Deleted 10. POST /update_task_status forces a status; POST /cancel_task sets 9.
How far back can I list tasks?
POST /get_all_tasks takes a job_type plus start_date and end_date inside a 31-day span. Set is_pagination to 1 and page with requested_page. For specific tasks, POST /get_job_details accepts up to 100 job ids in one call.
Ask about Tookan

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Tookan through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy