Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Creating Tasks and Accepting Reservations: Accept a Reservation using Assignment Callback Instructions

Remember when we created a Task and accepted it using the Reservations subresource of the REST API? I do. And it was grand.

This time, we'll create another Task, again using the REST API, but we will have our server accept the Reservation as soon as it is notified, via a synchronous HTTP response.

Before we create the next Task, once again make sure that our Worker Alice is in a non-available Activity state.

Repeat the commands from step 2 to create another Task that only Alice is eligible to handle. Here's our PHP file from earlier:


        and the curl command:

        curl{WorkspaceSid}/Tasks \
        --data-urlencode Attributes='{"selected_language": "es"}' \
        -d WorkflowSid={WorkflowSid} \
        -u {AccountSid}:{AuthToken}

        This time, before bringing Alice online, we need to make changes to our assignment.php file. Open it and modify the existing code to reflect the following:


        $assignment_instruction = [
          'instruction' => 'accept'
        header('Content-Type: application/json');
        echo json_encode($assignment_instruction);

        Instead of returning an empty JSON document as before, we've included an 'assignment instruction' in our response. The 'accept' assignment instruction tells TaskRouter to automatically accept the Reservation and assign the Task to the Worker it has been reserved for.

        To kick this process off, we need to transition Alice to an available Activity. With your Workspace open in the TaskRouter web portal, click 'Workers' then click to edit Alice and set her Activity to 'Idle'.

        Now, click 'Tasks' in the main navigation and you should see that the Task has an Assignment Status of 'assigned':

        What actually happened is that Alice was reserved for a very short period of time. TaskRouter made a request to your web server at the Assignment Callback URL, and your server told TaskRouter to accept the Reservation. At that point, Alice's Activity transitioned to the 'Assignment Activity' of the TaskQueue that assigned the Task, as it did in the previous step.

        And that's that. We created another Task using the REST API, accepted it via an assignment instruction at our Workflow's Assignment Callback URL and saw that this immediately accepted the Reservation for our Worker.

        Onward! Next we learn about shortcuts to create Tasks originating from Twilio phone calls.

        Part 3: Create Tasks from Phone Calls using TwiML »

        Rate this page:

        Need some help?

        We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.