IFTTT

About IFTTT

The IFTTT Connect API is a REST-based HTTP API located at connect.ifttt.com that lets developers integrate their own service into IFTTT connections. It handles connection lifecycle operations including enabling, showing, updating, and refreshing connections, as well as running triggers, queries, and actions tied to a user's account. All requests and responses use JSON, with standard HTTP status codes (200, 204, 400, 401, 403, 404, 422, 500, 502) indicating request outcomes.

Authentication supports two levels: unauthenticated requests limited to publicly-visible information, and service-authenticated requests using an IFTTT-Service-Key header for backend server calls. Most endpoints require a user_id parameter to access user-specific resources, which must match the ID returned by the developer's service to IFTTT. A Connect URL mechanism (https://ifttt.com/connect/{connection_id}) handles the authentication flow for enabling a connection, accepting parameters for email, redirect_uri, a provisional access code, and a skip_config flag.

The API is intended for developers building services that connect to IFTTT, whether through apps, websites, chatbots, or other client experiences. It can be used standalone or alongside IFTTT's iOS and Android SDKs, which are built on top of this API. IFTTT notes that it may add additional JSON fields to requests over time and instructs API implementers to ignore unrecognized fields rather than reject them.

Key features

• Connect URL flow that authenticates and enables connections across web, mobile, and SDKs
• Webhook endpoints for enabled, updated, and disabled connection events
• Trigger, query, and action endpoints for running service integrations
• Service-authenticated and unauthenticated request modes via IFTTT-Service-Key
• iOS and Android SDKs built on top of the Connect API
• Automatic storage of user field data required to run a connection

Frequently asked questions