Integration of functionality of a fulfillment service provider into third-party application
Integrating a fulfillment service provider into a third-party application via an Application Programming Interface (API) is described. In an example, a computing device associated with a fulfillment service provider can determine, based at least in part on an indication of an interaction between a user and a third-party application, that the fulfillment service provider has been initialized. In one example, functionality associated with the fulfillment service provider can be accessible to the third-party application via an API. In at least one example, the computing device can generate, based at least in part on the interaction with the third-party application and while the fulfillment service provider is initialized, a recommendation of at least one of a service, a merchant, or an item associated with the fulfillment service provider. The computing device can cause the recommendation to be presented via at least one of the third-party application or the fulfillment service provider.
1. A computer-implemented method comprising:
generating, via a third party application, an interface of a fulfillment service provider using an application programming interface (API), wherein the interface enables a user to access fulfillment functionality from the fulfillment service provider using the third party application without leaving the third party application;
receiving, via the interface associated with the fulfillment service provider, a request from the third-party application to access the fulfillment functionality from the fulfillment service provider, the third party application being associated with a third-party service provider;
detecting that the fulfillment service provider has been initialized based, at least in part, on indication of an interaction between the user and the third-party application;
determining context information associated with the interaction, the context information indicating a first event of the third-party service provider;
determining event information pertaining to the first event, the event information including one or more of: a first date, a first time, a first location, or a route between two locations;
predicting information pertaining to the first event based, at least in part, on the event information;
generating, using the predicted information, a recommendation of a second event pertaining to at least one of: a service available via the fulfillment service provider, a merchant available via the fulfillment service provider, or an item available via the fulfillment service provider; and
causing the recommendation to be presented via the third-party application through the generated interface.
2. The computer-implemented method of claim 1 , wherein:
the interface is accessible to a plurality of third-party applications including the third-party application;
the request is an authentication request; and
the computer-implemented method further comprises associating the fulfillment service provider with the third-party application based at least in part on authenticating the third-party application.
3. The computer-implemented method of claim 1 , further comprising:
determining an identity of the user associated with the interaction;
accessing user information based at least in part on the identity of the user; and
generating the recommendation based at least in part on the user information.
4. The computer-implemented method of claim 1 , further comprising causing the recommendation to be presented via a graphical user interface (GUI) presented via the third-party application, the GUI including at least one interactive component to allow the user to interact with the fulfillment service provider.
5. A system comprising:
one or more processors;
computer-readable media storing instructions, that when executed, cause the one or more processors to perform operations comprising:
generating, via a third party application, an interface of a fulfillment service provider using an application programming interface (API), wherein the interface enables a user to access fulfillment functionality from the fulfillment service provider using the third party application without leaving the third party application;
processing a request to access the fulfillment functionality from the fulfillment service provider, the request being received via the interface associated with the fulfillment service provider from the third-party application, the third party application being associated with a third-party service provider;
detecting that the fulfillment service provider has been initialized based, at least in part, on an indication of an interaction between a user and the third-party application;
determining context information associated with the interaction, the context information indicating a first event of the third-party service provider;
determining event information pertaining to the first event, the event information including one or more of: a first date, a first time, a first location, or a route between two locations;
predicting information pertaining to the first event based, at least in part, on the event information;
generating, using the predicted information, a recommendation of a second event pertaining to at least one of: a service available via the fulfillment service provider, a merchant available via the fulfillment service provider, or an item available via the fulfillment service provider; and
causing the recommendation to be presented via at least one of the third-party application or the fulfillment service provider through the generated interface.
6. The system of claim 5 , the operations further comprising:
receiving an authentication request from the third-party application; and
associating the fulfillment service provider with the third-party application based at least in part on authenticating the third-party application.
7. The system of claim 5 , the operations further comprising:
determining an identity of at least one of the user or a service provider associated with the third-party application;
accessing user information based at least in part on the identity; and
generating the recommendation based at least in part on the user information.
8. The system of claim 5 , wherein the event information includes at least one of: a location of the first event, a time of the first event or a real-time count of invitees attending the first event.
9. The system of claim 5 , wherein the event information includes a location of the first event, and the operations further comprise determining a set of merchants based at least in part on the location of the first event, wherein the set of merchants are within a threshold distance of the location of the first event.
10. The system of claim 5 , wherein the context information comprises at least one of:
a date;
a time;
a location;
an event detail associated with the first event;
one or more items added to a ticket or a virtual cart;
subject matter of a conversation between the user and another user via the third-party application;
subject matter of a content item presented via the third-party application;
subject matter of a social media post presented via the third-party application;
a pick-up location;
a drop-off location; or
a route between two locations.
11. The system of claim 5 , the operations further comprising determining the context information based at least in part on a machine-trained model.
12. The system of claim 5 , the operations further comprising causing the recommendation to be presented via a graphical user interface (GUI), the GUI including at least one interactive component to allow the user to interact with the fulfillment service provider.
13. A non-transitory computer-readable storage medium comprising computer program instructions configurable such that, when executed by one or more processors, the computer program instructions cause the one or more processors to:
generating, via a third party application, an interface of a fulfillment service provider using an application programming interface (API), wherein the interface enables a user to access fulfillment functionality from the fulfillment service provider using the third party application without leaving the third party application;
processing a request to access the fulfillment functionality from the fulfillment service provider, the request being received via the interface associated with the fulfillment service provider from the third-party application, the third party application being associated with a third-party service provider;
detecting that the fulfillment service provider has been initialized based, at least in part, on an indication of an interaction between the user and the third-party application;
determining context information associated with the interaction, the context information indicating a first event of the third-party service provider;
determining event information pertaining to the first event, the event information including one or more of: a first date, a first time, a first location, or a route between two locations;
predicting information pertaining to the first event based, at least in part, on the event information;
generating, using the predicted information, a recommendation of a second event pertaining to at least one of: a service available via the fulfillment service provider, a merchant available via the fulfillment service provider, or an item available via the fulfillment service provider; and
causing the recommendation to be presented via at least one of the third-party application or the fulfillment service provider through the generated interface.
14. The non-transitory computer-readable storage medium of claim 13 , wherein the fulfillment service provider is initialized responsive to receiving the request or detection of a trigger word associated with the interaction.
15. The non-transitory computer-readable storage medium of claim 13 , wherein the interaction is associated with the first event, wherein the recommendation identifies a set of merchants,
the computer program instructions further configurable to cause:
causing the recommendation to be presented via a graphical user interface (GUI), the GUI including at least one interactive component to allow the user to interact with the fulfillment service provider via the interface.
16. The non-transitory computer-readable storage medium of claim 15 , wherein:
the event information includes a real-time count of invitees attending the first event.
17. The non-transitory computer-readable storage medium of claim 13 , the computer program instructions further configurable to cause:
determining the context information, based at least in part on a machine-trained model.
18. The non-transitory computer-readable storage medium of claim 13 , wherein the context information comprises at least one of:
a date;
a time;
a location;
an event detail associated with the first event;
one or more items added to a ticket or a virtual cart;
subject matter of a conversation between the user and another user via the third-party application;
subject matter of a content item presented via the third-party application;
subject matter of a social media post presented via the third-party application;
a pick-up location;
a drop-off location; or
a route between two locations.
19. The computer-implemented method of claim 1 , wherein determining the event information comprises obtaining at least a portion of the event information from the third-party application, in real-time, during the first event.
20. The computer-implemented method of claim 1 , the recommendation providing a recommended second time at which the second event is to be initiated.
21. The computer-implemented method of claim 1 , the first event being a transportation event and the second event being a food order event.