Ideas

Add Instant Notification Capabilities to the API Via Webhooks
We want to be notified (proactively) when data changes on our stores' back-end, and webhooks are a fantastic way to do this! Webhook triggers (triggers = when & why data gets sent through a webhook) could include, but is not limited to, when a new order comes in, when a customer is deleted from the system, when an order is marked complete, etc. Our dream for your webhook system would be for you to generate a GUI (Graphical User Interface) webhook page available in our admin dashboard, the 'Webhooks' page. This 'Webhooks' page would allow us to view existing webhooks, delete webhooks, edit webhooks, or generate new webhooks. We want to set up specific parameters (filters based on all the available data options) per webhook. When the data meets the set parameters, detailed data will pass through those filters via that webhook URL. Then, when tools like integromat.com or zapier.com catch the data in the webhook, we can do some cool things with the data that we can't currently do with just your system! Examples of cool things could include, but are not limited to: 1) Automatically texting customers from our business phone system to tell them their order is complete. 2) Automatically sending a private slack message to the customer service manager when a customer record is deleted from the system. 3) Sending a customer a special 'thank you coupon code, to be used on their next order' for placing a new order with us. Webhooks provide us with instant filtered data for nearly instant communications and automation within our business!
1
·
Integrations
Gelato Intergration
Would like to intergate a program like Gelato to add customized products like phone cases using designs we are selling to customers on there stores. We have had many requests for phone cases, can coolers etc with designs created and sold on clothing we are selling on their stores. here is a little info on the gelato integration. Just want to know if this is possible now or in the near future Introduction The Gelato API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients. JSON is returned by all API responses, including errors. Base URL: https://order.gelatoapis.com If you have any questions or need help a great place to start is the help center. Authentication Before you can use the Gelato API you will need to generate an API key via our API Portal. Read more here. You authenticate your account by including your secret key in all API requests. Your API key carries privileges to create and manage your orders, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. To use your API key, you need to provide it in an X-API-KEY header with each call. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without a valid API key will also fail. Errors The Gelato API uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an structural or data error in the request (e.g., a required parameter was omitted, shipment prices are not found, etc.). Codes in the 5xx range indicate an error with Gelato's API servers (these are rare).
0
·
Integrations
Load More