The available evidence does not reveal what Takahiro Hashito actually paid, how much he posted, or the workflow he moved. So the headline’s personal cost question cannot be answered with a verified before-and-after figure. What can be compared is the current published pricing: X charges by API request and endpoint, while IFTTT offers subscription plans. Those are separate facts, not the author’s historical bill.
What is known about the switch
An indexed result identifies Takahiro Hashito’s article, “Why I dropped the X API for an IFTTT webhook – and what it cost me,” and tags it for automation, Node, and web development. The article text was not available in the indexed result, so it does not establish the author’s charges, posting volume, dates, implementation, or reasons for switching. A personal savings figure—or a claim that the webhook was cheaper for that workflow—would be speculation.
As an Amazon Associate I earn from qualifying purchases.
The useful comparison is therefore conditional: direct X API use is billed according to endpoint requests, while an IFTTT route may involve a plan subscription. To decide which costs less for a particular setup, compare the same period, post count, and link usage, and include any subscription needed for the IFTTT features involved.
Current published prices, separate from the author’s costs
The following figures are current published pricing checked on October 7, 2026. They are not historical prices paid by Hashito. X says its rates can change and points users to the Developer Console for current rates.
#1 Best Overall
| Service or plan | Published price | What the price applies to |
|---|---|---|
| X API | No subscription; pay-per-use credits | Charges vary by endpoint. |
| X Post Create | $0.015 per request | Current listed rate for a Post Create request. |
| X Post Create with URL | $0.200 per request | Current listed rate for a Post Create with URL request. |
| IFTTT Free | $0.00 | Includes two Applets. |
| IFTTT Pro | $2.99 monthly or $35.88 billed annually | The plan page lists Webhooks and Twitter Applets. |
| IFTTT Pro+ | $8.99 monthly or $107.88 billed annually | Published plan price; the cited plan information does not establish which features a particular workflow needs. |
Sources: X API pay-per-usage pricing and credits and IFTTT plans. Plan prices and included features can change; confirm the plan page and X Developer Console before budgeting.
How the webhook route works
IFTTT describes Webhooks as a way to send and receive web requests to connect a custom app or device with services. In an incoming-webhook setup, the application sends a request to Webhooks; receipt of that request triggers a configured Applet, which then runs its action. IFTTT describes the trigger this way: “This trigger fires every time the Webhooks service receives a web request to notify it of an event.”
For real-time Applets, IFTTT says they normally run within a few seconds after the trigger service notification. That is a service description, not a guarantee that every webhook-to-post workflow completes within a fixed time. See IFTTT Webhooks.
How to compare the two routes fairly
- Choose one time period. Use the same month or other interval for both options.
- Count the actions. Estimate the number of posts in that period and identify which X endpoint applies to each one.
- Account for links. X’s listed Post Create rate differs from its Post Create with URL rate, so classify requests accordingly rather than applying one rate to every post.
- Include the required IFTTT plan. Check whether the selected Applet and Webhooks features fit the Free plan or require a paid plan, then include the recurring subscription for the comparison period.
- Compare the operational trade-offs. Decide whether the time and work of maintaining a direct API integration is acceptable, and whether IFTTT’s Applet flow provides enough visibility and control for authentication, retries, and errors in your use case.
The first four steps produce a bill comparison from published rates and the workflow’s actual requirements. The last is a practical engineering decision: the available descriptions do not establish which route offers better failure handling or lower maintenance for Hashito’s implementation.
Rank #3
What the available figures can tell you
At the listed X rates, a request using Post Create with URL costs more than one using Post Create. That difference makes link inclusion and endpoint classification important to any estimate. But a direct-API total cannot be compared with IFTTT’s subscription price without the request count, mix of endpoints, relevant plan, and period. The headline alone does not provide those inputs.
X’s official pricing page states: “The X API uses pay-per-usage pricing. No subscriptions—pay only for what you use.” This describes X’s current model, not an assurance that a given workload is inexpensive. IFTTT’s plan price, meanwhile, is a subscription figure; the amount relevant to a particular workflow depends on which plan and features it needs.
When the switch may make sense
A webhook can be a reasonable route when an application needs to notify IFTTT of an event and an Applet can perform the required action. Direct API use may be preferable when the application needs control over its own request handling or when an Applet does not fit the workflow. These are decision criteria, not claims about the author’s undisclosed setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
- Favor a cost comparison based on actual endpoint counts and link use, not a single headline rate.
- Include the IFTTT subscription only if the plan required by the workflow is paid.
- Weigh the value of a managed Applet against the control and error-handling requirements of a direct integration.
- Recheck both services’ current terms and prices before making a budget decision.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
